AXBB not found

[NB Forrest]

I have a DIY table using a Hypertherm 30XP. I have been having problems with the pierce delay but only for the second cut. The torch will move about 1/2 inch before the torch turns on. I was changing the SheetCam settings without much results when when I opened Mach3 I got the message AXBB CNC motion Controller Error AXBB not found check the connection. What does that mean? What connection?

AXBB.png

[acourtjester]

Some electronics need a "plug in" file loaded so they can work with Mach. You may look at the image below and see a similar massage and the plug in menu. Check the menu to see if your needs to be configured for Mach to use/see it.

mach file.JPG

mach file 2.JPG

[NB Forrest]

That was it exactly! I didn't notice I have a UC400ETH (it was actually you that inspired me to use it) that I use and it is always automatically selected but somehow it was not selected. I'm still having the same second cut problem. I had it almost working at one point but still not good enough so I'm back at trying to fix it. I'm going to call Hypertherm tomorrow and ask them if there is something in the Hypertherm 30xp causing the delay.

[acourtjester]

I have seen this posted here before, but don't remember what the fix was. Have you checked the air pressure to the plasma, if to low it may not fire until line pressure is back up from the last cut. I put over 110 PSI to the back of mine, You may want to put a pressure gauge at the back of the plasma to check the pressure as it cuts. Not sure about the 30XP but my 65 will not fire under 80 PSI to the back of the plasma.

[NB Forrest]

The air pressure is an issue with the Hypertherm but I have insured I have about 100 psi and It cuts wonderfully after the torch moves about 1/2 inch. BTW I fixed the ohmc sensor problem by modifying a drag shield and I soldered a wire with a connector to attach to my ohmic sensor and it work beautifully. But back to the delay problem, I have noticed while using my 30XP by hand there is a delay from the time I squeeze the trigger to the time the torch activates and it is always after the first cut. That is why I am calling Hypertherm tomorrow morning to tell them the issue.

[acourtjester]

What is the time between end of cut and you wanting to cut again? Hypertherm runs the air flow to cool the tip, not sure if that needs to end before a next cut can be made.

[NB Forrest]

I'm not sure. I haven't measured it but guess it is no more than 5 seconds. In fact I just went to measure the time between cuts and now my z axis is not responding at all. The controller is still green, the wires going to the motor are snug but I haven't taken the cover to my torch lifter off but now that is what I'm about to do and see if something has come lose from the stepper motor.

[acourtjester]

Are you using home/limit switches maybe you tripped one??

[NB Forrest]

I have a floating head for a limit switch but the diagnostics screen is clear and mach3 shows it moving but it is not moving. Mach3 thinks everything is fine.

[acourtjester]

the thing with Mach 3 is you can tell it to move, but since there is no feed back. It shows it moving but the motors do not move, DRO will show moving by changing the numbers. If you have a way to switch the motor cables between motors you can see if something died, this is just for testing.
If you are using drivers like these (black boxes) you can switch the connecters between them for testing. Either the input from the BOB or outputs to the motors. But only with power off to them. Now don't switch inputs if the voltage in is different. I used 2 type one was 36 volts in the other were 60 volts in

DSCN4802.JPG

[NB Forrest]

Okay. I swapped the Pulse and direction for the y axis with the Pulse and direction for the z axis. Now the z axis moves by jogging the y and the y axis doesn't move jogging the z. So I suppose that tells me the z axis motor is good but now does that point me to the BOB? How do I test it?

[acourtjester]

In the software you can change the pins for step (pulse) and dir between the motors. That will tell you it the BOB is the problem. With the 400 you have 2 posts outputs where you can use 2 BOBs to get more pins to use, be sure you do not change the port pins in the software. If you only have one BOB and you select the wrong post that motor will not work. All motor step and dir and port pin need to be on the correct port.

[NB Forrest]

Port 2.png

I changed the port to port 2 for the 400 and nothing changed for the z axis.

Port 2.png

[acourtjester]

I think you miss-understood what I was saying. I just wanted you to know about the 2 posts. Just in case something had changed in the software post configuration. Now you can change ports by switching the cable from the port you using to the other. This would check the output of the 400 it case something blew. These are just troubleshooting things to find where the problem is. You can have software signals go bad, the BOB output, a driver or motor. Having flexibility of switch things is a plus to find what is the problem. And there is also the wiring, bad connection or breakage.
Once you can see which path is bad then you try to locate the reason.