Loss on information about homedX variables upon IOC restart about galil

[motorapp]

Hello,
The reason for the error is related to bad communication happening with the controller.

Inspecting the provided logs, the firmware on the controller is too old.
Please update the firmware to version 1.2F (preferred) or above, then try again.

[motorapp]

Hello,
The cause of the reported issue is communication problems with the controller that is caused by firmware that is too old. A minimum of firmware 1.2F is required for that controller model.

Providing further information below.

1. Yes, the Galil driver can set homedA-H to 0 during the setup of the required variables on the controller, but the process is not completed successfully in the reported case due to communication issues, due to firmware issues. The driver will decide to set up the variables on the controller if any of the following is true:
   A). The user has specified burn program to EEPROM in GalilStartController call AND the program specified was downloaded to the controller successfully because it was different from what was on the controller.
   B) The controller doesn't know the homedA-H variable
   C) The controller doesn't know the commutation initialized variable cinitA-H
   To set up the variables on the controller the driver does the following.
   A) Backup value of cinitA-H, backup value of homedA-H
   B) Set variables to desired power on value (homedA-H=0, CINITA-H=0)
   C) Burn variables to EEPROM
   D) Restore cinitA-H, homedA-H value that was captured in step A) above
2. The firmware below 1.2F on this controller has many known bugs. The minimum firmware is 1.2F. Firmware 1.2F assists greatly with an issue where ethernet traffic locks up the controller causing the red LED to come on. However, specific network configuration is most often required too. Please refer to the networking guide in the git repository documentation folder.
3. No. With given firmware 1.1d additional attempts will also fail.
   The PV $(P)START_STATUS can be used to see if the code specified started ok. It is checked only at IOC start.
   The driver only sets the controller program and variables if necessary.
   Once the specified program and variables are burnt to EEPROM, the driver won't do the program and variable set
   up again, until it's altered by the operator.

If you'd like to discuss your project further, please email me at [email protected]