BAJ
Member
In the past if I needed to change the jog speed every scan I used two identical MAJ blocks with a toggle bit to switch which one is "on" and which one is resetting every-other scan to satisfy the off-to-on edge triggering of the MAJ.
I just came across someone else's code and see they are doing an unlatch coil (OTU) of the MAJ Motion Control instance variable ".EN" right before calling the MAJ - does this work to create the edge trigger? It would be cleaner than my way if it does.
It's been my understanding the MAJ block needs to be solved with the input pin false to see the edge transition.
I only have access to the offline copy of the program and no motion axis to test with in my office. Any input will be appreciated.
Thanks,
-Brad
I just came across someone else's code and see they are doing an unlatch coil (OTU) of the MAJ Motion Control instance variable ".EN" right before calling the MAJ - does this work to create the edge trigger? It would be cleaner than my way if it does.
It's been my understanding the MAJ block needs to be solved with the input pin false to see the edge transition.
I only have access to the offline copy of the program and no motion axis to test with in my office. Any input will be appreciated.
Thanks,
-Brad