DonS
Member
I posted the below in a couple of threads where people had described a specific problem, but thought it might be a good idea to have it show up on the main forum page, as well:
For those who have seen a 'failure to lock onto VC', or 'ping-ponging between CC and VC'....
If you're using Win500 to upload to the radio, it's possible that that program is contributing to the problem. I wasn't initializing some data correctly when building TSYS objects for upload, and it looks like that corrupted data could kill the radio's ability to tune or unmute VCs in some circumstances. That corrupted data seems to affect CPU U0.1 more than F1.0, based on my testing.
I was able to reproduce the problem here on a couple of Motorola 3600 systems using U0.1 and Win500 v00.40. I've released Win500 v00.41 - I haven't seen the problem with that version.
For those who have seen a 'failure to lock onto VC', or 'ping-ponging between CC and VC'....
If you're using Win500 to upload to the radio, it's possible that that program is contributing to the problem. I wasn't initializing some data correctly when building TSYS objects for upload, and it looks like that corrupted data could kill the radio's ability to tune or unmute VCs in some circumstances. That corrupted data seems to affect CPU U0.1 more than F1.0, based on my testing.
I was able to reproduce the problem here on a couple of Motorola 3600 systems using U0.1 and Win500 v00.40. I've released Win500 v00.41 - I haven't seen the problem with that version.