Hello Guest it is April 25, 2024, 08:21:53 PM

Author Topic: Screen Script Error  (Read 817 times)

0 Members and 1 Guest are viewing this topic.

Screen Script Error
« on: November 06, 2021, 11:05:07 AM »
So I get this whenever I change mach 4 configuration:

The associated code is here:

It's part of the SigLib{ structure.

This watches the error line from my motor drivers, and is supposed to stop everything if a driver issues an error.

The machine works fine; Mach only complains when I save configs.

Offline DazTheGas

*
  •  778 778
  • DazTheGas
    • View Profile
Re: Screen Script Error
« Reply #1 on: November 06, 2021, 12:57:25 PM »
It looks to me that its cant find a function called eStop()

DazTheGas
New For 2022 - Instagram: dazthegas
Re: Screen Script Error
« Reply #2 on: November 06, 2021, 01:26:39 PM »
...but it found the first instance, right above it...

Offline jbuehn

*
  •  101 101
    • View Profile
Re: Screen Script Error
« Reply #3 on: November 08, 2021, 12:30:08 PM »
Does input 10 ever change state though where it's function would have been called?
Re: Screen Script Error
« Reply #4 on: November 08, 2021, 12:42:02 PM »
Theoretically it changes state if the motor driver errors out via losing steps or failing to reach a commanded position.

That's... hard to test, for obvious reasons.

But I'm not getting the error because of a state change (which if the function was truly undefined would be fair ball if it complained). Instead, I get the error only when I edit the configuration and save it.

If I just run the machine, I never see the error.

Offline jbuehn

*
  •  101 101
    • View Profile
Re: Screen Script Error
« Reply #5 on: November 08, 2021, 01:58:42 PM »
When you say edit the configuration, that's the Configure > Control menu?
Re: Screen Script Error
« Reply #6 on: November 08, 2021, 02:48:00 PM »
When you say edit the configuration, that's the Configure > Control menu?

Ayup.

Offline jbuehn

*
  •  101 101
    • View Profile
Re: Screen Script Error
« Reply #7 on: November 08, 2021, 06:10:03 PM »
I bet if you commented out the eStop() in input 9's function you'd then see it complain it can't find eStop() in input 10's function.

If you have logging opened and started when you enter/exit the configuration, you can watch all the signals get forced HIGH/LOW (on exit). It's calling input 9's function and erroring out before it calls input 10's function, because Mach is going through the signal ID's in order.

Do you have a global function called eStop?