Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firmware changes for SafetyBox usage with AASD15A #4

Open
aj-whirlybird opened this issue Feb 3, 2020 · 0 comments
Open

Firmware changes for SafetyBox usage with AASD15A #4

aj-whirlybird opened this issue Feb 3, 2020 · 0 comments

Comments

@aj-whirlybird
Copy link

AMC_Interface

  1. Alive signal: Frequency signal that changes its state regularly. The SafetyBox uses this signal to detect if the AMC controller is alive.
  1. S1: E-Stop/Park/Standby input: In future this signal will be controlled by the SafetyBox. Since it can trigger three states: E-Stop, Standby and Park it is not easy to control. This signal toggles between Park and Standby each time it is pressed. The first status is random and depends on the previous E-stop cycles.
    It would be simpler for the control if the first press of the button always led to standby, i.e. when it is released, standby is always preceded.

  2. 2nd E-stop channel: With this signal the control of the drives is extended by a second E-stop channel, which is directly controlled by the SafetyBox.
    This function uses SigIn2 on AASD15A drive.
    Parameter change: Pn053 = 7 (EMG).

  • 2nd E-stop channel: This is the biggest change!
  • Signal: on 25p D-Sub pin 7
  • Hardware: all pin 7 have to connect together
  • Firmware: I hope there's nothing to do.
  • Test: when an E-stop occurs, the SafetyBox sets the S1 input on the AMC controller to LOW and also the pin 7 at every D-Sub connector. This should work without firmware changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant