SunSpec Model 64001 — Veris Status and Configuration
SunSpec Model 64001 is a proprietary Veris vendor extension block that exposes device health, firmware inventory, and sensing-module inventory for Veris string combiner and energy monitoring units such as the EA10. The template reads hardware revision, RS and OS firmware versions, boot count, DIP switch state, sensor detection counts, LED threshold percentages, and the location string over Modbus TCP. Per-slot records for up to four attached current sensing modules capture each module's address, firmware version, and serial number. This gives commissioning engineers a single-poll view of the entire sensing chain without opening a device web interface.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 37, read and write
- Brand
- SunSpec
- Last updated
Registers (37)
37 read, 1 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| id | Read | ||||
| l | Read | ||||
| cmd | Read and write | ||||
| hwrev | Read | ||||
| rsfwrev | Read | ||||
| osfwrev | Read | ||||
| prodrev | Read | ||||
| boots | count | Read | |||
| switch | Read | ||||
| sensors | count | Read | |||
| talking | count | Read | |||
| status | Read | ||||
| config | Read | ||||
| ledblink | Pct | Read | |||
| ledon | Pct | Read | |||
| reserved | Read | ||||
| loc | Read | ||||
| s1id | Read | ||||
| s1addr | Read | ||||
| s1osver | Read | ||||
| s1ver | Read | ||||
| s1serial | Read | ||||
| s2id | Read | ||||
| s2addr | Read | ||||
| s2osver | Read | ||||
| s2ver | Read | ||||
| s2serial | Read | ||||
| s3id | Read | ||||
| s3addr | Read | ||||
| s3osver | Read | ||||
| s3ver | Read | ||||
| s3serial | Read | ||||
| s4id | Read | ||||
| s4addr | Read | ||||
| s4osver | Read | ||||
| s4ver | Read | ||||
| s4serial | 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.
Use cases
- Verify that all four current sensing modules are detected and communicating after initial installation.
- Track boot count over time to detect unexpected device resets caused by power quality issues.
- Compare hardware revision and firmware versions across multiple Veris units on the same site.
- Alert on a mismatch between detected sensors and expected sensors to spot a failed module early.
- Record serial numbers and firmware strings for each sensing module as part of a site commissioning report.
Installation
Enable Modbus TCP on the Veris communications unit: connect it to your LAN via its Ethernet port and confirm the device has a valid IP address assigned either by DHCP or static configuration.
Connect the ModbusCloud Gateway to the same network segment as the Veris device, ensuring no firewall blocks port 502 between Gateway and device.
In the ModbusCloud portal, add a new device, select 'Import template', choose the SunSpec Model 64001 Veris Status and Configuration template, and enter the device IP address and unit ID matching your Veris unit.
Spot-check the 'sensors' register: its value should equal the number of physically connected current sensing modules; if it reads zero, verify cabling on the internal module bus.
Things to watch for
Why does the 'sensors' register always read zero?
The sensing modules communicate with the main communications unit over an internal bus. If the count reads zero, check that each module is firmly seated and that the daisy-chain ribbon cable between modules is undamaged. Power-cycle the unit after reseating; the 'talking' register should then report the same count as 'sensors'.
The gateway connects but firmware registers return 0x8000. What does that mean?
A value of 0x8000 on a uint16 register is the Veris not-a-number sentinel, indicating the register is unsupported or the field is unpopulated for that slot. Registers for sensor slots 2 through 4 will return 0x8000 if fewer than the maximum number of modules are installed; this is expected behavior, not a communication fault.
Is it safe to write values to the 'cmd' register at any time?
No. The cmd register triggers device-level actions such as clearing all accumulators. Writing it inadvertently during live monitoring will reset accumulated energy data and may affect billing or performance calculations. Test any write commands in a maintenance window, verify the intended command code in the Veris point map documentation before writing, and do not poll it as a read register repeatedly.
Why does the unit ID setting matter for this device?
The Veris communications unit responds on a specific Modbus unit ID that is set via DIP switches or device configuration. If the unit ID in your ModbusCloud template does not match the device's configured ID, all reads will return a timeout or exception. Cross-check the unit ID in the device's configuration page or by reading the DIP switch position from the 'switch' register.
Knowledge base articles for this device
SunSpec Modbus: one register map for many inverters
SunSpec Modbus is the open register map SMA, Fronius, SolarEdge and Kostal share. The layout, int+SF vs float, the TCP port per brand and reading a mixed fleet.
Fronius Modbus: read a Symo GEN24 over Modbus TCP
Fronius Modbus explained: enable Modbus TCP on the Symo GEN24 on port 502, choose between int+SF and float, read the right SunSpec registers and scale them correctly. Practical guide for solar installers.
SMA Modbus: reading a Sunny Boy over Modbus TCP (installers)
SMA Modbus explained: enable the Modbus TCP server on port 502, choose between the SMA profile (unit ID 3) and SunSpec (unit ID 126), read the right registers, and handle the NaN values at night. Practical guide for installers.
Want to see how it works?
