On C80 and C50 HW version is not backwards compatible with Terminal LX (Workaround)

Problem: When reprograming a C50 and HW version 1.1.8/1.2.0 is selected and Terminal LX version is 1.0.1/1.1.1 /1.1.2, then the terminal is stuck in the loading screen. Basically the HW version 1.1.8/1.2.0 is not backwards compatible with older terminal versions (1.0.1/1.1.1 /1.1.2). The termonal is temporarily unresponsive with terminal USB port and Visu not showing. HW 1.1.7 still works with the older LX versions (1.0.1/1.1.1 /1.1.2.). The new IO data points “Terminal Memory Total” and “Terminal Memory Available” introduced in HW 1.1.8, causes this issue.

If you don’t know this issue it can cause major confusion on-site when updating a C50 or C80. Possibly also T-series panels.

Fixing the Stuck Terminal: Downgrade the HW version and do a USB installation. LX version cant be updated in this state as terminal USB does not work anymore. After the HW downgrade the LX version can be updated, then update the HW version and do USB install.

Workaround 1 : User always has to update terminal LX first and then the HMI program. This is not fool proof.

Workaround 2: Remove the new IO datapoints “Terminal Memory Total” and "Terminal "Memory Available from the HW file (HWx) . Be sure to create a new HW version Ex. make 1.2.0 a new version 1.2.1 with the removed IO data points. HW version file can be found in directory “C:\BRAutomation\AS412\AS\Hardware\Modules\PPC50xxxxx”

Make new version

Delete IO Data points

Use new HW version

I hope this helps someone! Feel free to ask a question if anything is unclear.

1 Like

Just to make it clear: the Hwx file is of course backward compatible with all terminal LX versions except the first one, 1.0.1. I think it is even documented, but I do not have time to search for it.

Just two points from me:

  • LX image 1.0.1 is the first version from 2019, which was burned to the first series of T50. Now we have 1.3.2.
  • If you still do active developing on this old hardware with the old version of LX, it makes absolutely no sense to update the Hwx file and not update the LX image (because of security fixes, bug fixes, etc.).

But I agree It can be confusing, so thanks for sharing :slight_smile:

1 Like

Thank you for adding these additional points. This is applicable to C50s and C80s that have been in the field for a time (older than April 2023). It could possible also affect the T-series terminals. This unexpected issue arises when a doing a maintenance update at the client.

This issue occurs on LX 1.0.1/1.1.1 and 1.1.2. So not only LX1.0.1. I updated the original post to include the exact LX Version.

I am not aware that this is documented. I could not find anything in AS4 help. That is the reason why I posted this workaround

1 Like