Messages

1

VB and the development of wizards / Re: Probing with PoKeys57CNC

« on: October 12, 2017, 07:29:39 AM »

Update again - Testing is done:

It works! PoKeys fixed the trouble with their plugin Version 3.12, after which the probing Trigger coordinates are properly written into the according Mach #2000 to #2005 -variables...


3.12 - 5.10.2017
- probing reporting to Mach3 improved

3.11 - 5.10.2017
- PoKeys device does not switch to STOPPED mode before doing the axis homing


And: The PoKeys guys are really fast. - My appreciation!  :-)

2

VB and the development of wizards / Re: Probing with PoKeys57CNC

« on: October 05, 2017, 04:35:48 PM »

Update:
PoKeys published an updated plugin an hour ago, which should improve the reporting of probing results to the Mach3 system variables. 
Wow, they're fast... 

I will not be able to test this before the weekend, as I am not at my workshop at the moment.


Have a nice evening,
Konrad

3

VB and the development of wizards / Probing with PoKeys57CNC

« on: October 05, 2017, 12:03:32 PM »

Hello everyone,

I just upgraded my highly appreciated Mach3 / parallel port driven mill to a PoKeys57CNC device. 

Unfortunately, although probing seemed to work fine on a first sight (probe connection works, G31 command is executed nice - machine stops as soon as probe is triggered) I've got a strange problem: the #2000 to #2005 variables, which should contain the probe trigger coordinates, are all "0" after execution of G31 command.   

TriggerPointX = GetVar(2000)
TriggerPointY = GetVar(2001)
TriggerPointZ = GetVar(2002)

--> To get machine running again, as I had to get some work done on it, I changed the relevant probing script to do the probing veeery slooow and polled the according X, Y and Z DROs, which is suitable as a temporary solution.

So, my question is:
- Who exerienced similar probing trouble with a PoKeys57CNC board.
- Maybe, PoKeys plugin has an own place to put the trigger coordinates to, which I don't know.
- Did I misconfigure Mach3 or PoKeys plugin, so probing basically work, but the plugin isn't able to write the trigger coordinates to the according variables

I'm happy about any help or Information.

regards, Konrad

4

General Mach Discussion / Re: Charge pump error in version R3.043.050

« on: November 07, 2011, 04:01:39 PM »

---> resolved?  Or is this issue still existing and needs a software-fix by Brian?


Konrad

5

General Mach Discussion / Re: Keygrabber improvements

« on: January 27, 2011, 02:53:22 PM »

What about this:

Profiles:

If you have different Mach profiles then save the config with a different name (it must be put in the Mach folder). Now edit your Mach shortcut and add the config filename directly after KeyGrabber.exe. For example C:\Mach3\KeyGrabber.exe Turn.grab /p Mach3Turn would open the turn.grab config file. The /p Mach3Turn will still be passed on to Mach3.
 
By the way: There is a "KeyGrabberReadMe.doc" in the Mach directory which explains how the keygrabber works.


best regards,
Konrad

6

General Mach Discussion / Re: New development version

« on: January 23, 2011, 05:27:33 PM »

OK, that's it...
There's a transparent image button in front of the led.

The behavior is the same on version 3.043.22.

Do you know a way to cure it?

 

7

General Mach Discussion / Re: New development version

« on: January 23, 2011, 03:22:42 PM »

Hi Gerry,

version is 3.042.40.

Trouble is, that sometimes some LEDs are showing a wrong state - so they do not update correctly.

I've got this trouble on cycle start and axis ref'd LEDs.

regard, konrad

8

General Mach Discussion / Re: New development version

« on: January 23, 2011, 03:08:19 PM »

Hi all,

I just noticed that the development version jumped from 3.043.22 to 3.043.26.
Does anybody know what's new in it?

(Is there a place where to find information about development versions like a change-log?)

regards, Konrad

And the link to the lockdown version now delivers the 3.043.22, which was the old development version, and the change-log doesn't mention it.

--> Reason of my stupid questions: I am working on a screenset and I am suffering from trouble with the update of LEDs.
I am wondering wether the new versions could deliver a solution for this trouble, as they were used to develope the all new "mach standard mill" screenset.
On the other hand, I want to avoid paying for this with other, new trouble coming with the development version...

Thanks for your hints...

best regards,
Konrad

9

General Mach Discussion / New development version

« on: January 23, 2011, 02:37:51 PM »

Hi all,

I just noticed that the development version jumped from 3.043.22 to 3.043.26.
Does anybody know what's new in it?

(Is there a place where to find information about development versions like a change-log?)

regards, Konrad

10

General Mach Discussion / Re: Mach did again!

« on: October 22, 2010, 10:04:34 AM »

Hello Brian.

thanks a lot for your hints.   

As I understand that it isn't easily possible to change a part of the program, on which many users have built their scripts and customisations, I myself took account of the coordinates which are delivered by the "GetToolChangeStart" function in my script.

As of now, everything is working and I am happy.


best regards
Konrad