Frequently Asked Questions

1. Make sure the gateway has connection by performing the Request Connection Test command on the communicator element. If this test fails or returns an error message, please refer to 'Why does my connection test fail?'.
2. When the registration concerns a communication module with connected devices (Sungate with inverter, Lewiz/Dingate with meters and sensors...), make sure the verification test has succeeded. Refer to the 'Failed Verification' topics in order to achieve a successful test.
3. Perform the Register Gateway command on an existing installation or create a new installation by using the plus icon in the installation overview. Futher information can be found here: New Installation

1. Make sure the main communication gateway has connection by performing the Request Connection Test command on the communicator element. If this test fails or returns an error message, please refer to 'Why does my connection test fail?'.
2. Make sure the verification test has succeeded. Refer to the 'Verification failure' topics in order to achieve a successful verification test.
3. Perform the Register Meter command using the meter's serial number. This can be done on an existing installation or create a new installation by using the plus icon in the installation overview. Futher information can be found here: New Installation

1. Check if the module is powered on.
2. Perform a connection test and check the signal strength; it should be greater than -95dBm. Increase the signal strength if necessary by moving the module to a location with better coverage: for example, make sure there are no large metal objects nearby. Most modules - except the Sungate - support the use of external antennas that can boost the signal strength. Sungates are equipped with a built-in internal antenna and do not require additional external enhancements.
3. If the signal strength is enough and the test fails, other issues might be affecting the connection: general network issue, connection refused by the device. Physically resetting the device might trigger the module to reset the connection. This can be done either by a technician on-site or by the resident. Power down the module and power it back on after at least 5 minutes.
4. We are currently working on an implementation to trigger a SIM card reset through the Cast4All Platform. This might result in the SIM card resetting its connection to the network.
5. An RMA can be requested if all previous steps have been taken: contact support@cast4all.com.

1. First of all, check if your meter has registered measurements. If the meter was falsely registered to another installation first, and the meter has not been removed, no new measurements can be registered for the new installation. Remove the old meter if present and use the Register Measurement command.
2. Perform a connection test and refer to the 'Connection Failure' topic if necessary.
3. Perform a verification test and refer to the 'Verification failure' topics in order to find the cause of the data disruption.

When this error occurs, it means that the respective channel could not be read because it has not been configured yet or the underlying meter has not been connected.

1. Does it concern a Dingate module? Configuring this device might take a while, try the verification test again after a few minutes.
2. Does the error concern the reading out of a grid meter where a P1MB module or P1 port is used? This probably means that the meter has not been well connected.

This error indicates that the meter is not providing (correct) feedback on the given modbus address.

1. Is the meter powered on? If it for example concerns an inverter and is it already dark outside when performing the verification, the inverter might have shut itself down. Try again the next morning.
2. Does the error occur in combination with the 'device datalink response packet is wrong' error with code 3? In that case, it is likely that only a single meter on the modbus line is causing the issue: disconnect each meter and reconnect them one by one, accompanied by a verification. This problem often occurs when using a P1MB module: check the connection and, if necessary, replace the P1MB module.
3. Check if the line settings (baud rate, modbus address and parity) on both the meter and the communication device are correct.
4. Make sure you uploaded the correct configuration to the gateway.
5. Check the wiring between the communication module (Sungate, Dingate, KWHIQ or Lewiz) and the device.
6. Retry the verification test.

This error message means that the modbus response received by the communication module from the respective meter it is querying is in an incorrect format. The data in the message is not processed because there is no certainty that it is correct data. This suggests that a meter with the correct line settings is connected to the Modbus line, but an issue occurs due to one of the following reasons:

1. A kink in the modbus cable can cause the message to be disrupted, this should be checked on-site.
2. It is possible that two different meters are set to the same modbus address, causing them to try to respond at the same time, leading to overlapping responses. Make sure the modbus addresses are correct.
3. A defective meter could cause interference on the modbus line. Disconnect each meter on the modbus interface and reconnect them one by one, accompanied by a verification.

If this error is returned after performing a verification, something must be wrong with the modbus wiring, as the interface is quite sensitive to disturbances.

1. A kink in the modbus cable can cause the message to be disrupted, this should be checked on-site.
2. Disconnect the respective meter for the communicator device and reconnect after checking the modbus wiring between the two.
3. Retry the verification test.

1. Check the 'Connection failure' topic and make sure the gateway has a stable connection before retrying the verification test.

This message is displayed when the number of channels defined in the module's configuration does not match the number defined in the application. Essentially, this means that the uploaded configuration is not up to date.

1. Try sending the desired configuration to the module again using the Upload Configuration File command and trigger the verification once more.

This alarm is triggered when the reading of a meter or sensor suddenly drops by an amount greater than the threshold value. For most Cast4All platforms, this threshold is set to 0, meaning an alarm will be created if the cumulative reading suddenly becomes smaller. In principle, this should not happen: a meter reading should only increase.

1. Perform a verification and check if the respective meter can be read out. Refer to the 'Verification failure' topics if an error occurs in the test.
2. Was the meter recently replaced? Use the Restore Meter command to update the meter values and automatically close the alarm.
3. If clear that the meter is responding, the alarm can be closed.

After two days without communication, this type of alarm is generated. The amount of hours before alarm generation is configurable.

1. Check the 'Connection failure' topic to handle this alarm.

This alarm is based on the error codes that are read out from the meter. Some of these error codes automatically result in the generation of an alarm.

1. Perform the verification and check the error code for each channel. Refer to the 'Verification failure' topics to resolve the issue.
2. If there are no error codes for the communicator, the alarm can be closed.

This alarm is generated when no data is coming through, or the data is invalid.

1. Check the validity of the alarm: was the meter powered off?
2. If this alarm is accompanied by a ConnectivityLoss alarm, fix the connectivity first by checking the 'Connection failure' topic.
3. Perform a verification test to check the data validity. If an error occurs, refer to the 'Verifciation failure' topics.

This message is shown for greyed out commands on the communicator element when there is a pending firmware upgrade.

1. Check the Communicator Upgrade tab under the Communicator element.
2. If the most recent command has the 'ToBePlannedMandatory' status, upgrade the firmware of the module using the Other Actions > Uprgrade Firmware Version command and leave the firmware version parameter empty, click confirm.
3. If the most recent command has failed, upgrade the firmware of the module using the Other Actions > Uprgrade Firmware Version command and select the most recent firmware, click confirm.

The PV production test validates the solar energy values. A successful test will not show you any values, but return an OK message.

1. In case the test returns the 'Connection loss', 'Connection timed out' or 'No GPRS Communication' message, check the 'Connection failure' topic to restore the connection with the communication module.
2. The 'Possibly Reversed Wiring' message tells you that the meter was wrongly installed. Change the wiring of the meter to fix this issue and perform the test again.
3. The other error messages tell you that the cumulative value reading of the export energy is not increasing. Make sure the inverter is well connected and properly working.