I am looking for some way to have an active scripting option in the HMI.
We want to make a 3 axis linear mover and instead of needing to reprogram the PLC to change targets i want to have some kind of active script on the HMI.. Like for exampel in a ABB 6-axis robot you have the teach pendant where you can jog to positons and add them to your program.. You also have an open editor where you can edit you code directly in the flex pendant. I want to so something similar so it is easy for the operator to create new programs and edit them.
I think it would be easier to create a generic motion program in the PLC and then have Jog & Add point items on your HMI.
For example, create an array that will hold all of your motion programs (e.g., MotionProgram[x]); the HMI user would just select which motion "recipe" they want to add or edit. For example, an HMI user choses to add a new MotionProgram[3].
For each MotionProgram[x], create multiple steps. If you normal profile needs 20 steps (or positions), create an array of 25 or 30 that will hold all of the motion positions (plus some extra). Now, the HMI user could use jog controls to jog to a point and then "learn" that point. It would look something like this:
MotionProgram[3]
* Step[1] = 123, 456, 789
* Step[2] = 321, 654, 987
* Step[3] = 231, 564, 879
* etc.
No scripting required in the HMI. Just one generic program in the PLC.
My thoughts,
SFW
Yes that was my first idea. To create and array of structs with like 100 position and then make an array of that array to get like 50 programs… I guess that is the easy way and then present 10-15 textfields to see the flow of the program… The important thing is that everything becomes easy and intuitive so operator/programmer easily can modify and add programs from the HMI. This is very important for us since the production changes alot so we need to swich between different setups and also add new setups from time to time…
The eHMI support group here have told us that the „active scripting“ scenario described in the original post currently isn’t possible (sorry).
There are existing requirements for eHMI scripting, but the implementation timeline is unfortunately not know at this stage.
