Messages

1

Mach Screens / Re: Saving Button Script - .set or .m1s?

« on: May 21, 2020, 02:39:46 PM »

.mcc files are compiles lua chunks and are applicable in Mach4 only.
Craig

No, the Mach3 editor allows you to save as an M1S ("Basic" text file) or an MCC file.

If you look at the MCC file in a binary editor, it still shows the text of most (all?) of the non-built-in commands, but not the numbers, and not (I think) statements like for(), if etc,.  I assume the numbers are in binary in the same position as in the original, but things like:
Code "G1 x23.5"
are still there, although it looks like it's in unicode.  Again, not sure, I haven't looked further than a cursory glance.

To me it looks like what used to be called "Pre-compiled" code, which is then used by an interpreter to speed the process at runtime.  The question is, does it in fact increase speed in the real world (saving a noticeable amount of time) or is it a hold-over from when machines ran slower, or is it just so vendors can help keep proprietary information secret?

2

General Mach Discussion / Homing-offsets and pullback

« on: May 20, 2020, 09:10:02 PM »

I had the machine I'm working on with Mach3 all set, and then the guy I am helping decided he wants Mach4, and Mach3 until he's comfortable with 4.  So he changed to a different interface, Ethernet SmoothStepper, and I'm trying to get it set.

I'm learning this as I go along, so big gaps in my Mach3 (and 4) knowledge, I'm a factory automation/motion control programmer professionally, but new (ish) to CNC.

I'm trying to get back to where I was in Mach3, and now the homing is different.  It used to go to the home switch, back off a bit, touch it again, back off again, and then set the values set in the Home Offset Settings.

Now, after copying all the settings to make the new settings with the new driver, the home routines for X Y and Z hit the home switch and stay on it.  The odd part is that the Y and Z seem to back off enough to turn off the switch, while the X stays on the switch (In the debug screen it shows the X Home switch still active).  Although maybe that's just that the motor jumps back a half step when stopped?

The only option in the ESS Setup it seems is for their DLLs to control all of the homing.  I would think that the amount to back off after hitting the home switches should be a setting somewhere, but I can't find it!  I was even told by someone that there is a place to set that, but they don't remember where.

Any ideas?  Was the homing being done by the original driver, and I just didn't know it, and that's why it did the double touch etc, or is there a macro that was changed, or what?

Thanks!

3

Screen designer tips and tutorials / Re: Is there a way to make an OEM DRO read-only?

« on: May 05, 2020, 05:19:38 PM »

Yes, I poked around and finally figured it out, I hadn't used the multiple selection up until now.  I then was embarrassed to find the "Swap Layer" under the Edit menu.
  Thanks!

4

Screen designer tips and tutorials / Re: Is there a way to make an OEM DRO read-only?

« on: May 05, 2020, 09:42:31 AM »

Try to change levels (perhaps the DRO is on top of the image button).

I have looked, and can't figure out how to change levels!  One would think there would be a Z-order, like "move Back" or whatever.  How is this done?

5

Screen designer tips and tutorials / Re: Is there a way to make an OEM DRO read-only?

« on: May 03, 2020, 04:21:30 AM »

I tried that, it didn't seem to work.

6

Mach Screens / Re: Saving Button Script - .set or .m1s?

« on: May 02, 2020, 12:06:57 PM »

In addition to that question, is there a speed increase, either theoretical or if anyone has noticed actual increases if you save scripts as .mcc files instead of m1c?

7

Screen designer tips and tutorials / Is there a way to make an OEM DRO read-only?

« on: May 02, 2020, 05:54:02 AM »

I would like to make it impossible for the user to change some OEM DROs, and only update them from scripts.  Any way to do this?

Or, alternatively is there a mechanism to get a notification when a DRO is modified by the user so that other dros can be suitable updated?

Thanks

8

General Mach Discussion / Re: Mach3, G31 probe on Z axis, and variable 2002

« on: April 27, 2020, 11:46:30 AM »

And by the way if you read it you will discover that a g31 does not retract....contrary to your belief, the retract requires
a second gcode move.

I was just quoting the documentation that came from Artsofty with Mach3, and it was just a side note!  Why does everyone focus on this one thing?  I never thought it would retract back up to original position or anything, it simply said it retracted a little, which it does not!

9

General Mach Discussion / Re: Mach3, G31 probe on Z axis, and variable 2002

« on: April 25, 2020, 05:53:39 PM »

The same reason why it says G73 retracts, the documentation is wrong.

Ugg, I'll watch for that!

Does Mach4 have either better documentation or stick better to ansi standards?

10

General Mach Discussion / Re: Mach3, G31 probe on Z axis, and variable 2002

« on: April 25, 2020, 05:37:15 PM »

Analyze this code to figure out how touchoff is working.
It does NOT retract automatically after contact.

Yes, I know, my side question about that is why does Artsoft specifically mention that it does retract back to the 2002 position, when in fact it does not?