Messages

181

SmartBOB controllers and dedicated accessories / Re: Error 7 when attempting to Home

« on: January 24, 2016, 11:01:08 PM »

"PMDX-SMARTBOB-USB DEVICE ERROR: SYSTEM ERROR (7): Motion Underrun"

I am also getting this error on occasion.  It does not seem to  occur at the same instance while running my programs.  I restart the program and Re-Zero my AXIS since I am afraid that it is loosing its position when this occurs.  I have not tried to increase my buffer yet, but will do so.

In addtion to increasing the buffer length, make sure that our plug-in's debug log settings are set to the default.  I don't know if you ever actually enabled our debug log during your earlier issues with USB cables (back in Oct).  Go to the Mach4 "Configure" menu and select "Plugins...".  Then click on the "configure" button for the PMDX SmartBOB.  When our configuration dialog displays, click on the "Debug" tab. "Debug Mode" should be "System" and "Debug Device" should be "Windows Debug API".

Let me know if increasing the "GCode buffer len" has any effect.

Bob
Bob

182

General Discussion / Re: Step Pulse Width

« on: January 24, 2016, 09:44:41 PM »

I have my Step Pulse Width set to 5us.  My driver (CW8060) specifies "Rising edge effective ,rising edge duration >10μS".  Is this the same thing?  Should I set it to 10us?  http://cnc4you.co.uk/resources/CW8060.pdf

Looking at that data sheet and the web page for the device, I cannot find any such specification.  The data sheet makes no mention or pulse duration or rising/falling edge.  The web page says it can handle "an amazing" 1,000 KHz step rate, which means it should handle step pulses with a duration of 0.5 microseconds.

That said, if the docs you have mention 10 microsecond pulse width, then as Steve mentioned, go ahead and try it.  You also should have jumper JP3 on the PMDX-422 set for "GND" for the step/dir common voltage, and the step polarity should be "positive".  And this should be for all axis that are driving that model stepper driver.

Bob

183

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX-126 Rev B K1/K2 Relay issue

« on: January 22, 2016, 11:17:33 PM »

As for which version of the PMDX-126 you have, I can't access our serial number records from home.  But we can figure this out.  All location descriptions below are based on the 126 oriented so that the 25-pin "D" connector for parallel port #1 is at the bottom edge, and the transformer is at the top of the board.

Rev A boards: The serial number block is near the lower right hand corner of the board, just below the ESTop LED.  There should be a silkscreen block just above the serial number for the revision, and should be marked "A1", "A2" or "A3".  If you can look at the underside of the board, in the lower right corner (lower left now that you've flipped the board over), you should see in copper "PCB-485A".

Rev B boards: The serial number block is along the lower left edge of the board, just to the left of the 25-pin "D" connector for parallel port #1.  The silkscreen also says "(Revision B") in the center of the board just below the transformer and the "PMDX-126" text.  Again, there should be a silkscreen block for the revision just above the serial number block.  It should say "B1", "B2" or "B3".

Rev C boards: The serial number block is in the same location as the rev B boards.  The silkscreen says "(Revision C)" in the center of the board just under the "PMDX-126" text.  The revision block would have "C1", "C2" or "C3".

A couple more things to look at, after you try #4 from my previous message:
(1) If you have a volt meter or DMM - With the 110VAC disconnected from the external relays, turn on the PMDX-126 K1 and K2 relays.  Measure the voltage between any of the "PC+5V" and "PC gnd" terminals on J1 through J6.

(2) Reconnect 110VAC to the external relays.  Disconnect the wire for your panel EStop LED from connector J7 on the PMDX-126.  See if you still get the EStop when the relay(s) energize.

(3) Where is the ESS mounted relative to the PMDX-126?  Is it mounted on top of the 126?  If not, how far away from the 126 is it?  And how long are the ribbon cable or cables from the 126 to the ESS (if the ESS is mounted on the 126 and you bought the cables from us then they are 6" (approx.).

Bob

184

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX-126 Rev B K1/K2 Relay issue

« on: January 22, 2016, 03:52:08 PM »

Are you sure that Mach3 is seeing the "EStop" signal?  Does the message in the Mach3 status line say "External EStop Requested"?  A limit switch going active will also make the Mach3 "Reset" button flash but will display a different message in the status line.

If the PMDX-126's EStop LED does not turn on, then the problem is NOT the EStop signal coming into the PMDX-126 board.  The PMDX-126 samples and filters** the EStop input, and outputs the EStop signal to the PC.  The EStop output to the PC is asserted for at least 1 second whenever the PMDX-126 detects the EStop input.  So even narrow pulses on the EStop input should result in visible EStop LED activity.

** I am pretty sure the rev B boards filter the EStop input but I haven't gone back through the code to verify this.

It is  possible that noise is getting coupled onto the EStop output (port 1 pin 10) between the PMDX-126 and the ESS.

How far away from the PMDX-126 are the external relays from the PMDX-126?

One other test would be to re-route the 110V that goes through the K1 and K2 relays and keep the 110V wiring as far away from the 126 and ESS as possible.  Except, of course, where it has to come into the AC input and the K1/K2 connectors.

Bob

185

SmartBOB controllers and dedicated accessories / Re: Laser on/off PMDX-422 Mach4

« on: January 22, 2016, 09:57:15 AM »

You can write custom macros to do this.  I am attaching macros for M10 and M11 that turn Output4 on (M10) and off (M11).  Place these in the "Macros" directory of your profile and remove the ".txt" extension so they are "m10.mcs" and "m11.mcs".  Then go into the "Configure" menu and select "Mach...".  Click on the "Output Signals" tab, scroll down to "Output #4", enable it and map it to your desired PMDX-422 output signal.

You can edit the macros to use a different output.  Or edit them to remove the call to mc.mcCntlSetLastError() if you don't want messages piling up in the Mach4 status line (and history).

Bob

186

SmartBOB controllers and dedicated accessories / Re: Error 7 when attempting to Home

« on: January 21, 2016, 12:13:24 PM »

Thanks Jarhead.  Though I see "Go To Work Zero" on wx4 screenset and I am using Mach version 2803.  Should I be using a different screenset?

The newer wx4 and wx6 screen sets call the button "Go To Work Zero" and the older wxMach screen set calls it "Go to zero".  Supposedly the same function however the scripts behind the buttons are slightly different but should have the same effect.  The wxMach screen set sends GCode (i.e. something like "G0 X0 Y0", by default leaving out the Z axis). The wx4 and wx6 screen sets call a function named GoToWorkZero(), which is defined in the screen load script to be:
        mc.mcCntlMdiExecute(inst, "G00 X0 Y0 A0")--Without Z moves
i.e. still sending GCode and by default leaving out the Z axis.  More than you wanted to know I'm sure.

1. "Reference All Axes (Home)" button causes the error "Unexpected homing request while Mach4 is disabled, ignoring" and also the error "Error 7 (Communication error) queuing HOME pkt for axis 'X' motor 'Slave 1' (id 3), aborting HOME cmd" flashes up briefly.

Fix for this is pending in next plug-in release.  Though what exactly do you mean by "flashes up briefly"?  Do you mean it shows up on the Mach4 status line at the bottom of the screen and is then replaced by something else (and you can see it again when you click on the "History" button)?

2. Go To Work Zero doesn't do anything.  Maybe I need to create my own button with a simple script for this.

This is what I am waiting for the debug log and profile package to look at.

3. A new problem I am having right now is that I can't run *some* gcode files.  One quite large (1.5Mb) file I was running happily an hour ago is now giving me the error "PMDX-SMARTBOB-USB DEVICE ERROR: SYSTEM ERROR (7): Motion Underrun"  When I press "Cycle Start Gcode" this message flashes up briefly and then the program seems to reset and disable the machine. 

Try increasing the SmartBOB's GCode buffer len and see if this has any effect.  Go to the Mach4 "Configure" menu and select "Plulg-ins". Click on the "Configure" button next to the PMDX SmartBOB.  When our config dialog appears, click no the "Performance Settings" tab.  The default for the GCode buffer len is 250 milliseconds.  Try increasing that to 500ms.  It that doesn't work, try 750ms.  If *THAT* doesn't work, then enable the debug log again and try to run the large GCode file.  When it fails, disable the debug log and either send me another profile package.

Bob

187

Parallel Port breakout boards, motherboards, and dedicated accessories / Re: PMDX-126 Rev B K1/K2 Relay issue

« on: January 21, 2016, 11:52:50 AM »

Suddenly, I get an eStop when issuing M8 or M7 in MDI/Gcode, or via my Pokeys mapped physical switches.

(1) By "via my Pokeys mapped...." do you mean you have mechanical switches connected to your pokeys board and those switches are configured in Mach to manually turn the flood/mist relays on and off?  If not, what do the switches on the pokeys board do?

(2) Can you look at the PMDX-126 while you issue an M7 or M8 command?  Does the red EStop LED on the PMDX-126 turn on when the relay(s) engage?

(3) Disconnect the 110VAC that is being switched by the relays, so the relays can close and open but won't actually switch power to the flood/mist pumps.  Then try M7 or M8.  Do you still get the EStop?

(4) Disconnect any EStop circuit you have connected to the PMDX-126's EStop and Fault inputs.  Then take a (very!) short piece of wire and connect the EStop input to the adjacent GND terminal.  Leave the Fault input unconnected.  Then try M7 or M8.  Do you still get the EStop?

(5) Are you powering anything from the "+12U" terminals on J11 or J12 of the PMDX-126?

(6) Are you powering anything from the "+V Raw" terminal on J7 (right next to the AC voltage selector switch)?

(7) A drastic test is to disconnect everything from the PMDX-126 except the 110VAC input power, the SS, and the EStop jumper to GND.  Then try M7 and M8 and see if you get an EStop.

There *may* be something loading down one of the PMDX-126 power supplies, or there is a faulty component in the power supply section.  Then when one of the relays tries to energize it loads down the supply  even further and causes the PMDX-126 to malfunction.  We'll see what your answers are to the above questions.

Bob

188

SmartBOB controllers and dedicated accessories / Re: Error 7 when attempting to Home

« on: January 19, 2016, 11:06:46 PM »

I believe the Go to Work Zero button has been removed from Mach4, you must be using the old screen set if it is still showing. I believe the functionality is removed.

I see "Goto Work Zero" in Mach4 build 2803 in the wx4 and wx6 screen sets.  In the wxMach screen set the button reads as "Go to Zero".  As far as I can tell I haven't edited or modified the wx4 screen set.

Note that if you use our sample profile as the starting point for your profile, it will use the wxMach screen set by default.  That may (will?) change in a future release.

Bob

189

SmartBOB controllers and dedicated accessories / Re: Error 7 when attempting to Home

« on: January 19, 2016, 02:26:07 PM »

Yes this works, but only as long as I don't try using the "Ref all home" button on the main screen during the same session.  If I do, I have to restart Mach4 to get the ref buttons on the "Machine Diagnostics" page to work.

Try opening one of the configuration dialogs (Configure->Mach... for example), then click on "OK" to close it.  That may reset things.

*Another* issue is that the "Go to Work Zero" button does nothing.  I have attached a log file generated when pressing the button.

Alas the log file you attached (the Mach4 diagnostic log) doesn't show me anything other than it entering a motion state then stopping.  To get more detailed information I need you to enable our plug-in's debug log, and then send me a "profile package".  The steps are described here:

http://www.pmdx.com/PMDX-Forums/index.php?topic=97.0

That message is also listed in the "FAQ - PMDX-SmartBOB Troubleshooting Tips" sticky message at the top of the SmartBOB message board.

After enabling the debug log, do whatever you need to do to make this problem appear (i.e. jog off of machine zero then click on "Goto Machine Zero").  Then disable the debug log and create the profile package as described in the link.  When you send me the package, also include a detailed description of what steps you took (i.e. if you jogged the machine, what coordinates did you jog to?).  You can post the package here or email it to me at bob at this domain.

Bob

190

SmartBOB controllers and dedicated accessories / Re: Error 7 when attempting to Home

« on: January 15, 2016, 12:07:54 PM »

Hi Bob,
So yes, it looks like it's just the homing issue.  Fairly crucial but I can get by for the moment manually.

In case you haven't tried this yet, you should be able to go to the "Machine Diagnostics" screen and home one axis at a time.

I wonder if I could ask a related question; do you have a timescale for supporting gantry squaring homing?  With the smoothstepper I had this set up with two proximity sensors, and it's quite important for me since using only one I often find a squaring discrepancy.

Right now, no, other than "soon".  After the show we are going to review the "to do" list for the SmartBOB software and review priorities for the next couple of releases.

Bob

191

SmartBOB controllers and dedicated accessories / Re: VistaCNC Pendant problem

« on: January 15, 2016, 11:37:26 AM »

I've got the profile package, thanks.  There are some *very* interesting things happening in the log file (and by "interesting" I mean "what on earth is going on here").  It is going to take me a while to try and figure out what is going on.  I'll post back here when I figure it out, or if I need you to run another test for me.

Bob

192

SmartBOB controllers and dedicated accessories / Re: Error 7 when attempting to Home

« on: January 15, 2016, 10:38:00 AM »

Another thing to mention is that I'm running Windows natively (using Bootcamp) on a Mac Mini, not sure that this should make any difference to USB operation.

I cannot say if this is an issue or not, as I have no experience with Mac hardware.  I would guess not.  We do have at least one user who is running successfully under Bootcamp:
http://www.pmdx.com/PMDX-Forums/index.php?topic=114.msg378#msg378

Aside from that, you are seeing two different issues:

When I click the Ref All Home button I get the following message and the machine automatically disables:
"Error 7 (Communication error) queuing HOME pkt for axis 'X' motor 'Slave 1' (id 3), aborting HOME cmd"

Issue #1 - Homing.  There is a known race condition in the homing code.  I have a fix for this in testing for the next plug-in release.

Just to follow up, this seems to be a general problem communicating with the board.  I have tried running some g-code and after a few seconds of running it will stop dead and not respond.  The board becomes disabled (DS2 LED off) and won't respond to mach4.  "ERROR: Could not disable the PMDX-SmartBOB-USB, error 'Communications Error''.
I then have to close Mach4, unplug the USB and re-plug to get it working again.

Issue #2 - general USB communication problems.  I see that Steve forwarded email to me that you sent to him saying that replacing the USB cable solved this problem.  Is that the case?

Usually this kind of problem is caused by electrical interference from either the motor and motor power supply of the spindle (VFDs are particularly troublesome).  The general solutions involve re-routing any high current wiring away from the USB cables, the SmartBOB and any limit switch wiring.

Bob

193

SmartBOB controllers and dedicated accessories / Re: VistaCNC Pendant problem

« on: January 13, 2016, 10:42:09 PM »

I presume that when you say "When I attempt to use it in any axis or any jog mode" you mean that not matter what the jog step size is you always get this error.  Is that correct?

This is likely some interaction between the two plug-ins, though it could be a timing issue between the Mach4 core, our plug-in and our device that is influenced by the VistaCNC plug-in.

I would like you to capture a debug log from our plug-in.  The general instructions are here:
http://www.pmdx.com/PMDX-Forums/index.php?topic=97.0

EDIT: When enabling the debug log - please enable the "Motion Info" level instead of the "Debug" level mentioned in the above link

After you enable the debug log, exit Mach4 then re-start it.  Set the pendant to try and jog an axis.  After you see the error message, disable our debug log (step 6 in the link above), create the profile package and email that to me at bob at this domain.  Or you can post it here, though you will have to rename the file to a ".zip" extension instead of ".m4prof".

Bob

194

General Discussion / Re: Disabling an optional 4th Axis on a CNC Router

« on: January 04, 2016, 12:36:26 AM »

While the G203V manual (http://www.geckodrive.com/g203v-rev-7) states that it will "will survive accidental motor disconnects while powered-up", we recommend that you remove power from the G203Vs before connecting or disconnecting a motor.  It is OK to have a G203V (or pretty much any stepper motor driver) powered on with no motor connected.

Bob

195

SmartBOB controllers and dedicated accessories / Re: Mach 4 Licensing thru PMDX

« on: January 03, 2016, 09:44:49 PM »

I'm considering the PMDX-411/Mach4 bundle but was wondering how Mach4 licensing is done through distributors.  Is that done through the Newfangled Solutions website directly or do distributors act as a middle-man for those transactions?

When you by a Mach4Hobby license from us, we (PMDX) provide you a coupon code that you then use on the Machsupport.com site, along with your PCID, to get your Mach4Hobby license.  Here is a complete description of the process:
http://pmdx.com/Mach4-License

I read on the NS site that hobby users can run the software on more than one machine under a single license, but it was a little vague.

I believe that they allow up to 5 active licenses at a time, though they ask that if you are using multiple PCs/machines for production (i.e. revenue producing) work that you purchase a license for each of those machines.  But that is my recollection.  Please read the Mach4 license terms for the definitive answer (http://www.machsupport.com/help-learning/software-licensing-info/).  Look in the "General" tab for "non-commercial" users.

It also says that if the product is purchased through a distributor, they buyer will not have an account at NS. So how would one go about getting the additional license(s), if required, or replace the license in the event of computer replacement?

That *used* to be the case, but no longer is, at least the way that PMDX handles license purchases.  See the link I posted above.

Bob