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.


Topics - Bob at PMDX

Pages: [1] 2
2
The Mach4Hobby plugin for the SmartBOB-USB family of controllers has been updated to version 0.41.205, released 26 May 2016.  This plug-in requires Mach4 builds 2872 or higher. It has been tested with builds 28782 and 2914, and should work with later builds when released.

Full details of this release are HERE: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_38_188.html
(including detailed descriptions of new features related to encoders and spindle RPM measurement).

Download the plug-in here:  http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In

New features since version 0.38.188:
- Requires Mach4 build 2872 or higher

- Supports encoders as MPGs and spindle RPM measurement on PMDX-410/422 (rev B or later) and PMDX-424 (all revisions)

- Added a sample PMDX-424 profile

- PMDX sample profiles now use the wx4 screen set (see the release notes for more information on screen sets)

- Added "Help" buttons on the plug-in configuration tabs for the encoder and spindle configuration

Bug fixes since version 0.38.188:
- Fix bug that caused USB buffer overflows and/or communication timeouts when sending GCode motion to the SmartBOB device.

- Fix bug that under certain conditions caused the direction signal to change too soon after a step pulse (known as a hold time violation), which in turn could cause the motor driver to move the motor in the wrong direction.

- SmartBOB plug-in configuration dialog now stores updated motor direction polarity when running in Mach4 Hobby build 2914 or higher.

- Fixed a bug relating to un-mapping multiple Mach4 input signals mapped to a single PMDX-SmartBOB pin.

Bob
[edited to re-word subject line]

4
We have published an updated version of the PMDX-424 Quick Start Guide.  This is document revision 0.6.  Most of the changes were minor punctuation or re-wording.  We did correct the wiring connections for the DC powered version of the PMDX-424, added more detail to the mechanical dimensions drawing, and added the pin-out for the USB header.

You can download the manual from the PMDX-424 page (down near the bottom):
http://www.pmdx.com/PMDX-424

Or from the User's Manual page:
http://www.pmdx.com/Manuals

Bob

6
*******************************************************************************
This page is obsolete and maintained here for historical purposes.
Please visit the page on the new PMDX FAQ site here:

http://faq.pmdx.com/content/3/1/en/troubleshooting-did-not-find-a-valid-pmdx_smartbob-device-errors.html

or

http://faq.pmdx.com/index.php?solution_id=1000

*******************************************************************************

So, you've got your nice new shiny PMDX-SmartBOB-USB and you can't wait to take it for a spin.   You follow the steps in the Quick Start Manual and install our plug-in.  Then you plug the SmartBOB into a USB port on your PC and fire up Mach4 and you are greeted by a couple of pop-up dialogs saying that our plug-in could not find a valid PMDX-SmartBOB device.

Bummer! What now?

Well, there are a few things you can try before contacting PMDX Support for help.

BACKGROUND: The PMDX-SmartBOB installer attempts to install a "USB Virtual COM Port" driver.  This driver is a 2nd installer package that our installer extracts and runs automatically as a background task (i.e. it is, or should be, invisible to the user).  And this virtual COM port driver installer then spawns yet another installer (yes, that's 3 levels of installers running).  That 3rd installer *is* visible.  Sometimes, for reasons that so far escape me, that 3rd installer apparently does not always install correctly.  This leaves the Virtual COM Port driver not fully functional.

***************************************************
(1) Check the "Real Easy Things" First
***************************************************
(a) Do you have any USB hubs or USB extender cables (with electronics in them) between the PC and the SmartBOB?  If you have a USB hub it *MUST* be powered from an external power supply. The SmartBOB family will not work with bus powered USB hubs.  Also, USB extender cables that have electronics in them ("signal boosters", etc.) usually act as bus powered USB hubs and will not work with the SmartBOBs.  Try connecting the SmartBOB directly to your PC.

(b) Make sure the SmartBOB is plugged into a working USB slot on your PC.  Try a different USB device in the same USB port on your PC.  Does the other device work?

(c) Try plugging the SmartBOB into a different USB port on your PC.  If you used a slot on the back of your PC, try one on the front.

(d) If you have a PMDX-424, also make sure that it has power.

(e) All SmartBOB devices except for the PMDX-411 have a "Power On" LED. Is that lit?

(f) If the device has power and if the firmware in the SmartBOB is running, the red and green LEDs will turn on in various patterns.  The normal startup sequence is that both LEDs will turn on for a short time (maybe 1 second).  Then the green LED will flicker off and back on once.  Then the red LED will remain lit, and the green LED will produce a short flash once every 2 seconds.  If you see a different flash pattern, let us know what you see.

***************************************************
(2) Look in Device Manager
***************************************************
The first thing to try is to use the Windows Device Manager to look at the list of installed devices and see if the virtual COM port is listed.  The way to get to Device Manager is different in the different versions of Windows.

WinXP: Go to the Start menu, click on "Settings" and then "Control Panel".  When the control panel is displayed, double-click on the "System" icon.  This will display the "System Properties" window.  Click on the "Hardware" tab and then the "Device Manager" button.

Win7: Go to the Start menu and select "Control Panel" (usually on the right-hand side of the start menu area).  If you see approximately 8 groups of topics, then click on "Hardware and Sound", then under the "Devices and Printers" section click on "Device Manager".  If instead of 8 groups you see lots and lots of icons, look for the icon named "Device Manager" and click on it.   Note that the icons are not always in strict alphabetical order.

Win8.1: If using a touch screen, swipe in from the right edge of the screen, and then tap Search.  If you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.  Then in the search box enter "device manager" (without the quotes).  Then click on Device Manager in the results.  (see http://windows.microsoft.com/en-us/windows-8/where-is-device-manager)

Win10: Enter the words "Device Manager" (without the quotes) into the search box on the taskbar, then select Device Manager from the list of results. (see http://windows.microsoft.com/en-us/windows-10/open-device-manager)

Once you have the Device Manager window open, look for a line that says "Ports (COM & LPT)".  Click on the small plus sign next to that to expand this category.  You should see a line that says "STMicroelectronics Virtual COM Port", and there should NOT be a yellow question mark next to it.  This usually means that both parts of the Virtual COM Port driver installed correctly.  See the first image below for an example.  If you see this, this go to step (3) below.

If you do not see the "STMicroelectronics Virtual COM Port" line, look just above the "Ports (COM & LPT)" line for "Other Devices".  Click on the small plus sign to expand that category.  If you see a line that says "STM32 Virtual COM Port in FS Mode", then the Virtual COM Port driver did not fully install.  See the second image below for an example.  If you see this, go to step (2)

If you do not see either of these, or you see a device with a yellow question mark next to it, that means the Virtual COM Port driver is either not installed of not functioning.  Or it means that the SmartBOB device is not working.  In this case, follow he steps below to see if the problem is with the driver.

***************************************************
(3) Uninstall and re-install the driver
***************************************************
You will need to know if you have a 32-bit or 64-bit version of Windows.  If you don't know this, open the control panel as described above. If you see approx 8 groups of topics, then click on "System and Security", and then click on the sub-heading "System".  If instead of 8 groups you see lots and lots of icons, look for the icon named "System" and click on it.  Somewhere in the System Properties window it will show you whether it is a 32-bit or 64-bit version.  Note that for Windows XP, it will either say "64-bit" or nothing.  If it doesn't mention "64-bit" then you are running the 32-bit version.

Go here (http://www.pmdx.com/Downloads_Utilities/) and download either "VCP_V1.3.1_Setup.exe" for 32-bit systems, or "VCP_V1.3.1_Setup_x64.exe" for 64-bit systems.  Save the file somewhere that you can find it.

**IMPORTANT** Unplug the SmartBOB from the USB port before continuing.

Run this installer.  If it gives you a choice of "Modify", "Repair" or "Remove", select "Remove".  If you do not see these choices, then the driver is not installed at all and the installer will install it.  If you select "Remove", then once the installer has finished, run it a second time.  This will (or should) install the driver.

IMPORTANT!!!  The installer will bring up a 2nd installer during the install process.  DO NOT click on any buttons in the first installer window until the 2nd installer has finished and closed its window.  When the 2nd installer window appears, click on any "OK" or "Continue" buttons until it finishes.

Once the 2nd installer has finished AND closed its window, allow the 1st installer to finish.

Plug the SmartBOB into a USB port, open the Device Manager and see if the entry appears in the "Ports (COM & LPT)" category.  If not, contact PMDX support.  If so, try running Mach4 and see if the plug-in can talk to the SmartBOB.  If it can, have fun running your machine!  If not, proceed to step (3).

***************************************************
(4) Generate a SmartBOB plug-in debug log
***************************************************
If the Virtual COM Port driver shows up in Device Manager but you still see the "cannot find a valid SmartBOB device" error, then generate a debug log and send that to us.  The general steps to do this are listed here:
http://www.pmdx.com/PMDX-Forums/index.php?topic=97.0

You will need to start Mach4, then click on "OK" to clear the error messages.  Once at the main Mach4 window, enable the debug log as described in the link above.  Exit Mach4, then re-start Mach4.  Then disable the debug log as described in the link above.  And finally, create a "profile package" as described in the link above, then exit Mach4.  Send the profile packet to PMDX support.

[modified 6 Aug 2016 to add "check the easy things" section]

8
The Mach4Hobby plugin for the SmartBOB-USB family of controllers has been updated to version 0.33.159, released 6 November 2015.  This plug-in tested with Mach4 builds 2313 through 2763 and should work with later builds unless the API is changed.

** PLEASE READ THE RELEASE NOTES !!  They contain important information about using these new features and bug fixes.

New features since Version 0.31.147:
  • The real-time status display shows the PWM signal if assigned to the SmartBOB Pin16 or Pin17. Does not show the PWM signal when using a PMDX-407. The real-time display now also shows the values of the step and direction pins.
  • Enhanced the debug log capability to include information from the SmartBOB device.
  • Enhanced USB communication error recovery.
  • Closes debug log files before Mach4 creates its "package" (from the Help->Support menu) and then re-opens them afterwards. This allows the log files to be included in the package even if they were open.

Bug fixes since version 0.31.147:
  • Fixed a bug in the PMDX-411 firmware that prevented the spindle PWM signal from appearing on Pin16.
  • Fixed a bug that re-mapped the charge pump signal to Pin17 if it was mapped to any other SmartBOB output pin.
  • Fixed issue with motion planner interface that mis-reported the actual position for certain moves. The result was that the ending position for subsequent moves would be off by a couple of step pulses. This happened when the motor tuning parameters had a slow max velocity and a slow acceleration/deceleration rate.
  • Fixed a bug that required exiting Mach4 and re-starting it in order to disable "Wildhorse Probe" mode or "Expanded Inputs" mode.
  • No longer overwrite fixture offset table when homing an axis.
  • Fix memory access error in USB interface.
  • Fix memory access error in configuration dialog.

Full details HERE: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_33_159.html

This updated plug-in can be downloaded HERE:  http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In

11
The Mach4Hobby plugin for the SmartBOB-USB family of controllers has been updated to version 0.30.136, released 1 August 2015.  This plug-in works with Mach4 builds 2313 through 2580

** PLEASE READ THE RELEASE NOTES !! They contain important information about using these new features and bug fixes.

New features since Version 0.27.128:

    Added a real-time Input/Output status display to plug-in diagnostics dialog.

    The plug-inc onfiguration and diagnostics screens now include the current screen set name

Bug Fixes Since Version 0.27.128:

    Fixed bug that caused plug-in to report incorrect probe position for G31 commands.

    Changed the algorithm used to find the SmartBOB communications port to avoid issues with some
     Bluetooth modems on Windows 8.1


Full details HERE: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_30_136.html

This updated plug-in can be downloaded HERE:  http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In

12
The Mach4Hobby plugin for the SmartBOB-USB family of controllers has been updated to version 0.29.128, released 16 July 2015.  This plug-in works with Mach4 builds 2313 through 2522.

** PLEASE READ THE RELEASE NOTES !! They contain important information about using these new features and bug fixes.

New features since Version 0.26.117:

    Added support for G31 probing (see Probing Features and Restrictions for more information).

    Homing supports the CYCLE STOP button

    If the SmartBOB is selected as the motion device, the plug-in checks the motor and axis configuration and
    reports an error if a motor is disabled and is assigned/mapped to an axis that is enabled.

    Decreased the distance that homing moves the axis onto the home switch before stopping, and increased
    the speed used to move the axis back off of the home switch.

Bug Fixes Since Version 0.26.117:

    Fixed installer bug that failed to detect Mach4 Industrial running during the installation process.

    Add work-around for startup issue in Mach4 that prevented Mach4 from properly interpreting input
    signals from our plug-in on startup.

    No longer report a motor configuration error if the motor is disabled and NOT assigned to an axis.


Full details HERE: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_29_128.html

This updated plug-in can be downloaded HERE:  http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In

13
The Mach4Hobby plugin for the SmartBOB-USB family of controllers has been updated to version 0.25.111, released 8 May 2015.  This plug-in works with Mach4 builds 2313 through 2336.  It DOES NOT work with build 2441.

Changes for this release include:

(1) Supports 20 microsecond step pulse widths (used mainly with Sherline stepper drivers)

(2) Fixed issue that caused the axis DROs to occasionally display incorrect data

(3) Fixed bug that did not always update step pulse width

(4) Fixed an issue that occasionally caused Mach4 to hang when exiting the SmartBOB plug-in configuration dialog

Full details HERE: http://www.pmdx.com/Downloads_/ReleaseNotes_Ver_0_25_111.html

This updated plug-in can be downloaded HERE:  http://www.pmdx.com/PMDX-SmartBOB-USB-Plug-In

14
*******************************************************************************
This page is obsolete and maintained here for historical purposes.
Please visit the page on the new PMDX FAQ site here:

http://faq.pmdx.com/content/2/4/en/how-to-report-a-problem-what-to-tell-us.html

or

http://faq.pmdx.com/index.php?solution_id=1003

*******************************************************************************

There are several pieces of information that we almost always need to know in order to help figure out what might be happening (or not happening) with your machine.  It helps to have that information when you first report an issue.  That saves us the time of replying and asking you a bunch of questions, and then you having to reply again.

So here is a list of things you should include with any problem report:

(1) What version of Windows are you running, including whether it is a 32-bit or 64-bit variation.  For example, XP 32-bit, Win7 64-bit, etc.

(2) What version of Mach4 (see http://www.pmdx.com/PMDX-Forums/index.php?topic=73.0)?  And please don't tell us "the latest version".  By getting the version number from Mach4 as it is running, you help us verify that you are indeed running the version that you think you are running.

(3) What version of our plug-in (see http://www.pmdx.com/PMDX-Forums/index.php?topic=73.0).  And again, please don't tell us "the latest version".  We need to verify that you are indeed running the version that you think you are running.

(4) If there is any message in the Mach4 message box (in the lower left corner of that mach4 screen), then click on the "History" button and save the contents to a file (alas, you cannot copy it directly to the Windows clipboard), then copy the contents of that file into your post.  Or attach the file to your post if it is a large file.

(5) Did you see any pop-up error messages?  If so, try to tell us what they said

(6) When describing your issue, try to describe the exact behavior that you are seeing.  If the motion is not what you expect, describe HOW it is not.  Did it move more or less than you expected.  Did the actual motion match what the DRO shows?

(7) Is the issue reproducible?  Every time?  Or once in a while?

15
*******************************************************************************
This page is obsolete and maintained here for historical purposes.
Please visit the page on the new PMDX FAQ site here:

http://faq.pmdx.com/content/3/3/en/how-to-capture-a-debug-log-file-and-send-to-pmdx.html

or

http://faq.pmdx.com/index.php?solution_id=1002

*******************************************************************************

Sometimes we will ask you to to enable the SmartBOB Plug-in's debug log, run a test for us and then send us the resulting log file.  Here are the steps you need to do this:

(1) Display the SmartBOB plug-in configuration dialog box.  To do so, with Mach4 running select the "Configure" menu, highlight "Plugins" and then select the "PMDX-SmartBOBUSB" (see the first image below).  In older versions of Mach4, go to the "Configure" menu and select "Plugins". Then click on the "Configure" button on the "PMDX-SmartBOB-USB" line.

(2) Enable the debug log: click on the "Debug" tab (see 2nd image), the change the settings as instructed by PMDX.  Usually this will be "Debug Mode" set to "Debug" and "Debug Device" set to "File" (see the 3rd image).  BUT NOT ALWAYS!!!

(3) Save settings and exit Mach4: click on "OK" to close the SmartBOB configuration dialog, then "OK" again to close the plug-in configuration window.

(4) OPTIONAL (and recommended unless instructed by PMDX to *NOT* do this): Restart Mach4  - exit Mach4, wait at least 10 seconds, then re-run Mach4.

(5) Run the test as described by PMDX.  Make notes of every step that you do.  For example: started Mach4, did a "Ref All Home", jogged the X axis 3 inches to the right, etc.  We will need that information to help process the log file.

(6) Disable the debug log: Go back to the SmartBOB "debug" configuration tab (see steps 1 and 2 above).  Click on the "Restore Default Settings" button (see 4th image).  Click on "OK" to close the SmartBOB configuration window, then "OK" again to close the Mach4 plug-in configuration dialog.

(7) Exit Mach4

(8) Send PMDX the debug log file.  If you are running Mach4 build 2580 or higher there is a function built in to Mach4 to create a "package", which you can then send to us.  This package includes all of the files associated with the current Mach4 profile (including our log files) as well as a copy of your screen set.  To create this package, go to the Mach4 "Help" menu and select "Support", and then "Package Current Profile".  By default Mach4 will save this in the Mach4 installation directory (usually C:Mach4Hoby), but you have the option of saving the file somewhere else.  Send us this file.

If you are running an older Mach4 build (earlier than 2580), then you will have to send the log file to us yourself.  The log file is named "PMDX-SmartBOB-USB.log" and will be stored in one of two places, depending on which version of our plug-in you are running.  In the examples below I presume that you installed Mach4 in the default "C:Mach4Hobby" directory.  If you installed Mach4 in a different directory, then substitute the actual install directory where you see "C:Mach4Hobby".  For example, if you installed Mach4 in the default location of "C:Mach4Hobby", the log file will be:

       For plug-in versions 0.30.136 (released 2 Aug 2015) and newer:
             C:Mach4HobbyProfilesYOUR_PROFILE_NAMEPMDX-SmartBOB-USB.log
       where "YOUR_PROFILE_NAME" is the name of the Mach4 profile that you are running.

       For plug-in versions 0.29.128 (16 Jul 2015) and older:
             C:Mach4HobbyPluginsPMDX-SmartBOB-USBPMDX-SmartBOB-USB.log

Send that file to us as an attachment to an email, sent to the email address given you by PMDX support.

[editied 22 Mar 2016 to update for new Mach4 build 2914 menu structure and add images of important steps]
[edited 15 Sep 2015 to show log file location for newer plug-in releases and added Mach4 "Package Profile" feature]

Pages: [1] 2