Serial protocol with different timeouts

[GregorFey]

Hi,
first of all i'll want to thank all of the people involved into serialport. It is an amazing library.

Now the job is to realize a protokol with different timeouts. Therefore i think of using InterByteTimeout. To change the timeout i use the following code:

parser = port.pipe(new InterByteTimeout( {interval: newTimeout, maxBufferSize: newBufferSize} ))

On the 11th change the following warnings are thrown:
(node:6404) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added to [SerialPort]. Use emitter.setMaxListeners() to increase limit
(node:6404) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 data listeners added to [SerialPort]. Use emitter.setMaxListeners() to increase limit

Increasing the count of possible listeners will not solve the problem, since the protocol will run for hours, handling tons of transmissions. The clean and only way is to avoid touching the limit for the listeners.

At this point i have the following questions:

Is this the right implementation for the problem or would it be better to use javascript timers?
How should i set a new timeout to avoid the warnings if its the right way ?

Many thanks in advance...

Regards

PS: Full stacktrace (--trace-warnings) for the warnings

(node:6404) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added to [SerialPort]. Use emitter.setMaxListeners() to increase limit
    at _addListener (events.js:390:17)
    at SerialPort.addListener (events.js:406:10)
    at SerialPort.Readable.on (internal/streams/readable.js:858:35)
    at SerialPort.once (events.js:437:8)
    at SerialPort.Readable.pipe (internal/streams/readable.js:669:9)
    at Object.readAck (G:\Projekte\Prototypes\Node\rs232\protocol.js:62:31)
    at Object.askWaitAck [as action] (G:\Projekte\Prototypes\Node\rs232\protocol.js:83:16)
    at Object.run (G:\Projekte\Prototypes\Node\rs232\fsm.js:47:46)

(node:6404) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 data listeners added to [SerialPort]. Use emitter.setMaxListeners() to increase limit
    at _addListener (events.js:390:17)
    at SerialPort.addListener (events.js:406:10)
    at SerialPort.Readable.on (internal/streams/readable.js:858:35)
    at SerialPort.Readable.pipe (internal/streams/readable.js:716:7)
    at Object.readAck (G:\Projekte\Prototypes\Node\rs232\protocol.js:62:31)
    at Object.askWaitAck [as action] (G:\Projekte\Prototypes\Node\rs232\protocol.js:83:16)
    at Object.run (G:\Projekte\Prototypes\Node\rs232\fsm.js:47:46)

[GregorFey]

Ok, further reading of the documentation leads to the conclusion, that my idea is not working due to the following issue:

InterByteTimeout parser needs one byte to be received to begin the timeout. So it waits for the first char for ever and therefore
a timeout for the first character can't be implemented using a InterByteTimeout parser.

So here a clarification of what should happen and which timeouts are needed.

1. A request is written
2. Wait for ACK/NCK for the request. Timeout the reading after ACK_TIMEOUT
3. If the receiver did sent NCK, cancel the request and start over.
4. Wait for the first byte of the answer to the request send in step one. Timeout the reading after ANSWER_TIMEOUT.
5. Read the subsequent bytes using an inter byte timeout of CHAR_TIMEOUT. Here the InterByteTimeout parser comes into play.

Any hint how to achive this will be appreciated. If i'm wrong at any point, you are welcome to point out my misconception.

Thanks in advance again...

Regards