hardware timed message

[_Bryan]

Hello,

  I have attached a screen shot of a small part of my program.  (I don't have XNET installed on the machine I used for the screen shot, sorry)  The important part of that message is the rolling counter that keeps the connection alive.  I also have to be able to change the battery state request value and the rest are static numbers at this point.

My main question is how can I have the rolling counter (0-13) sent every 100ms without relying on software timing?  And while still being able to change the battery state value when needed, but still sent at 100ms?

I have someone worried that windows xp might decide to do something that could interupt the counter timing or cause it to repeat or miss sending part of the count.   They are also testing new software on the unit under test and I don't want them to be able to say my rolling counter was off or had a hiccup.

[_Bryan]

Since no replies yet I decided to send an email to support.

[jaime_c]

I know it's been 4 years ... any chance you got a good solution?

[Hooovahh]

Sure use Queued Mode.  This will add some values into a queue which will be written one at a time, at the hardware timing specified.  Once the queue is empty it stops writing.  What you can do is have a seperate loop running, or periodcially service this queue.  If the queue is almost empty, add new elements to it to be written.  In the past this is how I accomplished a rolling watch dog where a signal needed to increment from 0 to 255 then back to 0.  My code would figure out what the next 10 values were to be written, then would add them to the queue if there were less than 10 in the queue.  It certainly isn't simple, and having the API support some kind of incrementing hardware counter would be nice but the control is there for hardware timed writes.