Plasma with pmdx 411 and gecko g540

[hutch77]

I am trying to replace an old computer that is dead was running mach 3 with a gecko g540. I have mach 4 and a pmdx 411 trying to make it all work together is a bit over my head. I have the motors working everything moves correct but I cant get the plasma to turn on.

[Steve Stallings]

We will need a bit more information before we can be of much help.

Did this electrical configuration work for you with Mach3?

Where and how do you have the torch firing circuit wired?

If this is likely to be a Mach4 configuration issue, please generate
a packaged profile using the  Help > Support > Package Current Profile
and send us the resulting file. You can send by email or post it here.

[Steve Stallings]

I am assuming that you are using M3 and M5 to control the torch.

You need to configure Mach4 to drive one of the pins that controls the
relay output from the G540 that you are using to fire the torch.

Go to:  Config > Mach > Output Signals

Scroll way down until you find "Spindle ON" and configure that to be
Enables, select SmartBOB-USB as the Device, and then select  Output
Name to be the Pin # as needed.

The Proma SD should work with Mach4, but the Proma 150 uses Up
and Down output signals and expects Mach to generate step signals
for the Z axis. Currently Mach4 does not do this internally because
the plan was for the device to take over this function. Currently
PMDX does not do this, and to the best of my knowledge other
common devices also do not do this yet.

Looking at the profile that you provided, you have both the SmartBOB
and the Simulator enabled. Please disable the Simulator.

I also see that you have Output 1 set up to talk to Pin 17 on the
SmartBOB. Perhaps this is what you thought would fire the torch.
Output 1 is only going to respond to code in a Macro. See above
where I described setting up Spindle On to control the torch.

[hutch77]

Thank you that worked.
I have one other question with the same setup I have 2 motors on my x axis. The 2nd motor is plugged into the (a) axis slot on my gecko. When I turn it on as a slave in mach 4 the machine will move one way until I let off but then wont move on the x axis again until I disable and then re enable it. It does this even if the motor isn't plugged into the gecko. On mach 3 it looks like you slave the axis not the motor is this correct and how do you set mach 4 to do the same.

[Bob at PMDX]

Mach3 used different terminology (everything was an "axis").  Mach4 makes the distinction between "motors" and "axes".  To slave the G540 "A" motor to the "X" motor, on your "X" axis the "Axis Mapping" tab should look like the attached image.  And I am presuming that you have the direction reversed for your slave motor *IF* your gantry requires that.

Now on to the jogging issue.  Are you jogging by clicking the mouse on the jog buttons?  If not, how are you initiating the jog motion?  When you press the jog button, the "Cycle Start" button will become grayed out.  When you release the jog button the "Cycle Start" button *should* turn bright green again.  Does it do this when you can no longer jog the X axis?  Can you jog any of the other axes?

I would like you to create a plug-in debug log for me to capture this.  The general instructions are in item (4) here:
    http://www.pmdx.com/PMDX-Forums/index.php?topic=75.0

Enable the debug log as shown, exit Mach4.  Restart Mach4 and try to replicate this issue.  Once the X axis fails to respond, try to jog one of the other axes.  Then disable the log file and create a profile package as described in the FAQ.  You can either upload that to this forum thread or email it to me at bob at this domain.

Bob

[hutch77]

I am using the mouse and the jog buttons. The motor is reversed. The other axis work fine. The cycle start does not turn bright green after I jog it once. When I do jog it I can go as far as I want and it works as long as I don't stop once I stop it will not go again.

[Bob at PMDX]

I downloaded your profile on Friday (thanks).  While I can not yet replicate the issue you are seeing, I do see messages in the debug log file that hint at what it going on.  I'll post back here when I have more information, or want you to run more tests.

Bob