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 2 [3] 4 5 ... 35
31
Sorry, but our manual has not been updated to reflect a change in how the PMDX-424 operates.

The current version now allows you to reset the board by unplugging the USB cable, so if you do not have the USB cable connected the lights will not operate as described in the manual because the board is being held in the reset condition.

32
Having multiple profiles on one computer is fine, but you only install Mach4 once. Use Mach4Loader to select the desired profile, or edit your desktop launcher to start the desired profile.

Having two SmartBOBs plugged into your computer at the same time will not work because the first one found is the one that will run, regardless of profile. You will need to plug in only the one that you intend to run at the time.


33
General Discussion / Re: Mach4 bundle coupon
« on: July 29, 2020, 07:56:33 PM »
Thanks Chris, for closing the loop here.

We generally do not edit posts except in instances of personal attacks, or other violations of terms, so this one will stay.

34

There have been multiple reports of probing bugs that PMDX has not been unable to replicate and we would like to have assistance collecting more detailed data on this problem.

If you are able to help, please send us Debug logs generated while attempting to probe. It is best minimize the size of the log file by not running a lot of G-code other than the probe cycle.

General instructions for using debug logs are on this FAQ page:
How to capture a debug log file and send to PMDX?
https://faq.pmdx.com/index.php?solution_id=1002

The settings for debug logs are found in the SmartBOB plugin screen in Mach4 here:

Configure > Plugins > PMDX SmartBOB  ... then select the Debug tab

Mach4 cannot not be in the enabled state when accessing the Configure functions.

The SPECIFIC settings that should be used for this probing test log are:

Debug mode - select only "Debug"

Debug device - select only "File"

Enable additional debug logs - select these 3
                               "Motion log"
                               "Position log"
                               "Packet log"

Message logging options - none selected

Then exit the setup screen by clicking on OK and the Plugin configuration screen will close.

After changing the log settings, exit Mach4, then restart it.  Do as little as necessary to prepare for the probe motion. Please keep notes and send us a description of everything you did. It makes it easier to wade through the log files.

Then execute the probe cycle. Repeat the probe cycle until you get a failure. Describe what happened, including the error messages that you get, and tell us how many times you did the probe cycle before it failed. 

Then go back into the plugin configuration Debug tab and "Restore Default Settings" (unless you plan to run several debug attempts) and then shut down Mach4 so it will close the debug log file.

If you have Mach4 installed in the default location, you will find the log files at:

C:/Mach4Hobby/Profiles/<your profile name here>/PMDX-SmartBOB-USB.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXVersionInfo.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXMotionDebug.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXPositionDebug.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXPacketDebug.log

If the resulting files are more than a few of megabytes, we may need to help you generate smaller files.

We would also like to have a "Packaged Profile" from the Mach4 profile that was used to generate the log files.

Lastly, tell us what version of Windows you are running and describe your computer briefly.

Do not post the files in the forum.

Please send the files as email attachments to our support email address found here:

http://www.pmdx.com/ContactUs

Sorry for the extra step, but we prefer to not post email addresses in forum messages where they may be harvested by spammers.

Thank you for your assistance.

Steve Stallings
PMDX

35

There have been multiple reports of probing bugs that PMDX has not been unable to replicate and we would like to have assistance collecting more detailed data on this problem.

If you are able to help, please send us Debug logs generated while attempting to probe. It is best minimize the size of the log file by not running a lot of G-code other than the probe cycle.

General instructions for using debug logs are on this FAQ page:
How to capture a debug log file and send to PMDX?
https://faq.pmdx.com/index.php?solution_id=1002

The settings for debug logs are found in the SmartBOB plugin screen in Mach4 here:

Configure > Plugins > PMDX SmartBOB  ... then select the Debug tab

Mach4 cannot not be in the enabled state when accessing the Configure functions.

The SPECIFIC settings that should be used for this probing test log are:

Debug mode - select only "Debug"

Debug device - select only "File"

Enable additional debug logs - select these 3
                               "Motion log"
                               "Position log"
                               "Packet log"

Message logging options - none selected

Then exit the setup screen by clicking on OK and the Plugin configuration screen will close.

After changing the log settings, exit Mach4, then restart it.  Do as little as necessary to prepare for the probe motion. Please keep notes and send us a description of everything you did. It makes it easier to wade through the log files.

Then execute the probe cycle. Repeat the probe cycle until you get a failure. Describe what happened, including the error messages that you get, and tell us how many times you did the probe cycle before it failed. 

Then go back into the plugin configuration Debug tab and "Restore Default Settings" (unless you plan to run several debug attempts) and then shut down Mach4 so it will close the debug log file.

If you have Mach4 installed in the default location, you will find the log files at:

C:/Mach4Hobby/Profiles/<your profile name here>/PMDX-SmartBOB-USB.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXVersionInfo.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXMotionDebug.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXPositionDebug.log
C:/Mach4Hobby/Profiles/<your profile name here>/PMDXPacketDebug.log

If the resulting files are more than a few of megabytes, we may need to help you generate smaller files.

We would also like to have a "Packaged Profile" from the Mach4 profile that was used to generate the log files.

Lastly, tell us what version of Windows you are running and describe your computer briefly.

Do not post the files in the forum.

Please send the files as email attachments to our support email address found here:

http://www.pmdx.com/ContactUs

Sorry for the extra step, but we prefer to not post email addresses in forum messages where they may be harvested by spammers.

Thank you for your assistance.

Steve Stallings
PMDX

36
The relay connections on the PMDX-126 are for just the contacts of the relay, no power from the board comes out of the connector. You wire it up as if it was a switch controlling external power.

37
Putting the G540, the stepper motor power supply, and the SmartBOB in the same enclosure is fine.

Things to worry about are power wires to a brush type spindle motor, power wires to or from a VFD, or the power cable to a plasma torch. The plasma torch cable should never pass through the control enclosure. If the power wires to a spindle or VFD are passing through the control cabinet, try to separate them from the input signals and USB cable as far a possible.

38
I am going to assume that you have a secondary parallel port since it is unlikely you have enough inputs to use a pendant with a single parallel port.

Pins that are always inputs (10, 11,  12, 13, and 15) should not be a problem and I recommend temporarily utilizing these if you are not getting your input signals.

The data pins (2 thru 9) can be used as input for the Port 2 in Mach3. Make sure that you have the box labeled "Pins 2-9 as inputs" checked in the "Port #2" box of Ports and Pins for Mach3.

It may be that some parallel port cards use unusual registers to control configuration and Mach3 may not be able to make pins 2 thru 9 be inputs on such a card. If you suspect this to be the case and you have a motherboard parallel port available, you can juggle the port addresses such that Mach3 uses the add on card as Port #1 for step and direction signals, and the motherboard port for your pendant. Then Mach3 should be able to control the input mode. Make sure that the port is configured as AT or PS2 style, or EPP mode in your bios. Plain PC parallel port mode does not allow 2 thru 9 to be inputs.

The add on parallel port card sold by PMDX does work with Mach3 for inputs on pins 2 thru 9.



39
It is OK to connect your PMDX-424 to the computer and run Mach4 without your motor drivers or stepper motors attached.

Step pulses will still be generated and your DROs will react as if the motors were present because this is an "open loop" system.

You should leave the red jumper clip installed on the E-Stop input or replace it with a normally closed switch because the sample profiles expect the switch to be connected.

40
There has been no change in the PMDX-126 and the external power source
is still recommended when you use both a PMDX-107 and the ESS. Some
people get away with it, but the PMDX-126 was originally engineered to
satisfy the needs of the USB SmoothStepper and the ESS draws more current.

I do not understand your question about J3 and J4. These connectors on the
PMDX-126 have nothing to do with the ESS.

If you are asking about jumpers on the ESS, you should remove the jumper
clips next to the Port 1 and Port 2 ribbon headers when using external power.

If you are asking about jumpers on the PMDX-126, you should put JP3 in the
off position to disconnect PMDX-126 power from the Port 1 and 2 connectors
of the PMDX-126.

41
Adding an LED at the probe could be made to work if you put the probe
on the input for pin 15 and set the jumper at JP5 to the on position.
This will provide a stronger pull-up resistor so that you can connect
a series connected LED and current limiting resistor across the probe
input and still have the input work. This arrangement is used in the
"WildHorse" probe and the input will work with it.

http://www.wildhorse-innovations.com/support/EPHookup-Alignment-new-v1.pdf

If this is not practical for you, you could modify your Mach3 screen set to
put and indicator on the main screen.

42
General Discussion / Re: Connecting VFD to PMDX-126 without 107 card
« on: July 31, 2018, 08:57:33 PM »
You can configure the VFD to use its front panel to set the speed, while
accepting the run/stop control from an external source. A relay on you
PMDX-126 can be used for this purpose.

ACM refers to Analog Common and would only be used if you had a
PMDX-107 to supply and analog speed control.

DCM refers to Digital Common and is used together with the FWD
input to control run/stop of the VFD.

43
The G214 is different from the older 200 series models. You must
connect both +5 and Gnd for them to run.

44
Ground loop issues usually matter for input signals, but not for things
like stepper motors or spindles. Noise radiation from these cables
to other parts of the system can matter, especially for spindles
driven from a VFD.

Noise issues are funny, and there is no one right answer. If you are
not having issues with the stepper wiring causing false signals on
one of your inputs, and if you do have a safety ground to the metal
parts of the machine where the motors are mounted, the I would
tend to not connect the ground from the stepper motor cable.

45
This may be magnetic interference from the motors. How close is close? I would
expect that 6" of separation should be OK.

Do the sensors have built in indicators? If so and if they light, then the issues
is with the sensor. It may be that your sensors will perform better with an external
24 volt power source.


Pages: 1 2 [3] 4 5 ... 35