Guest
Show Posts
1
VB and the development of wizards / observed doOEMbutton anomaly in vb script editor
« on: March 07, 2013, 10:23:21 PM »
When executing an IF statement triggered by depressing a button on the joypad, DoOEMbutton(310) does not execute. However when using the debuging feature in Mach 3's VB scripting it does! I have placed a message statement in the statement so I know the logic is getting to the execution of DoOEMbutton(310), but axis simply doesn't move.
Example:
If True DoOEMbutton(310) : message "increment jog"
When debugging the axis jogs and the message is displayed in the status line. When using the external trigger, only the message is displayed and the axis does not move.
This programming approach works for other dobuttion (i.e. the dobutton combination that does REF HOME ALL). Only the axis jog buttons are unresponsive. I've got to be missing something here...a timing issue?? Even the most simple macro just executing a dooembutton(310) does the same thing -- it isn't the IF then logic messing this up.
Simple example:
DoOEMbutton(310) 'one line only no other programing
I'm sure the answer will be apparent to someone, but I'm pulling my hair out.... People use these dobuttons all the time in their programming to index lathes, but no one reports any problem and I'm not seeing them use any special conditions -- they just say "doOEMbutton(310)".
Are all dobuttons not created equal??
Example:
If True DoOEMbutton(310) : message "increment jog"
When debugging the axis jogs and the message is displayed in the status line. When using the external trigger, only the message is displayed and the axis does not move.
This programming approach works for other dobuttion (i.e. the dobutton combination that does REF HOME ALL). Only the axis jog buttons are unresponsive. I've got to be missing something here...a timing issue?? Even the most simple macro just executing a dooembutton(310) does the same thing -- it isn't the IF then logic messing this up.
Simple example:
DoOEMbutton(310) 'one line only no other programing
I'm sure the answer will be apparent to someone, but I'm pulling my hair out.... People use these dobuttons all the time in their programming to index lathes, but no one reports any problem and I'm not seeing them use any special conditions -- they just say "doOEMbutton(310)".
Are all dobuttons not created equal??