Troubleshooting for Mitsubishi Electric Point Manager

Trouble	Troubleshooting Method
Cannot connect to devices.	Check the service startup status of Mitsubishi Electric FA in Workbench, and if it is not started, start it.
Check whether each parameter in the device properties is correctly compared with the actual connection route.
Execute the Communication test to see the error message.
When the connected device communicates with multiple MELSOFT (Mitsubishi Electric's engineering software products such as GX Works3) by TCP, the same number of settings as the connected MELSOFT (MELSOFT connected device settings) need to be set in the parameter settings of the connected device. Try also: Set a longer timeout. Connect to the device by using different communication path from the other MELSEC devices. For details, refer to the manual of the connected Mitsubishi Electric product.
Tag data is not updated.	Check the service startup status of Mitsubishi Electric FA in Workbench, and if it is not started, start it.
Check if the device is activated, and if it is not activated, activate it.
Check the communication error event with AlarmWorX64 Viewer and take corrective action. A description of error event may contain an error code returned by each device. Please refer to the manual of each Mitsubishi Electric device for details. See GenEvent Server.
Cannot write value to tag data.	Check if the tag in Tag Group Properties is assigned to a read-only register.
If there is an issue that is different from the examples mentioned above or if there is an issue that cannot be solved by the troubleshooting method for the issues mentioned above.	Get the log of Mitsubishi Electric FA with TraceWorX and check the contents. See TraceWorX64.

Cannot connect to devices.

Check the service startup status of Mitsubishi Electric FA in Workbench, and if it is not started, start it.

Check whether each parameter in the device properties is correctly compared with the actual connection route.

Execute the Communication test to see the error message.

When the connected device communicates with multiple MELSOFT (Mitsubishi Electric's engineering software products such as GX Works3) by TCP, the same number of settings as the connected MELSOFT (MELSOFT connected device settings) need to be set in the parameter settings of the connected device.

Try also:

Set a longer timeout.
Connect to the device by using different communication path from the other MELSEC devices.

For details, refer to the manual of the connected Mitsubishi Electric product.

Tag data is not updated.

Check the service startup status of Mitsubishi Electric FA in Workbench, and if it is not started, start it.

Check if the device is activated, and if it is not activated, activate it.

Check the communication error event with AlarmWorX64 Viewer and take corrective action. A description of error event may contain an error code returned by each device. Please refer to the manual of each Mitsubishi Electric device for details. See GenEvent Server.

Cannot write value to tag data.

Check if the tag in Tag Group Properties is assigned to a read-only register.

If there is an issue that is different from the examples mentioned above or if there is an issue that cannot be solved by the troubleshooting method for the issues mentioned above.

Get the log of Mitsubishi Electric FA with TraceWorX and check the contents. See TraceWorX64.

Troubleshooting for Mitsubishi Electric FA