Communicator
The Communicator page displays all the devices delivered to support the monitoring of your energy flows. Each device is equipped with a SIM card, allowing it to serve as a gateway to the network. These devices may either include an internal meter (such as the E350 or KWHIQ) or enable the monitoring of connected equipment like inverters, meters, or sensors.
Communicator fields
Communicators cannot be created or modified in the Cast4All Platform. These fields however give you more information on the state of the communicator.
| Field element | Description |
|---|---|
| Logical device name | Unique identifier for the communicator |
| Configuration information | Details on the firmware version and uploaded configuration |
| Registration details | Status of the device and date of first registration |
| Network connection and polling | Detailed time information on the performed actions |
| Security field | Field that states which group can access this communicator - also applicable in the Cast4All Connect app |
| Resident user | Mailing address of the linked resident |
Detailed information
Measuring device
The type field of the communicator defines which and how many measuring devices are linked to a communicator. Each measuring device can be configured by using the Upload Configuration File command. The serial number of a measuring device is filled in after performing a verification test for the connected gateway.
Communicator remote command
This tab shows the history of all the actions that are performed on this communicator. You can easily follow up on the progress of your action through this tab.
Connection test
The progress and result of your connection test (cf. Commands) can be consulted through this tab. This tab shows a more detailed result compared to the communicator remote command tab as it gives you feedback on the signal strength and failed/succeeded connections.
Pv production test
The progress and result of your pv production test (cf. Commands) can be consulted through this tab. This tab shows a more detailed result compared to the communicator remote command tab as it gives you feedback on the read-out values and result message in case of a failed test.
Communicator verification
The progress and result of your verification test (cf. Commands) can be consulted through this tab. This tab shows a more detailed result compared to the communicator remote command tab as it gives you feedback on the values that are read out on the different channels and registers. This tab can be used to validate the connections. Consult the FAQ in case of a failed verification.
Commands
These commands allow you to configure the communicator and make sure the device is well tested before registering it to an installation.
Request Manual Polling
All registered communicator devices are polled at least once a day. This polling can be triggered manually by performing the Request Manual Polling command. The command performs a read-out of the communicator and all connected devices. After setting up a connection with the device, its buffer will be read out and all values are stored in our Cast4All Platform.
Request Connection Test
The connection test attempts to perform two actions: sending a small data packet and establishing a stable data connection with the communication module. The test allows you to check whether the communication module has an active connection either via SIM or LAN. If the SIM connection succeeded, it will also tell you the signal strength of the connection. In order to have a stable connection, this strength should be greater than -95dBm.
KWHIQ: 94.31.6
E350 (Landis & Gyr): 9.4.31.4
Request Verification
The verification test performs a readout of all available channels of the gateway module. The result indicates how the channels are configured and whether the readout was successful. Check the Verification Test tab for the results on the channel and register readouts. If the verification test fails, refer to the FAQ for solutions.
Request Pv Production Test
By performing this test, you can check the validity of the solar energy values. Be aware that this test may take several minutes to complete. The cumulative export value should increase, while the imported energy may also increase. However, the increase in exported energy should be greater than the increase in imported energy. The test results will indicate either success or failure and can be found in the Pv Production Test tab. A failure may suggest that the meter is wired incorrectly or that the exported energy is not increasing. For troubleshooting steps, refer to our FAQ.
Upload Configuration File
In order to properly read out the communication module and its connected meters, the communicator needs to be configured. The device then knows how and what meters/sensors to read out and at what frequency. Select the correct Configuration file and polling option and press confirm. Select the Has to skip polling boolean if the gateway does not have the Registered status yet, the buffer will then not be read out. The progress can be checked in the Upload Configuration File tab and Communicator Remote Command tab. The next step is the verification test in order to check the validity.
Upgrade Firmware Version
Each new firmware version consists of fixes and new features for the communication module. Use this command to upgrade the module to the inputted Firmware Version. Release notes on every firmware version are made available to you when a new firmware version is uploaded to the devices. This command is mostly performed automatically by Cast4All.
Request Modbus Action
Through this command, you can read or write the register of a connected device. Some predefined actions can be selected in the Modbus action type dropdown. If it concerns a writing action, input the desired Register value and confirm.
Furthermore, you can construct your own reading or writing action by combining the Modbus function code and address fields. Refer to the Modbus protocol documentation or the Modbus device's specifications for the supported function codes. The Slave address is the modbus address of the meter you want to access from the master device. The Register address defines the location of the data. After a function code is selected, the Register length has to be given as well. More information can be found in the modbus documentation.
The progress and result of the action can be found in the Modbus action type tab under the communicator element.