At CO2Meter.com, when we are chasing down a customer application question, we use our Free GasLab® software to solve connection and syntax issues. You can too.
Think of GasLab® as a sanity tool. Suppose you're developing communication software for a sensor system and something happens. Either the sensor stops responding, or it returns nonsense results. This leads to all kinds of questions. Has the sensor died? Have I broken something the code? Is the problem another piece of hardware? Popping the sensor out of the circuit and being able to test it independently to zero in on the fault can save you hours of frustration. Trust us, we've all been there too!
GasLab® streaming display & debugging command sequences
Start by connecting your sensor up to your PC via USB. If you're using a devkit that includes both a sensor and a USB cable, this is easy. If you only have the sensor, first read the online documentation for instructions to communicate with your particular sensor. GasLab® is designed to work with every sensor we offer. Once you have the sensor connected to your PC, follow the instructions to install GasLab® from our website
In the example on the right (click to see larger image), “all call” MODBUS address (FE) or the default address 68 can be used follow by 44 (read RAM) starting at address 0008 (the location of current CO2 value) which so 2 bytes long. GasLab inserts the MODBUS CRC code and the sensor reply’s with the current value. “A hidden gem” is that in the K30 sensor, temperature is reported at location 000A. There is a lot more on this in the application notes and communication documentation.
As you can see, GasLab® gives you the technical ability to test the operation of any sensor at the most basic level.
Testing command sequences during code development and to diagnose potential self-inflicted problems can save you hours. It sure beats trial and error.