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.


Messages - Steve Stallings

Pages: 1 ... 3 4 [5] 6 7 ... 35
61
If your drives move the correct distance, then you have the counts
per unit configured correctly for your Encoder and G320 setup.

If the fault only occurs sometimes, you may have a tuning problem.
Try running with lower velocity. If this cures the problem, it is likely
a tuning problem.

The charge pump is required if you are using the PMDX-126 to
interface with the Err/RST terminal of the G320 drivers. If you are
manually resetting the drives and have not connection from the
Err/RST terminal to the PMDX-126, then a charge pump is not
required.


62
Most lasers with power controls will accept PWM signals directly.

The PWM signal which controls the PMDX-107 is also available
on connector J6 as "16". This signal is not electrically isolated
so check to see if connecting the laser's control input ground
to your computer's parallel port ground is going to cause any
problems.

63
It may work directly, but I do not have the necessary documentation on
the K2CNC machine to tell you. If you have a manual for the K2CNC or
can send us a Mach3 configuration XML file for the K2CNC, we can verify
it for you.

The main issue is that the step and direction signals need to match one
of these two configurations:

Step on pins 2, 4, 6, and 8   Direction on pins 3, 5, 7, and 9

OR

Step on pins 3, 5, 7, and 9   Direction on pins 2, 4, 6, and 8

These two possibilities cover 95% or more of the interfaces
typically used with Mach, but there are some exceptions.

64
The correlation between J1 of the PMDX-126 and J4 of the PMDX-134 is
as you described it.

It is probably easier to think in terms of which DB-25 pins control which
connector on the PMDX-134.

65
General Discussion / Re: New Hobby CNC Router Build Help
« on: September 26, 2017, 09:30:04 PM »
PRO: Solid state relays require very little signal power to control them. A logic
level output can drive most of them.

PRO: Because they have no moving parts, they can be used for things that
turn on and off frequently and still live a long time.

CON: The most likely failure mode of a solid state relay is to be shorted in the
ON state.

PRO: A mechanical contactor, not just a simple relay, has two contacts in series
on each leg so that if one contact welds shut, the other still opens the circuit.
The MD20-120 is a true contactor.

PRO: It also has two poles so it can switch both sides of a 240 VAC line.

66
General Discussion / Re: Pull up resistor?
« on: August 28, 2017, 07:08:50 PM »
The other guy was probably thinking of the Step and Direction signal inputs
which are isolated.

67
General Discussion / Re: New Hobby CNC Router Build Help
« on: August 28, 2017, 07:07:40 PM »
Not that style. They are intended for lower voltage DC motors.

The style I was referring to was like these:

https://www.ebay.com/sch/i.html?_from=R40&_trksid=m570.l1313&_nkw=24V-380V+25A+SSR-25+DA

No PWM ability, but rugged on/off control for large AC powered brush type routers.

68
General Discussion / Re: Which hardware for new projects.
« on: August 28, 2017, 02:53:44 PM »
Your 3D printer likely has a single board with the control processor,
the motor drivers, and the heater controller all integrated together.
Unless you really want to get into conversion to Mach software, I would
suggest that you pursue a replacement of similar design.

The slicer is what reads the STL model file and generates the G code.
There are several that are free.

Mach4 will have a 3-D printer mode to accommodate the G code quirks
needed for controlling the material feeder, but it is beta code at the
moment.

Plasma cutters need torch height control if you are cutting anything
more than thin sheet metal. Currently PMDX does not offer a torch
height control.

It is possible to use an external one such as the Proma SD model with
our PMDX-424 board and Mach4, or you can use a Proma 150 with a
PMDX-126 board if you have a computer with a parallel port and run
Mach3 software.

the

69
General Discussion / Re: motion underrun
« on: August 28, 2017, 02:34:14 PM »
The SmartBOB family of products are USB 2.0 and backward compatible with USB 1.1.

If connected to a USB 3.0 port they will run in USB 2.0 mode.

Even though your computer is fast, it is possible that your G code contains segments
so short that there is not sufficient time to transmit them relative to how long the
movement should take. Look to see if you have G code moves that are tiny, such
as less than a couple of thousandths of an inch.

70
General Discussion / Re: Pull up resistor?
« on: August 28, 2017, 02:29:54 PM »
First guess..... your encoder signals are connected in the opposite
phase from that needed for your motor connections. Try swapping
the A and B channels of the encoder or the + and - wires to the
motor, but not both.

Second guess..... your encoders do not have a shared ground
reference with the inputs of the G320X. The ground of the encoder
power must be connected to the ENC GND on the G320X even when
using an external power source.

Third guess.... your encoders are not making valid signals. You should
be able to measure the output voltage of each phase (A, B) to ENC GND
using a regular meter by removing the motor wires and very carefully
moving the shaft of the motor by hand. With some practice you should be
able to stop the shaft with the signal at 0 volts and at near 5 volts on each
signal. This will prove that the electrical output is valid.

71
PMDX has released a new plugin that fixes a problem that
has plagued our users for a while. It did not affect all
systems, but did affect many of them. The source of the
problem was the PMDX plugin trying to use the Mach4 API
before Mach4 was done initializing. This could result in
machine.ini files being corrupted any time the PMDX plugin
was in the plug-ins folder under \Mach4Hobby\Plugins. This
problem could happen even if the SmartBOB was not selected
for use in the profile you were running because Mach4 asks
all plugins that are present to run their initialization
code so that Mach4 can populate the selection menus with
all the plugins that are available.

The most noticeable symptom of the problem would be altered
screen colors, but other more subtle configuration problems
could result because uninitialized data was getting written
to the machine.ini file.

If the toolpath area of your screen has a mustard color
background instead of the default blue background, then you
have been affected by this problem.

Remember that this issue could affect even profiles that did
not use the SmartBOB, and that the changes remain in the
machine.ini file even if you had subsequently removed the
PMDX SmartBOB plugin.

You should update your PMDX SmartBOB plugin, even if you
are not using it, so that future corruptions do not happen.
The updated plugin is version 0.52.254 and is available here:

http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In

It is best to rebuild your profile from freshly installed
sample profiles from PMDX and Mach4 defaults. This assures
that you have a clean machine.ini file. You can safely look
at old profiles after the new plugin is loaded, but do not
use them to copy and create a new profile.

If you are still running a profile with the default name,
such as Mach4Mill or PMDX-Sample, you should use the
Mach4Loader to make a safe copy of it before reinstalling.
This will allow you to have a reference to look at to find
your old settings.

To do this start the Mach4Loader, highlight the profile that
you are using, and click on the COPY button. Provide a
new name such as MySavedProfile in the box for the profile
name and then where it asks for screen set, click on the
button with three dots and select the screen set that you
were using, typically wx4.set is you were using a sample.
Then click on OK to save the profile under the new name.
Now the newly saved profile will not be overwritten when
you reinstall Mach4 and you can start it any time by using
Mach4Loader and highlighting the name and clicking OK.
Because you have installed the updated PMDX-SmartBOB
plug-in there is no risk in opening old corrupted profiles.

In order to be sure that you have known good profiles to copy from
when building new profiles you will need to remove the old PMDX
sample profiles and reinstall both Mach4 and the PMDX SmartBOB
plugin. The PMDX SmartBOB installer will not overwrite existing
PMDX samples, so you must delete the "PMDX-Sample" and the
"PMDX-424-Sample" profile before reinstalling the PMDX SmartBOB
plugin.

You can do this by deleting their folders from the \Mach4Hobby\Profiles folder,
or by using the Mach4Loader icon, highlight the profile to be
removed and click on the Delete button.

Both Mach4Hobby and the PMDX-SmartBOB plugin can be installed
over your existing ones without un-installing (other than the
old PMDX sample profiles mentioned above). Other custom profiles
will not be overwritten during the installs. Both Mach4Hobby and
the PMDX SmartBOB plugin offer standard Windows un-installers if
you choose to run them.

We apologize for the trouble and confusion this may have caused
for you. It sure caused us plenty.

Steve Stallings
www.PMDX.com

72
General Discussion / Re: Mach4 hobby version 3468
« on: August 15, 2017, 10:57:14 AM »
Build 3468 and 3474 introduced new features but also an unexpected bug. They were
removed from the released build download area while the bug gets resolved.

Users who loaded these builds should consider reverting to build 3390 for stability.

If you are running customized profiles that have been saved with a new name other
than the default sample names, you can reload build 3390 and your customized profiles
will still be here.

If you are still running with profiles named Mach4Mill, Mach4Mill_6Axis, Mach4Lathe,
or Mach4Router then you should use the Copy Profile function of Mach4Loader to
make a fresh copy of your profile with a new name before reloading build 3390 so
that your profile does not get overwritten.

73
If your previously working setup stops working when you set
Dip Switch 1 to the Open position, then the PMDX-126 is not
seeing the Charge Pump Signal.

There are two ways to confirm the presence of the Charge
Pump signal. First, there is an LED on the PMDX-126 labeled
Outputs Enabled. It you set DIP Switch 1 to On for operation
without a Charge Pump, you should see the LED glow as
long as you do not have an E-Stop condition. If you set
DIP Switch 1 to Off to enable the Charge Pump function, then
this LED will  turn off when the board does not see a Charge
Pump signal on Pin 17. You can also look at the Pin 17 LED
beside connector J6 to look at the Charge Pump signal directly.

Your description of the wiring between the VFD and the
PMDX-107 is correct.

If you cannot get the Charge Pump signal to work, you will
need to set DIP Switch 4 of the PMDX-107 to the On position
to tell it to ignore the Charge Pump signal.

You can tell if the PMDX-107 is responding to signals from
the SmoothStepper by looking at the LEDs on the PMDX-107.

If these LEDs are responding and your VFD does not, you
should also try the TEST button on the PMDX-107.

If the VFD still does not respond, it is likely that your
VFD parameters are not set correctly. The most important
ones are A001 (frequency source) and A002 (Run command
source). Both of these must be set to 01 to allow activation
from the control terminals where the PMDX-107 is connected.

74
I will recommend running with COM used as ground, or
the negative side of your signals. To do this you will
need to set COM to be GND using our Mach4 plugin.
With Mach4 running, but not enabled, select:

Config > Plugins > PMDX-SmartBOB

and click on the tab labeled Motor Config. In top right of
the dialog will be an area for Step/Dir Common Configuration.
Click on the box for Step/Dir is Ground. This is the
default setting and should already be checked if
you have not edited anything.

It is also possible to operate with COM set to +5V
but we find it less confusing to use COM as Gnd with
modern drivers. Older drivers tended to use +5V as
COM because the old TTL logic family was better at
sinking current than at sourcing current. With CMOS
this is no longer a concern.

The COM terminal of the motor connector on the
PMDX-424 should connect to both the PUL- and to
the DIR- of the driver. The Step terminal of the motor
connector on the PMDX-424 should connect to the
PUL+ on the driver. The Dir terminal of the motor
connector on the PMDX-424 should connect to the
DIR+ on the driver.

You do not need any connection to the ENA+ and
ENA- terminals of the driver. The driver defaults to
enabled and these signals are only needed when
you need to disable the driver.

Just a note, your M542 drivers are for stepper
motors, not servos.

75
The J15 and J16 ports function identically. If you had it working
with the DB-25, then no changes other than the cable are required
to move to the ribbon header.

Please check that you do not have one end of the ribbon cable plugged
in backwards at either the PMDX-126 or the SmoothStepper. On the
PMDX-126 pin 1 of the ribbon cable goes to the end nearest the
J16 legend on the board. For the ESS you can see the orientation
in this diagram:

https://warp9td.com/documentation/ESS-Mechanical-Diagram.pdf

Pages: 1 ... 3 4 [5] 6 7 ... 35