Messages

1

SmartBOB controllers and dedicated accessories / Re: Proximity Homing switches led blinks

« on: November 11, 2020, 05:47:37 PM »

OK. After reading your response I went back and discovered that a wire common to all the proximity detectors was loose and the devices probably were not getting enough voltage/current.
Tightened things up and everything is back to normal.

By the way, I am powering them from a separate 24 volt supply and not from the +5 on the board.

Thanks for the quick response.

Chuck

2

SmartBOB controllers and dedicated accessories / Proximity Homing switches led blinks

« on: November 11, 2020, 02:57:59 PM »

I have the PMDX 416 ( 53.263, 1.13.73, 0.60.208 and Mach4 build 4300)

Machine was working fine but now all of my proximity switches are blinking when they were normally lit steadily. They do not react to metal as they should.
I have looked through the setup files and don't see anything different.

Reloaded software/firmware but did not change.

I also went back to an earlier initialization and that had no effect.

Only light lit on the PMDX 416 is the yellow power light.

Any ideas on what to check? Has my board failed?

Thanks

3

SmartBOB controllers and dedicated accessories / motor35 and disable with probe action

« on: January 07, 2018, 05:05:55 PM »

I am have been having a heck of a time with my system disabling itself after:
- any probe action via the Probing tab or the TouchOff
- anytime I jog to a location then press Work Zero button
- anytime I jog to a location and enter a MIDI command G00 G90 GX0 (for example)

The Log facility is consistent with output in all of these situations and shows a Requesting a stopped report for motor35.
Following this is what appears to be a report from my 4 motors but not one from motor35.
What is motor35? I don't have one but there is one in the ini file that is enabled. Disabling motor35 has no effect.
At this point my Enable button still shows enabled but my jog keys are all dim and the machine can't be moved until I press the enable key twice.
I have opened a ticket with Artsoft but have not heard anything yet.

I completely rebuilt my setup and reinstalled PMDX and Mach4 then reconfigured the motors and the switches.

Here is a sample of the Log report: (Mach4)(jogged out on X and Y and Z away from my work zero position.  Then pressed the Work Zero button)

2018-01-07 13:49:45.399 - API: mcCntlMdiExecute(inst = 0, commands = 'G00 G90
G00 G53 Z0
G00 X0 Y0
G00 Z0') (Mach4GUI LUA script)
2018-01-07 13:49:45.500 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1875
2018-01-07 13:49:45.500 - S_IDLE_on_exit
2018-01-07 13:49:45.500 - ACTION_start_mdi
2018-01-07 13:49:45.501 - S_MDI_RUNNING_on_entry
2018-01-07 13:49:45.501 - S_MDI_RUNNING2_on_entry
2018-01-07 13:49:45.501 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2018-01-07 13:49:45.503 - Waiting on SetStill...
2018-01-07 13:49:47.085 - Controller::RunCanonBuffer called AddStopReportRequest() RunCanon.cpp:85
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 0 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 0.
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 1 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 1.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 3.
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 2 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 2.
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 3 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 35.
2018-01-07 13:49:47.108 - API: mcMotionSetStill(inst = 0, motor = 2) (unknown caller)
2018-01-07 13:49:47.332 - API: mcMotionSetStill(inst = 0, motor = 0) (unknown caller)
2018-01-07 13:49:47.332 - API: mcMotionSetStill(inst = 0, motor = 1) (unknown caller)
2018-01-07 13:49:47.332 - API: mcMotionSetStill(inst = 0, motor = 3) (unknown caller)

I really don't know if this is a Mach4 or PMDX issue.
I have a PMDX 416 and Mach4 build 3481

Appreciate any help with this issue.
Chuck