DEVCOM: Device Communications Overview

Providing insights into DEVCOM for CyFlex users, emphasizing the importance of confidentiality during interactions, and explaining the three types of devcom interfaces available - AK, GENSYNC, and GENSTREAM. The presentation also covers AKG protocol communications, pitfalls to be cautious about, and the different ways Devcom can be interfaced with instruments.

• Communication
• CyFlex
• Devcom
• AK Protocol
• GENSYNC

hoffpauir_l Follow

Uploaded on Oct 06, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. DEVCOM GENERAL DEVICE COMMUNICATIONS

2. The information in this presentation is provided to all users of CyFlex. Please do not share this information to individuals not directly related to the use of CyFlex. Additionally, at lunch and learn events, there are multiple companies on this call and not all companies have non-disclosure agreements (NDA) with each other. Because of this, all participants should be careful to not share any proprietary information.

3. DEVCOM Devcom is intended to provide communications with instruments over serial or TCP. Three types of devcom interfaces are available: AK Using Emerson AK Protocol GenSync Command and Response Protocols GenStream Data is sent continuously. 3

4. GENSYNC Provides for SYNCHRONOUS communication. Command and response. No data can be received that is not requested. Example Device SCPI Protocol to measure voltage and current, as well as reporting device errors. MEAS:VOLT? [floating point value] MEAS:CURR? [floating point value] SYS:ERR? [integer value], [string] View Example 4

5. GENSTREAM Provides for STREAMING and synchronous communication. Command and response. Polled unrequested data. (Note: Asynchronous data is not yet supported.) Example Device Command to stop and start streaming. GenStream start GenStream stop Streamed voltage and current measurements volt=[value] curr=[value] View Example 5

6. AKG Provides for standard AK protocol communications. Example Device Provides only AKEN command. View Example 6

7. PITFALLS Caution: Hardware handshaking is on by default. STTY settings can be set in spec files for devcom. Limitation: Currently spaces are always taken as delimiters. This means that strings (i.e. sentences) cannot be read. This will be corrected in a later revision. 7

8. INTERFACES Devcom can be interfaced with in three ways: devcom_smsg_tst Provides one time devcom communications for testing. Ex: devcom_smsg_tst genSyncDemo SYST:ERR? errNum_devCom gp_test gp_test scripts can communicate through devcom directly. Ex: @DEVCOM # instrument name genSyncDemo # command key strings # SYST:ERR?, %d %s SYST:ERR? errNum_devCom errStr_devCom devcom_mon event and variable driven communication running independently. 8

9. DEVCOM_MON Provides abstraction from the hardware device. Can be driven by timers as well as events. View example devcom_mon implementation. 9

10. GP_TEST Provides greater control over sequences of commands. Can be used in conjunction with devcom_mon utilizing events for sequencing. View example gp_test implementation. 10

11. DEBUGGING Minicom Used to experiment with the instrument to help understand the protocol. /data/errors/ log files strace sin names strace p[pid] eread,write tt & 11

12. DEVCOM DEVICES IN USE Examples of devices which use DevCom at CTC AVL415G (Smoke Meter) AVL439 (Smoke Meter) AVL483 (Soot Sensor) AVL740 FuelExact AVL Slim Line NoxBox (custom setup) HORIBA SPCS 12

13. December Lunch and Learn session: 12/04/19 Presenter: Len Logterman Topic: go.scp Template 13