Show Posts
1
Technical support / Re:NETCMD$ TIMING?
« on: June 04, 2007, 12:31:10 PM »
I see a difficulty for an application I am considering with the comm timing and overhead.
I wish to use TH100MD as a host, connecting to up to 15 E10+npn unis with the RS-485. They will be polled regularly (it would be good if I could poll all 15 in a .5 second loop for simple I/O input states, with a very an occasional single on/off variable would be sent to the remote E10 unit.
There will be an optic sensor input on each E10 (as well as on the MD unit) with input of as little as 15ms duration that I need the E10 to register and latch in memory to respond to the poll from the Host to inform the Host an input pulse did occur, even if the pulse is gone.
Some E10 units will also have a motor position sensing digital I/O input (simple switch detector on a cam), that when activated, the E10 must turn off an local output within approximately 50 to 70ms of the input rise (programmed to be done locally, not through the host MD).
Is the NetCMD$ wait time of .15s a timeout? Will successful, short (digital I/O monitoring or setting) message take less time?
Can an E10 unit latch (remember) an input occurance (not trying to count them, more than one occurrance doesn't matter) while handling a Host communication request? And can I ensure a local E10 output state be turned off in 50ms from a local input rise in the E10 while it is polled regularly from the Host?
I wish to use TH100MD as a host, connecting to up to 15 E10+npn unis with the RS-485. They will be polled regularly (it would be good if I could poll all 15 in a .5 second loop for simple I/O input states, with a very an occasional single on/off variable would be sent to the remote E10 unit.
There will be an optic sensor input on each E10 (as well as on the MD unit) with input of as little as 15ms duration that I need the E10 to register and latch in memory to respond to the poll from the Host to inform the Host an input pulse did occur, even if the pulse is gone.
Some E10 units will also have a motor position sensing digital I/O input (simple switch detector on a cam), that when activated, the E10 must turn off an local output within approximately 50 to 70ms of the input rise (programmed to be done locally, not through the host MD).
Is the NetCMD$ wait time of .15s a timeout? Will successful, short (digital I/O monitoring or setting) message take less time?
Can an E10 unit latch (remember) an input occurance (not trying to count them, more than one occurrance doesn't matter) while handling a Host communication request? And can I ensure a local E10 output state be turned off in 50ms from a local input rise in the E10 while it is polled regularly from the Host?