91
SmartBOB controllers and dedicated accessories / Re: Limit Switches Active High
« on: May 29, 2017, 08:41:34 PM »
I would agree that rewiring is the best solution in your case.
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.
92
SmartBOB controllers and dedicated accessories / Re: Stop button on mach4 and 424 board
« on: May 29, 2017, 08:39:44 PM »
This is normal operation.
Stop is not intended to allow you to resume operation. For that purpose
you should use Feed Hold. You can then use the Spindle ON/OFF button
to stop the spindle to clear chips or whatever, and then use it again to
start the spindle again before you hit Cycle Start to resume.
Stop is not intended to allow you to resume operation. For that purpose
you should use Feed Hold. You can then use the Spindle ON/OFF button
to stop the spindle to clear chips or whatever, and then use it again to
start the spindle again before you hit Cycle Start to resume.
93
SmartBOB controllers and dedicated accessories / Re: Mach4 touch function with 424 board
« on: May 29, 2017, 08:36:21 PM »
When you say that Mach4 is seeing the changes, are you looking at the
signal called PROBE on the Machine Diagnostics page? Probe 1, Probe 2,
and Probe 3 are not currently supported in the SmartBOB plugins.
If you are seeing the Probe indicator light up when you activate the
probe or touch the touch plate, then the SmartBOB is working and
Mach4 is configured to look at it correctly.
Is the window that you are using for touch labeled "TouchOff UI" in the
bar at the top of the window? If not please indicate what touch facility
you are using, and what build of Mach4.
Is Mach4 in the enabled state, i.e. the button in the lower left is Red
and says Disable?
Is the "Code Probe Options" in the "TouchOff UI" window set to G31?
When you trigger the probe or touch the plate, the box in the lower
center of the "TouchOff UI" window should light up and say "Selected
Probe Is Currently Active". If this does not happen, something must
be wrong with the Mach4 install or configuration and you should
consult the Mach Support forum for assistance.
signal called PROBE on the Machine Diagnostics page? Probe 1, Probe 2,
and Probe 3 are not currently supported in the SmartBOB plugins.
If you are seeing the Probe indicator light up when you activate the
probe or touch the touch plate, then the SmartBOB is working and
Mach4 is configured to look at it correctly.
Is the window that you are using for touch labeled "TouchOff UI" in the
bar at the top of the window? If not please indicate what touch facility
you are using, and what build of Mach4.
Is Mach4 in the enabled state, i.e. the button in the lower left is Red
and says Disable?
Is the "Code Probe Options" in the "TouchOff UI" window set to G31?
When you trigger the probe or touch the plate, the box in the lower
center of the "TouchOff UI" window should light up and say "Selected
Probe Is Currently Active". If this does not happen, something must
be wrong with the Mach4 install or configuration and you should
consult the Mach Support forum for assistance.
94
SmartBOB controllers and dedicated accessories / Re: 424 and 104 Relay board not responding to mach4
« on: May 29, 2017, 07:18:23 PM »When I configure a PMDX-424 and PMDX-104 and install your profile, I cannot
duplicate your results.
Your configuration for the Mist and Coolant relays is logical and correct.
Mist and Coolant using your profile activate relays as expected. The relays
are off while Mach4 is disabled, and respond to M7, M8, and M9 in the
correct manner when Mach4 is enabled. This was confirmed by both the
LEDs on the PMDX-104 board and by continuity measurements of the relay
contacts using an Ohm meter.
Your configuration for spindle control is not logical considering that you
have a PMDX-407 spindle control board.
There is no need for an output driven from the Mach4 "Spindle On" output.
This function occurs automatically in response to the messages from the
Mach4 API to the PMDX SmartBOB plugin. Spindle On will result in the
small solid state relay on the PMDX-407 being activated without needing
to provide an dedicated Spindle On signal from Mach4.
The Spindle Reverse output from Mach4 should be configured to control
the Relay on the PMDX-424. The Run signal from the J2 of the PMDX-407
should be wired to the Com of the Relay. The N/C of the Relay should connect
to the Forward terminal of your VFD. The N/O of the Relay should connect
to the Reverse terminal of your VFD. The Com from J2 of the PMDX-407
should connect to the terminal of the VFD that activates the Forward
or Reverse run mode of the VFD.
95
Parallel Port breakout boards, motherboards, and dedicated accessories / Re: G214 with PMDX-126
« on: May 26, 2017, 09:10:54 PM »
The G214 needs both GND and +5V to operate all the signals of its interface.
You can use PCgnd and PC+5V from the J1, J2, J3, and J4 terminal strips of
the PMDX-126 for this purpose.
The ENABLE input of the G214 will allow the drive to run when there is no
connection. When you want to "freewheel" the motor, you can either tie the
ENABLE input to PCgnd or use a logic signal to drive it low. The outputs on J5
or J6 are suitable for this function.
The RESET input is similar to the ENABLE input, but it will also reset the
microstep counters to the same state as initial power up.
The FAULT output is a totem pole output. This means that you will
need to add a diode in series before you can combine the signal
from several drives into the one ERR input on the PMDX-126.
Each diode should have its cathode connected to the FAULT signal
of the G214 drive. All of the anodes could connect together and to
the ERR- on J13 of the PMDX-126.
The ERR+ from J13 of the PMDX-126 should connect to the PC+5
on J5 or J6 of the PMDX-126.
The return path will be through the G214's OptoIsolator Ground
that is already connected to PCgnd on the PMDX-126.
The diodes can be any switching diode rated for 5 volts or more.
You can use PCgnd and PC+5V from the J1, J2, J3, and J4 terminal strips of
the PMDX-126 for this purpose.
The ENABLE input of the G214 will allow the drive to run when there is no
connection. When you want to "freewheel" the motor, you can either tie the
ENABLE input to PCgnd or use a logic signal to drive it low. The outputs on J5
or J6 are suitable for this function.
The RESET input is similar to the ENABLE input, but it will also reset the
microstep counters to the same state as initial power up.
The FAULT output is a totem pole output. This means that you will
need to add a diode in series before you can combine the signal
from several drives into the one ERR input on the PMDX-126.
Each diode should have its cathode connected to the FAULT signal
of the G214 drive. All of the anodes could connect together and to
the ERR- on J13 of the PMDX-126.
The ERR+ from J13 of the PMDX-126 should connect to the PC+5
on J5 or J6 of the PMDX-126.
The return path will be through the G214's OptoIsolator Ground
that is already connected to PCgnd on the PMDX-126.
The diodes can be any switching diode rated for 5 volts or more.
96
Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX 126 REV C, k1 k2 relays.
« on: May 15, 2017, 12:14:07 AM »
Both the K1 and K2 relays will default to off in the power up state
and also any time an E-Stop event happens. You would normally
use the N/O contacts to switch the power to your load.
The power supply for the 70 VDC to the motor drivers does not
need to be controlled by the host computer because a stepper
motor will not run away if the host crashes, and because the
PMDX-126 will prevent step pulses to the drivers if an E-Stop
happens.
You do not normally use a relay to switch the mains power
into a VFD because of the high inrush current at the mains
input, and because the VFD will provide low current controls
inputs suitable for turning the spindle on and off. Better yet
you can add a PMDX-107 and control the VFD from that and
also gain variable speed control from G code.
If the H2O pump is for cooling the spindle, I would recommend
that it not rely on an independent control signal as running
the spindle without cooling is a very bad thing. You can configure
the PMDX-1226/107 to control a relay at the same time that it
controls the VFD. Read the section about Multi-Mode usage of
the relays. Or if you do not use a PMDX-107 then use the large
K1 relay to control both the power to the VFD and the cooling
pump.
In any case, the small K2 relay's N/O contacts, with the MOV
connected to the N/O terminal, can be used to control the 3A
load for the dust collector.
and also any time an E-Stop event happens. You would normally
use the N/O contacts to switch the power to your load.
The power supply for the 70 VDC to the motor drivers does not
need to be controlled by the host computer because a stepper
motor will not run away if the host crashes, and because the
PMDX-126 will prevent step pulses to the drivers if an E-Stop
happens.
You do not normally use a relay to switch the mains power
into a VFD because of the high inrush current at the mains
input, and because the VFD will provide low current controls
inputs suitable for turning the spindle on and off. Better yet
you can add a PMDX-107 and control the VFD from that and
also gain variable speed control from G code.
If the H2O pump is for cooling the spindle, I would recommend
that it not rely on an independent control signal as running
the spindle without cooling is a very bad thing. You can configure
the PMDX-1226/107 to control a relay at the same time that it
controls the VFD. Read the section about Multi-Mode usage of
the relays. Or if you do not use a PMDX-107 then use the large
K1 relay to control both the power to the VFD and the cooling
pump.
In any case, the small K2 relay's N/O contacts, with the MOV
connected to the N/O terminal, can be used to control the 3A
load for the dust collector.
97
Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX 126 REV C, setup with AM882 Fault Detection
« on: May 14, 2017, 11:38:43 PM »
Most motor drivers including the AM882 units describe their signal
response in terms of rising or falling current flow into the optocoupler.
For Mach configuration you should leave it set to a red X in the active low
column in the configuration chart, and wire the output signal from the
PMDX-126 to the PUL+ and PCgnd to PUL- so that a signal transitioning
from a logic low to a logic high will result in rising current into the optocoupler.
This corresponds to Common PC_gnd. Other methods will also work, but I
chose to explain this one because it is least confusing.
The input signals on J12 do have pull-up resistors to +5 volts. You can connect
your signals from a normally closed switch from the input to Gnd and leave
the Mach configuration at the default red X for Active Low (meaning active high).
response in terms of rising or falling current flow into the optocoupler.
For Mach configuration you should leave it set to a red X in the active low
column in the configuration chart, and wire the output signal from the
PMDX-126 to the PUL+ and PCgnd to PUL- so that a signal transitioning
from a logic low to a logic high will result in rising current into the optocoupler.
This corresponds to Common PC_gnd. Other methods will also work, but I
chose to explain this one because it is least confusing.
The input signals on J12 do have pull-up resistors to +5 volts. You can connect
your signals from a normally closed switch from the input to Gnd and leave
the Mach configuration at the default red X for Active Low (meaning active high).
98
SmartBOB controllers and dedicated accessories / Re: Limit Switches Active High
« on: May 14, 2017, 11:28:51 PM »
Perhaps you are confusing "active high" with "normally closed".
These are related, but not the same concept.
It is desirable to use a normally closed circuit to sense home or limit
switches because a failure of connectors or wiring will result in the
system stopping in a safe fashion. Normally open sensors will also
work, but the wiring failure fail safe advantage is lost.
The inputs of the PMDX-424 interface board is internally pulled to +5
volts by a resistor. If you connect a normally closed switch between
the input signal and ground, the signal is normally low. Therefore
you would configure Mach for "active high" operation. The is the
default setup with a red X in the box labeled active low, indicating
that active low operation is not being requested. Yea, I know, it
is confusing.
If you have proximity sensors things can be more complicated. These
sensors can be normally open (most common) or normally closed,
and they can be NPN (ok for the PMDX-424) or PNP (requires use of a
PMDX-105 for level conversion).
These are related, but not the same concept.
It is desirable to use a normally closed circuit to sense home or limit
switches because a failure of connectors or wiring will result in the
system stopping in a safe fashion. Normally open sensors will also
work, but the wiring failure fail safe advantage is lost.
The inputs of the PMDX-424 interface board is internally pulled to +5
volts by a resistor. If you connect a normally closed switch between
the input signal and ground, the signal is normally low. Therefore
you would configure Mach for "active high" operation. The is the
default setup with a red X in the box labeled active low, indicating
that active low operation is not being requested. Yea, I know, it
is confusing.
If you have proximity sensors things can be more complicated. These
sensors can be normally open (most common) or normally closed,
and they can be NPN (ok for the PMDX-424) or PNP (requires use of a
PMDX-105 for level conversion).
99
SmartBOB controllers and dedicated accessories / Re: PMDX-424 SmartBob No Green LED
« on: May 14, 2017, 10:50:42 PM »
This board was returned for warranty repair and was found to
indeed have a problem. Amazingly it was just the circuit that
drove the LED. The board otherwise functioned as expected.
It has been fixed and returned to the customer under warranty.
indeed have a problem. Amazingly it was just the circuit that
drove the LED. The board otherwise functioned as expected.
It has been fixed and returned to the customer under warranty.
100
SmartBOB controllers and dedicated accessories / Re: PMDX 424 help
« on: May 14, 2017, 10:42:34 PM »
This indeed sounds like a setup issue, but in hardware.
Your solid state relays should be connected from signal output to + on SSR,
and - on SSR to PCgnd. If you have them connected from PC+5 to + on SSR
and - on SSR to signal, this will cause the sort of inversion that you describe.
Your solid state relays should be connected from signal output to + on SSR,
and - on SSR to PCgnd. If you have them connected from PC+5 to + on SSR
and - on SSR to signal, this will cause the sort of inversion that you describe.
101
SmartBOB controllers and dedicated accessories / Re: G31
« on: May 14, 2017, 09:05:05 PM »
That is great to hear.
Thanks for your patience.
Thanks for your patience.
102
SmartBOB controllers and dedicated accessories / Re: What post configuration should I be using.
« on: May 14, 2017, 09:03:31 PM »
My only guess is that your Mach4Hobby configuration is corrupted.
You could try re-installing Mach4, but be sure your profile is named
something other that the defaults, such as Mach4Mill, and make
a packaged profile so you can re-import your old configuration.
You could try re-installing Mach4, but be sure your profile is named
something other that the defaults, such as Mach4Mill, and make
a packaged profile so you can re-import your old configuration.
103
Announcements / PMDX-414 SmartBOB-USB released
« on: April 28, 2017, 04:45:04 PM »
The PMDX-414 is refresh of our SmartBOB product line that combines
the encoder support of the PMDX-410 with the panel mount system
of the PMDX-412 into a single new design so you no longer have to
choose between these two features when selecting a low cost board.
The PMDX-414 has replaced both the PMDX-410 and the PMDX-412
in our product line and can functionally replace both products. The
older products will continued to be supported by our Mach4 plug-ins
because they share the same design architecture as all of the
SmartBOB family.
You can view the PMDX-414 product page here:
http://www.pmdx.com/PMDX-414
the encoder support of the PMDX-410 with the panel mount system
of the PMDX-412 into a single new design so you no longer have to
choose between these two features when selecting a low cost board.
The PMDX-414 has replaced both the PMDX-410 and the PMDX-412
in our product line and can functionally replace both products. The
older products will continued to be supported by our Mach4 plug-ins
because they share the same design architecture as all of the
SmartBOB family.
You can view the PMDX-414 product page here:
http://www.pmdx.com/PMDX-414
104
Announcements / SmartBOB-USB plug-in updated to version 0.51.252 probing fixes, support PMDX-414
« on: April 27, 2017, 02:44:39 PM »
The Mach4Hobby plugin for the SmartBOB-USB family of controllers has been updated to version 0.51.252,
released 19 April 2017. This plug-in requires Mach4 builds 2872 or higher. It has been tested with builds
2914 and 2233, and should work with later builds when released.
Full details of this release are here: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_51_252.html
Download the plug-in here: http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In
Major changes for this release (see the release notes for a complete list of changes):
(1) Fixed several bugs in probing support.
(2) Clarified error messages for lathe threading.
(3) Added support for PMDX-414.
released 19 April 2017. This plug-in requires Mach4 builds 2872 or higher. It has been tested with builds
2914 and 2233, and should work with later builds when released.
Full details of this release are here: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_51_252.html
Download the plug-in here: http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In
Major changes for this release (see the release notes for a complete list of changes):
(1) Fixed several bugs in probing support.
(2) Clarified error messages for lathe threading.
(3) Added support for PMDX-414.
105
SmartBOB controllers and dedicated accessories / Re: What do I need to be able to probe Z.with 411 and g540
« on: April 18, 2017, 08:46:58 PM »
Homing needs to be configured in Mach4 before it will happen.
See: Config > Mach and click on the Homing and Soft Limits tab.
See the Mach4 CNC Controller config.pdf manual in your Docs folder for more information.
See: Config > Mach and click on the Homing and Soft Limits tab.
See the Mach4 CNC Controller config.pdf manual in your Docs folder for more information.