Using the Serial Data Collector


What is RS232 DB9 serial port | RS232 pinout

Tripp Lite USB C to USB-A Cable USB Type C 3.1 Gen 1, 5 Gbps M/M 20in - First End: 1 x Type A Male USB - Second End: 1 x Type C Male USB - 5 Gbit/s - Nickel Plated Connector - Gold Plated Contact - Black


Serial ports are tried and tested interfaces that can be found on many devices.  It is not uncommon to run across RS232, RS485, and 4-20ma serial interfaces on new and in-service equipment.  Another common form of serial interface is USB (Universal Serial Bus), this is often used on development boards and loggers for communicating with a host (i.e. – Arduino-based systems).

Bringing data into Machinechat JEDI from serial interfaces is made possible with the serial data collector introduced in v3.0 of the software. Data in CSV (comma separated values) can be sent to JEDI via a serial interface on the machine where JEDI is running. For example, an Arduino-based system may send out the values for “light”, “sound”, and “temperature” on a regular basis.  The recurring data might look like this:



Setting up a JEDI serial data collector consists of 5 steps:

  1. Select the serial port to monitor
  2. Select a unique TargetID name for the data stream
  3. Set the serial port parameters (baud rate, stop bits, data bits, and parity)
  4. Set the record delimiter
  5. Add the CSV fields

Optionally, the timestamp can be extracted from the serial data if it is present, but by default the data is stamped as it comes in.


Once the data collector is setup and enabled, the serial data will enter JEDI and be available to create dashboards, rules, and actions with.  One of the best places to start is the “device dashboard”, where you can see the data coming into the system like this:


If you are having trouble bringing in serial data, a handy debugger is available.  In the lower left portion of the serial data collector setup screen you can "Enable Debug".  This will capture activity and any errors taking place when the collector is running.  You can find the output of this capture in the "debug" sub-directory where JEDI is installed.




Was this article helpful?
0 out of 0 found this helpful