Messages

1

General Mach Discussion / Re: Check this out, I am about to be published in Digital Machinist!!!

« on: July 27, 2013, 11:27:57 PM »

The first being the M74?






Coat, hat, door

2

General Mach Discussion / Re: mach3 jog mode disabled for mdi input

« on: July 21, 2013, 10:06:41 AM »

Well that was quick, thanks Hood!

Change made and all is good again.

ex-egll

3

General Mach Discussion / Re: mach3 jog mode disabled for mdi input

« on: July 21, 2013, 09:43:06 AM »

Thanks Hood, although I dread to think what you may find in there as I have been "playing around" with the system for some time now... changing screens, new macros etc.

4

General Mach Discussion / mach3 jog mode disabled for mdi input

« on: July 20, 2013, 11:02:05 PM »

Hi, recently I have started to get a message "mach3 jog mode disabled for mdi input" whenever I try to enter instructions into the MDI input box. Obviously in my playing around I have altered something, but can't determine what it was. Can anyone help resolve this please?

5

General Mach Discussion / Re: Should this work - Emulated Input Signal

« on: June 16, 2013, 04:10:11 PM »

Thanks for the responses, I'll play with the "real thing".

6

General Mach Discussion / Should this work - Emulated Input Signal

« on: June 11, 2013, 07:32:46 PM »

Hi,

I am a newcomer to the world of CNC, and I am just starting to play around with Mach3 (3.043.066). I have started to look at probing, and after a couple of "interesting" results I would like to try and run in some form of simulated mode, without hardware connected.

I was thinking that using Config / Ports & Pins /Input Signals and then emulating the Probe Input with a Hotkey may work. I have set it up as follows:

Probe Enabled, Port #1, Pin #13, Active Low, Emulated, HotKey 65.

Initial results looked promising, as I had a led (OEMLED(825)) on the screen that would turn green when I pressed the hotkey. I could also test the state of this LED in code and output a message showing the correct state. So far, so good.

Next part of the code uses G31 to move the probe and the IsMoving() function to determine when the probe movement has stopped. This code works ok in the "real world", but in simulation the LED goes on with the hotkey but and the probe keeps moving. I guess that some other means signals G31 that the probe has stopped moving; it does not rely directly on the state of the Probe Input pin.

Is there a way to simulate the probe making contact with the work piece that G31 will respond to.

I realise there are a number of probing routines out there, sometimes I just feel like re-inventing the wheel to keep the grey matter from stagnating too much!