RS232: initial delay is 3500ms and interchar is 750ms. IP: initial delay is 5000ms and interchar is 250ms.
The initial delay is a wait time. When a Nevo Widget sends a command to a 3rd party device this device needs some time to come up with its response. Nevo will wait a certain amount of time and if the 3rd party device fails to answer within this timeframe the device block will stop and become available for the next round of communication. If there’s something in the device blocks buffer, it’ll immediately send this command. If the buffer is empty the block will wait for the next incoming command.
The initial delay on IP devices is a bit longer because IP networks can be a bit slower e.g. due to network congestion.
When the 3rd party does respond, it’ll do so serially, i.e. one character at a time. There is a small delay between those characters. Nevo will wait a certain amount of time for the next character to become available. If there’s no character within this timeframe Nevo considers the transmission to be done. This means that at that point in time the Device Block will spit out the response string of the 3rd party device.
Some RS232 devices are very slow or they interupt the response stream because they need time to calculate something or to come up with a list (e.g. artist list). That’s why the intercharacter delay is quite long. But it is needed to be able to support all RS232 devices out there.
In summary:
The Nevo will wait (3500ms for RS232) for a response from a device. If it sees a response then it waits 750ms as each bit comes in. After 750ms with no data it assumes the device is finished sending and then processes the info.
If the RS232 device replies in 500ms the remaining 3000ms is ignored. Same goes for the intercharacter timeout. Except for the last one. So when the RS232 device finished sending its response, Nevo will still wait 750ms for the next character which will never be there. After that the widget continues.
