Messages

1

SmartBOB controllers and dedicated accessories / Re: Connecting Tool Setter Probe to Patriot VFD

« on: October 16, 2025, 01:50:14 PM »

Without more info on your probing device, I can only offer generic advice.

Input terminal 4 on the G540 maps to pin 13 on the DB-25 of the PMDX-411.

If you use a wire jumper on the G540 Main Terminal Block to test this input by temporarily shorting terminal 4 to terminal 12 (power supply ground of the G540) you should be able to control the indicator in the Show Real-Time Input/Output Status window available in the Configure>Plugins>PMDX-SmartBOB control panel window. Once you get this working, proceed to Mach4 and use Configure>Control, select the Input Signals tab. Scroll way down to find Probe 1 in the left column. Then in the Mapping Enabled column next to Probe 1 click to change the Red X to a Green Check Mark. In the Device column click on the box and then the down arrow to list devices. Select SmartBOBUSB. In the Input Name column click in the box and then the down arrow to list available inputs on the SmartBOBUSB. Inputs that have already been assigned to other functions will not be in the list. Select pin 13 assuming it is available. Apply and exit. Now you should be able to see the Probe 1 status in the Mach4 diagnostics screens.

2

SmartBOB controllers and dedicated accessories / Re: PMDX-424/Mach4 Port Autoscan

« on: October 16, 2025, 01:20:59 PM »

Since you are getting USB device acknowledgement from Windows and Device Manager shows the correct virtual Com port it is unlikely that you have a hardware problem.

I have tried installing your Debug profile on build 5036 of Mach4 (current released version) and it runs as expected.

There is a remote chance that something got corrupted in your PMDX plugin install.

It is normal for the plugin install procedure to complain about the SmartBOB being plugged in when you try to install the plugin. You should follow the prompt which tells you to unplug it and try again.

If this does not get you anywhere, you will find more tips about communications problems here:

https://faq.pmdx.com/

Check out the first FAQ link.

If this does not help, I suggest trying a new install to test on a different computer. This install does not need a license installed to do this test.

3

General Discussion / Re: PMDX-1PARPCI driver.

« on: January 13, 2025, 08:07:33 PM »

 
Your issue is getting the drivers for WindowsXP.  Windows7 will automatically load the driver if you ask it to search.


Sorry, I did not realize that Rosewill no longer made the WindowsXP drivers available on their web site.


I have updated our product page to add a download link for a copy of the needed zip file for WindowsXP from our web site.


http://www.pmdx.com/Downloads_/PMDX-1PARPCI-Rosewill-WinXP.zip

4

SmartBOB controllers and dedicated accessories / Re: Using a masso optical encoder with 422

« on: September 24, 2024, 09:07:45 AM »

The A, B, C inputs on a SmartBOB are designed for "TTL" signals in the 0 to 5 volt range. There is protection provided so a 10 volt signal from the Masso encoder will not harm the input, but I am not sure the input will respond.

In order for the A, B, C, input to respond the signal must be capable of producing a valid logic low signal of less than 1.5 volts and the ground reference of the encoder power supply must be connected to the GND terminal of the encoder connector of the SmartBOB. Be careful that there is no conflict in the ground systems.

You can use the Real-Time Input/Output Status panel provided in the SmartBOB plugin configuration tab in Mach4 to verify that the SmartBOB is able to read these signals.

5

SmartBOB controllers and dedicated accessories / Re: What determines the possible values that can be asigned to input and outpuits?

« on: September 24, 2024, 08:57:05 AM »

First thing to understand is that the pins on the PMDX-416 are predefined as either Input or Output type. You must assign output signals to an Output pin type.

The set of Output pins is: 1, 14, 16, 17 (general purpose), and Relay (dedicated). There is also an internal dedicated signal for PWM speed control via a PMDX-407 spindle control module that mounts on top of the PMDX-416. It is configured in the SmartBOB plugin control panel Spindle Config tab, not the Output Signals tab in Mach4.

The set of Input pins is: 11, 12, 13, 15 (general purpose isolated), A, B, C (non-isolated, typically used for encoder inputs), and dedicated isolated inputs for E-Stop and Fault.

You cannot use pin 15 as an Output because it is an Input type pin.

Once any Output pin has been assigned, it will no longer be in the drop down list because only one signal can be allowed to drive a pin due to electrical conflicts resulting from multiple sources fighting to control the pin. If you are trying to use an Output pin and it does not show up in the drop down list, go the the Configure > Control > Output Signals tab and scroll down through the chart to be sure that there is not already a signal trying to use that pin.

Input pins CAN be assigned to multiple signals because each signal can observe the same pin without causing an electrical conflict. This is useful when you want to wire multiple limit or home switches to one signal. If you do this you must not move multiple axes at the same time while homing. You can also define the same input to be observed as a Home signal and as a Limit signal for that same axis.

Also, the list of signals in Mach4 can be confusing because some signals will have both an Input and and Output style functions. For example "Motor 1 Home" is an input signal that Mach4 observes while homing that motor. Depending on your axis assignments that motor could be the X axis. There is also an Output called "X Home" which Mach4 uses to tell an external indicator the status of homing. That Output signal is not required and not often used. I suspect you are confusing the "X Home" output with the signal that you need for Mach4 to monitor your home switch.

6

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX 126 RevB + ESS convert to linux CNC

« on: January 09, 2024, 10:52:06 AM »

The DB-25 port of the 7192TM is electrically and pinout compatible with the PMDX-126.

MESA provides sample configurations such as the Gecko G540 which may prove useful as a starting point for configuring your system.

7

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX-126 + ESS + MACH4 + Encoder inputs

« on: January 09, 2024, 10:49:39 AM »

The PMDX-126 does not need to know the signals are for an encoder, it just has to faithfully pass them on to the ESS which must be configured to utilize the quadrature signals as encoders. Refer to ESS plug-in and documentation for details.

8

SmartBOB controllers and dedicated accessories / Re: PMDX-424, constant PC connection required?

« on: October 29, 2023, 10:02:06 PM »

The PC needs to remain connected to the board during the process of running the G-code because it is Mach4 software that is feeding the motion commands in small bits to the PMDX-424.

The PC does not need to be, and probably should not be, connected to the Internet while running Mach4.

9

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: Outputs Enabled Light

« on: April 07, 2023, 06:37:39 PM »

After phone discussions with Tony, we have concluded that there is indeed something wrong with his care. He is returning it for warranty repair.

Steve Stallings
PMDX

10

General Discussion / Re: 424 relay

« on: February 15, 2023, 08:43:58 PM »

Nothing wrong with using m3/m5 to control torch firing.

It sounds like something is corrupted in your configuration.

Please switch to using direct email support using the email address on our Contact and About Us web page.

Create a "Packaged Profile" and send that to us as an email attachment and we will go from there if the profile looks OK.

11

General Discussion / Re: 424 relay

« on: February 15, 2023, 03:10:49 PM »

Did you mean after the first m5? A g5 is not a valid G-code command?

12

General Discussion / Re: 424 relay

« on: February 15, 2023, 07:50:22 AM »

Does the G-code program simply continue running without turning the spindle off, or does the program actually hang?

Is the m5 command the last line of code in the program?

13

General Discussion / Re: Quick Fusing a 424

« on: January 26, 2023, 05:12:17 PM »

Fuses are for protecting circuits from overload due to current. The PMDX-424 has an internal self resetting "polyfuse" to interrupt the current that it draws from the 120 VAC mains if there is a fault within the PMDX-424 or if something overloads one of its outputs.

Having a fuse in the 120 VAC power line feeding the PMDX-424 is useful if you are concerned about short circuits in your wiring harness.

Protection from power surges would require a "surge arrester" which works by clamping excess voltage, not a fuse. It is common to find 120 VAC outlet strips with built in surge arresters. Such a power strip may be useful to protect the PMDX-424, and also the computer and monitor associated with the system.

Stand alone surge arresters are available, but they typically cost more than an outlet strip with an internal surge arrester.

Here is one example of a stand alone surge arrester:

https://www.ebay.com/itm/175581200914

14

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: 107 Pin Options

« on: January 12, 2023, 02:01:51 PM »

If you do not need to run your spindle in reverse you can set the PMDX-107 to Run/Dir mode (Config switch 3) and do not connect the Dir output of the PMDX-107 to the VFD. This will allow you to use pin 14 for other purposes without disturbing the VFD.

15

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX 126 J11 GND TO MACHINE

« on: November 16, 2022, 10:24:09 AM »

The "GND" terminal on J11 is isolated from the computer interface by the PMDX-126, so the PMDX-126 and computer are protected. This signal is intended to be safe to use with the safety ground and/or chassis of a CNC machine.

Other parts of your machine wiring that also connect to the "GND" terminal of J11, J12, and J13 of the PMDX-126 will all be connected to the same circuit. Normally the items connected to these "GND" terminals are designed to also be safe to connect to the safety ground and or chassis of the machine, but I wanted to mention that for completeness of this response.

If you are using a simple isolated probe plate connected to the "E" input on the PMDX-126, your cutter/probe is expected to complete the circuit back to the "GND" terminal. While many machines will work by using the chassis to complete the circuit, I recommend using an "alligator" clip on the cutter/probe with a wired connection back to one of the "GND" terminals for more reliable operation.