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 - thebuildbug

Pages: [1]
1
SmartBOB controllers and dedicated accessories / Re: PMDX 424 inputs
« on: April 16, 2020, 01:45:28 PM »
It seems you have two options

1) Add inputs to your design.

   There are add on boards like the PMDX-108-INPUT (requires PC Parallel Port) and similar products that you can use to add inputs to your system.
   Obviously you become the integration engineer on what ever board you choose. I have not done this so I'll leave more detailed advice to others.
   
2) Combine some of the inputs you already have.

   I'm assuming you are using the 6 proximity switches (two per axis) as limit switches for your machine.
   If this is NOT the case, this suggestion may not apply.
   It's possible to rewire your existing proximity switches to only require 3 of the inputs
   (one per axis). Here's a link to a more detailed description
   
   https://github.com/gnea/grbl/wiki/Wiring-Limit-Switches
   
   The example in the link above uses limit switches but the principle is the same for proximity switches.
   For N.O. proximity switches you would wire them in parallel, and N.C. switches you would wire them in series.
   
   Mach4 doesn't really care which proximity switch is firing (when it's acting as a limit switch), all it knows is that when any proximity switch fires all motion is stopped. It's sometimes useful
   for the operator to be told which switch caused the stop but this may be a feature you weigh against your current problem.

2
Hello,

I'm using a PMDX-424/PMDX-407 to control a home built woodworking CNC mill. The mill
is up and running well, yet I'm having problems with probing motions.

                 Mach4: Hobby 4.2.0.4300
           PMDX-424: [Rev D PCB]
        PMDX Plugin: 0.53.263
PMDX Bootloader: 1.15.76
  PMDX Firmware: 0.60.208
                      OS: Windows 10 Pro (64-bit)

While probing I'm intermittently encountering one of the following problems (they do not occur simultaneously).

1) The tool strikes the touch plate, motion stops, and Mach4 is disabled.
    Frequency of occurrence: ~ 1 in 4 probing attempts
    This results in the following error in the log file (see attached log)
         2020-03-21 16:34:04.559 - PMDX [ERROR]: Too many discarded motion samples after sync
         2020-03-21 16:34:04.559 - PMDX [INFO]: MachEnable(0) from 'looking for sync pos from motion planner'
         2020-03-21 16:34:04.559 - API: mcCntlEnable(inst = 0, FALSE) (PMDX-SmartBOB-USB)
   When this occurs I'm able to re-enable, jog the machine, submit gcode via the MDI, and try again (Mach4 & PMDX plugin seem to recover)

or

2) The tool strikes the touch plate and Mach4 becomes unresponsive. Clicking anywhere in
   Mach4 GUI results in an hour glass cursor appearing. Windows reports Mach4 is "Not Responding"
   and I'm forced to kill the Mach4 process and restart. I have not been able to retrieve a log when this occurs.
   Frequency of occurrence: ~ 1 in 10 probing attempts
   
Sometimes the probing will work perfectly for a while and then starts having problems again.   
   
Example Gcode:
  F10
  G31 Z-2.0000
(The gcode is submitted by a button in Mach4 using the API i.e. mc.mcCntlGcodeExecuteWait(INST, myGcodeCmd))

Any help would be greatly appreciated.
Thanks

Pages: [1]