Apogee Instruments Apogee Instruments Guardian SM-500 / SM-600 Modbus RTU template

Apogee Instruments Guardian SM-500 / SM-600

Greenhouse climate monitor for PAR or ePAR, air temperature, humidity, CO2, VPD, dew point and pressure.

The Apogee Instruments Guardian SM-500 and SM-600 are fan-aspirated multi-sensor monitors that measure PAR (SM-500) or ePAR (SM-600), air temperature, humidity, CO2, vapor pressure deficit, dew point and barometric pressure in greenhouses, grow rooms and vertical farms. This Modbus RTU template reads all measurements, fan speed and device status, and lets you write the fan, averaging, calibration and communication settings from ModbusCloud.

Protocol
Modbus RTU
Connection
RS485, 19200 baud
Registers
58, read and write
Key readings
PAR or ePAR · Air temperature · Relative humidity · CO2 concentration · Vapor pressure deficit · Dew point · Barometric pressure · Fan speed
Available commands
Start measurements at power-on · Fan duty cycle · Fan darkness threshold · PAR multiplier and sensor offsets · Running average time · Modbus address and serial settings
Compatible models
Guardian SM-500 · Guardian SM-600
Last updated

Registers (58)

58 read, 31 write

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
PAR / ePARµmol/m²/sRead
Air Temperature°CRead
Relative Humidity%RHRead
CO2ppmRead
Barometric PressurekPaRead
Vapor Pressure DeficitkPaRead
Dew Point°CRead
Fan SpeedrpmRead
Device StatusRead
PAR / ePAR (Integer)µmol/m²/sRead
Air Temperature (Integer)°CRead
Relative Humidity (Integer)%RHRead
CO2 (Integer)ppmRead
Barometric Pressure (Integer)kPaRead
Vapor Pressure Deficit (Integer)kPaRead
Dew Point (Integer)°CRead
Fan Speed (Integer)rpmRead
Device Status (Integer)Read
Start Measurements at Power-OnRead and write
Start Measurements at Power-On (Integer)Read and write
Fan Duty Cycle%Read and write
Fan Duty Cycle (Integer)%Read and write
Fan Darkness Thresholdµmol/m²/sRead and write
Fan Darkness Threshold (Integer)Read and write
Running Average TimesRead and write
Running Average Time (Integer)sRead and write
Bluetooth ControlRead and write
Bluetooth Control (Integer)Read and write
LED IndicationRead and write
LED Indication (Integer)Read and write
PAR MultiplierRead and write
PAR Multiplier (Integer)Read and write
PAR Multiplier FactoryRead
PAR Multiplier Factory (Integer)Read
PAR Offsetµmol/m²/sRead and write
PAR Offset (Integer)µmol/m²/sRead and write
Air Temperature Offset°CRead and write
Air Temperature Offset (Integer)°CRead and write
Humidity Offset%RHRead and write
Humidity Offset (Integer)%RHRead and write
CO2 OffsetRead and write
CO2 Offset (Integer)Read and write
PAR Multiplier Factory (Alt 108)Read
PAR Multiplier (Alt 109)Read and write
Slave AddressRead and write
Slave Address (Integer)Read and write
Baud RateRead and write
Baud Rate (Integer)Read and write
ParityRead and write
Parity (Integer)Read and write
Stop BitsRead and write
Stop Bits (Integer)Read and write
Model NumberRead
Model Number (Integer)Read
Serial NumberRead
Serial Number (Integer)Read
Firmware VersionRead
Firmware Version (Integer)Read

Loading registers…

Send your device list

If a device is not in the library yet, we build the template for free as soon as we have the register data.

Number of installations (optional)

Use cases

  • Show PAR, air temperature, humidity, CO2 and VPD per greenhouse compartment or grow room on one dashboard.
  • Get an email alert when CO2 falls below your dosing target or VPD rises above a limit you choose.
  • Keep a year of light, temperature and humidity history to compare growing conditions between crops and seasons.
  • Alert on a low fan speed, so a blocked or failed aspiration fan is noticed before it affects the air temperature.
  • Stop the fan before fogging or spraying with a scheduled automation, and switch it back on afterwards.
  • Download the measurements as CSV for your own crop registration or climate reports.

Installation

  1. Connect the white wire (RS-485 positive) and the blue wire (RS-485 negative) to the RS485 port of the ModbusCloud Gateway and the black wire to ground. Terminate the bus with 120 Ohm at both ends.

  2. Tie the green wire to ground to select RS-485 and power the Guardian with 5.5 to 32 V DC on the red wire. The USB cable only supplies power and carries no data.

  3. The Guardian ships with address 1, 19200 baud, 8 data bits, even parity and 1 stop bit. Change them in the Apogee Connect app if the bus needs other settings.

  4. In ModbusCloud, add a Modbus device with protocol RTU, address 1 and 19200 8E1, then import this template.

  5. Write 1 once to Start Measurements at Power-On. Then check that PAR, air temperature, humidity and CO2 show plausible values in ModbusCloud.

Things to watch for

The Guardian does not answer. What should I check?

Check 19200 baud, even parity, 1 stop bit and address 1, or the settings you chose in the Apogee Connect app. The green wire must be tied to ground for RS-485; tied to 12 V the Guardian talks RS-232. Swap the white and blue wires if nothing answers. If the Guardian has its own power supply, run a ground wire between the Guardian and the Gateway.

Why are all values 0 after a power cut?

To save energy the Guardian only starts measuring after the first read of a measurement value, and that first read returns 0. This happens after every power cycle. Write 1 once to Start Measurements at Power-On and the Guardian measures as soon as it has power. CO2 and humidity can still take up to 30 seconds after power-up to become accurate.

Why is each measurement in the list twice?

The Guardian gives every value as a precise floating-point number and as an integer copy multiplied by 10 or 100. The template scales the copies back, so both show the same value. Use the floating-point values on your dashboards. The integer PAR copy cannot show more than 3276.7, which bright sunlight or strong grow lights can exceed.

Can I change settings from ModbusCloud?

Yes. Writing is off per gateway by default, so request it for the gateway in the portal first, and read a setting before you change it. A new baud rate, parity or number of stop bits only takes effect after a power cycle, a new address at once. Never write 0 to Slave Address: that sets address 1 and resets the factory calibration. Write 0 to PAR Multiplier to return to the factory value.

Why is the fan running again after a power cut?

Fan control and Bluetooth control set over Modbus do not survive a power cycle. If you stop the fan for fogging or spraying, write the fan duty cycle again after a restart, for example with an automation. A duty cycle of 0 stops the fan; when it runs, the minimum speed is 40 %.

Want to see how it works?

Electrician working in an open distribution board