AW: [EXTERNAL] Experiences using RS-485 Multi-Drop with StreamDevice?

["Zimoch Dirk \(PSI\) via Tech-talk" <tech-talk at aps.anl.gov>]

StreamDevice is locking only for the duration of one protocol. So If you have protocols which send only the commands and do not wait for a reply but read the replies with separate I/O Int records, locking would not apply.

StreamDevice has the %=... feature to compare incoming data with a given value. Thus if you have the unique ID in some record, you could do something like { in "%(unique_ID_record)=d %f"; } (assuming decimal ID) in the I/O Intr records which should filter the reply with the matching ID.

 

I am not sure about performance though.

 

Dirk

 

Von: Tech-talk <tech-talk-bounces at aps.anl.gov> Im Auftrag von Ralph Lange via Tech-talk
Gesendet: Montag, 26. Oktober 2020 18:03
An: EPICS Tech Talk <tech-talk at aps.anl.gov>
Betreff: Re: [EXTERNAL] Experiences using RS-485 Multi-Drop with StreamDevice?

 

Thanks a lot Matt,

 

That unique ID is in addition to the RS-485 address, like a transaction counter.

It looks like any single controller can cope with multiple commands being received at high speed, and will send the responses in some (any) order, using the unique ID from the respective command in the replies for the master to tell them apart.

This "parallel" mode probably does not apply as StreamDevice/Asyn is serializing the protocols and waits for the response before sending the next request.

 

Thanks again,

~Ralph