At 21:23 12/10/2002 -0400, Courtney wrote:
>Hi Brendan,

HI Courtney,
         thanks for the prompt reply as usual

>The pacing and EOC entries are not baudrate dependent.

OK good to know.


>  The entries simply
>control the amount of delay between each command or between the end of a
>line.  The ICOMs all echo the command that is sent to it plus whatever
>return values result from the command.  So, yes, DXbase does wait until it
>gets what is expected from a command.  If for some reason it doesn't get
>what it expected in a reasonable time, it times out and you see the error
>message.

So DXbase doesn't retry on error then?

It seems to me with the ICOM interface being unable to handle collisions 
that it would be highly desirable to allow for some retries on error. 
perhaps this retry No. could be specified in the radios.ini file, this 
would allow for no retires when setting up a new model or making changes as 
we don't want the retires masking timings that are too tight to work 
reliably under normal circumstances when testing changes.
Once reliable values have been tested then a retry value of 2 or 3 
would  prevent occasional errors with the ICOM interface from causing 
problems for the user (in the middle of the pileup..)

73
Brendan EI6IZ 

Reply via email to