Troubleshooting non responsive machine- Mach3/Syil x4

**Doddy** · 24-08-2019

Okay, that surprised me.

Can you measure the pin 17 voltage on the parallel port, with respect to gnd (any pin 18 through 25). Again, this is computer-side only.

From the RUN page, slew the X axis left and right (verify with DRO). In one direction you'll get 5V on pin 17, in the other, 0V.

**IhateDoug** · 24-08-2019

Originally Posted by Doddy

Okay, that surprised me.

Can you measure the pin 17 voltage on the parallel port, with respect to gnd (any pin 18 through 25). Again, this is computer-side only.

From the RUN page, slew the X axis left and right (verify with DRO). In one direction you'll get 5V on pin 17, in the other, 0V.

Nothing

Sent from my iPhone using Tapatalk

**Doddy** · 24-08-2019

Okay, so the pendulum of blame swings from BOB to PC.

Now that I know that you're happy patching pins on the parallel port, lets test the actual machine.

With all cables/ribbons on the Syil in place, from the DB25 on the machine (not the PC!), ground the X-Axis "Step" pin (pin 7 to pin 25). I'm assuming here that the pin is pulled high on the BOB. At the point that you ground the pin 7 you should get a single step on the x-axis. Continually breaking/making that connection should introduce further steps. The machine isn't going to launch itself - just move microscopically in one direction on the X-axis.

If that's the case then I think you need to look at the parallel port set-up.

**IhateDoug** · 24-08-2019

Originally Posted by Doddy

Okay, so the pendulum of blame swings from BOB to PC.

Now that I know that you're happy patching pins on the parallel port, lets test the actual machine.

With all cables/ribbons on the Syil in place, from the DB25 on the machine (not the PC!), ground the X-Axis "Step" pin (pin 7 to pin 25). I'm assuming here that the pin is pulled high on the BOB. At the point that you ground the pin 7 you should get a single step on the x-axis. Continually breaking/making that connection should introduce further steps. The machine isn't going to launch itself - just move microscopically in one direction on the X-axis.

If that's the case then I think you need to look at the parallel port set-up.

I thought it mite of been the pc so I got a new one - the pc is new and the problem remains.

I mite wait till tomorrow for that one - most of my gear is on my houseboat. I’m just rummaging around the shed floor atm so mite wait and go get some proper jumper wires and what not from the boat and do it semi properly tomorrow

Sent from my iPhone using Tapatalk

**paulus.v** · 24-08-2019

You said in your first post that
you have:
-replaced the pc (was on it way out anyway)
-checked the ports configured

Did you actually checked that the Port Address of your new pc parallel port matches the one you set in Mach3 (0x378)?

**JAZZCNC** · 24-08-2019

Don't know if this as been asked but did you install Mach3 and the parallel port driver or just copy across your old Mach3 folder.?

**IhateDoug** · 24-08-2019

Originally Posted by JAZZCNC

Don't know if this as been asked but did you install Mach3 and the parallel port driver or just copy across your old Mach3 folder.?

I bought the pc off a computer guy, he set it up with Mach 3 before giving it to me so I’m unsure - in saying that Mach3 shows up in the device manager if that’s an indication of the driver being installed- I mite reinstall Mach 3 just to be sure

Sent from my iPhone using Tapatalk

**Doddy** · 25-08-2019

Originally Posted by JAZZCNC

Don't know if this as been asked but did you install Mach3 and the parallel port driver or just copy across your old Mach3 folder.?

Wow. Jazz may have just jumped back in from obscurity to save the day.

OP/Mitch. For information. I was playing this morning with an old XP machine that I'd been previously using with Mach3 and an ethernet motion controller. I was having exactly the behaviour that you described during my diatribe yesterday - no response from Mach3 to any of the parallel port settings. Using both a DMM and oscilloscope I could get no joy from the parallel port, even though Mach3 was configured for parallel port interface.

I've now re-installed Mach3, ensuring that I included the parallel port driver. Immediately there's life in the system. I can measure the X-DIR signal alternating between 0 and 3.3V (note, not 5V.... I'd turned the printer port from Bi-Directional to EPP mode in the computer BIOS, in doing so the signal level on the parallel port changed from 5V logic to 3.3V logic).

Ignoring the e-stop (as OP described - it can't be obviously disabled - but you can set the port# to 0 which looks to effectively disable it) - I can short pin 17 to pin 11 (configure that for e.g. X-Home) and confirm on diagnostic page that I can toggle this with left/right control.

To summarise - even though the parallel port may be selected within Mach3, unless you install the parallel port driver - my experience is that you're on a hiding to nothing.

**m_c** · 24-08-2019

Originally Posted by paulus.v

You said in your first post that
you have:
-replaced the pc (was on it way out anyway)
-checked the ports configured

Did you actually checked that the Port Address of your new pc parallel port matches the one you set in Mach3 (0x378)?

What OS does the new PC run?

Anything newer than Win7, (aka 8.x or 10), and anything 64bit, won't work with the parallel port.