Hello Guest it is April 18, 2024, 05:03:47 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - japolta

Pages: 1
1
Thanks for the reply.
I neglected to say that increment jog is in effect.  The axis only moves the discreet amount. It works fine when being debugged. I have found numerous examples of dooembutton (310) being executed as script usually jogging the lathe axis a discreet amount.  So I still remain confused.
BR549, I should have been clearer, I stylized the logic to keep the example simple.  You are correct.

2
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??

3
I love the plugin!!!
Help though please....
I am running an older XP system.   I cannot get any changes I make to the joypad buttons to stick.  For example,  I followed the manual and changed BW (w SR) to be executed script.  The configuration goes to user defined and I save it.  I have been doing this with MAch 3 active and then restart mach3.  The change doesn't stick and the default 3 axis buttons retain.  I must be missing something simple.  Any insight would be appreciated.
Thanks.

Pages: 1