*****very important discovery*****
I have recently discovered that there are variations of 'restricted' AR-DV1's, which deal with the restrictions in different ways.
eSPYonARD has to regularly check many things in order to keep its screen display updated.
Two of those involve interrogating the Radio regarding 'de-scrambler' settings.
Many restricted AR-DV1's accept those commands, and send out the replies as per AOR's manual. I know that to be true because I have lots of Customers who I am in contact with, using the U.S. Radio.
However some restricted Radios do not. They either send no replies, or non documented ones.
That will cause problems with the program, as it checks and re-sends commands if the AR-DV1 does not reply as documented.
There was no way of knowing this anomaly existed, especially as so many 'restricted' AR-DV1's worked with no problem. Thank goodness a new User contacted me just a week ago, and because of that it became apparent, and it could be corrected.
When I became aware of this I incorporated a 'checking routine' which can identify when certain AR-DV1's experience this anomaly, and once identified the program no longer calls those routines, thus eliminating the problem.
NOT as simple as it sounds as AOR provide no way of distinguishing between different AR-DV1 variations.
This 'fix' will be in the new update v.60007-007, and a LOT of other new things too.
I have recently discovered that there are variations of 'restricted' AR-DV1's, which deal with the restrictions in different ways.
eSPYonARD has to regularly check many things in order to keep its screen display updated.
Two of those involve interrogating the Radio regarding 'de-scrambler' settings.
Many restricted AR-DV1's accept those commands, and send out the replies as per AOR's manual. I know that to be true because I have lots of Customers who I am in contact with, using the U.S. Radio.
However some restricted Radios do not. They either send no replies, or non documented ones.
That will cause problems with the program, as it checks and re-sends commands if the AR-DV1 does not reply as documented.
There was no way of knowing this anomaly existed, especially as so many 'restricted' AR-DV1's worked with no problem. Thank goodness a new User contacted me just a week ago, and because of that it became apparent, and it could be corrected.
When I became aware of this I incorporated a 'checking routine' which can identify when certain AR-DV1's experience this anomaly, and once identified the program no longer calls those routines, thus eliminating the problem.
NOT as simple as it sounds as AOR provide no way of distinguishing between different AR-DV1 variations.
This 'fix' will be in the new update v.60007-007, and a LOT of other new things too.