Messages

201

Mach4 General Discussion / Re: Disable cycle Start button using external input

« on: December 08, 2020, 05:11:39 PM »

Hey,
So you can probably do by getting the screen property, but you could also just edit the Cycle Start function to not run unless the input is active. 
I have a small mill in the shop that I messed with the Cycle Start function to not run unless all axis are homed.  I just added in another "if" statement in the function.  If one of the axis aren't homed, set a message telling the operator to home the machine. 
That's just one option.

202

Mach4 General Discussion / Re: This function is unlicensed?!

« on: November 02, 2020, 09:06:57 AM »

I know that the renishaw subrprograms have a lot of "safety features"
They probe so far in one direction and if nothing happens it stops the macro and gives you an error.  You'll need to get the industrial version to use those types of functions.
You could write your own probing routines and not use the conditional aspects of the Renishaw routines.
I wrote a tool setting routine that works wonderfully.  I don't like using Mach4 Macros to do probing, I like MacroB programs to handle probing and tool setting.  Much safer IMHO. 

203

Mach4 General Discussion / Re: This function is unlicensed?!

« on: October 26, 2020, 09:27:30 AM »

It will work with any probe, but like Graham said, you'll need industrial license as well as the sub routines that are being called from that program. 
Every G65P#### is a separate sub program for the probing routine.  Those will have to come from renishaw or you may be able to find them online somewhere or you can write your own, but you'll need to understand what the probing routines do to make it a safe routine. 

204

Mach4 General Discussion / Re: This function is unlicensed?!

« on: October 20, 2020, 09:40:45 AM »

Can you post the probing routine that is output from your post processor? 

205

Mach4 General Discussion / Re: Mach4 feature vs Mach3

« on: April 29, 2020, 09:42:29 AM »

I will second everything that has been said so far, especially the Zero Brane editor and the Modbus communication.  I use PLCs with TCP Modbus to handle most of the IO on the larger machines that I retrofit at work.  it is so fast and easy to set up and I don't have to worry about anything because PLCs are incredibly robust.

The flexibility with the screen editor is pretty cool too. 
I totally redid the OD Grinders we have in the shop by making my own custom screen full of buttons, leds, user input boxes, etc... I was able to use Mach4 industrial to make a pretty solid Macro Program.  I basically made one giant conversational screen right in Mach4 and the operator has all the controls right on the main screen.

As far as machining goes, Mach3 was good for machining but Mach4 IMHO is so much better, it handles High Speed Machining toolpaths far better, in my experience, over Mach3.  As far as G Code goes, it is more particular about what is needed to run, mainly in canned cycles, but to me that means it is a much more robust G Code interpreter than Mach3.

206

Mach4 General Discussion / Re: Mach4 in Fusion 360 Post Processor

« on: April 29, 2020, 09:34:28 AM »

RecceDG
Here is a post processor that I edited to use Mist.
Be aware this post will also give you the option to use a mist collector, you will see it in the post properties.  It will output "m115" at the beginning of a program and will output "m116" at the end of a program is enabled.

207

Mach4 General Discussion / Re: Interface with Industrial PLC (Ethernet or other options)

« on: April 29, 2020, 08:44:51 AM »

Mach4 has TCP Modbus.  You just set it up in the modubs configuration.   I have 5 or 6 machines here in the shop that I'm using the Click PLC from Automation Direct and communicating with TCP Modbus.  I use it to handle most  of my IO. 

208

Mach4 Toolbox / Re: mach 4 plasma tool off set

« on: March 26, 2020, 11:48:05 AM »

It's been a while on this thread, but can you post the code that I sent you?  I don't remember how I helped you out and someone else is asking about this as well.
Thanks!

209

Mach4 General Discussion / Re: Weird problems.

« on: December 31, 2019, 04:26:59 PM »

I just found out (by happy accident) that the debugging will work if you choose "Open script editor" and not "Edit debug scripts".
I am also able to get the state of an input now.  I'm not sure what I changed, but it works now so I'm happy. 
The LEDs still don't work correctly all the time though.

210

Mach4 General Discussion / Weird problems.

« on: December 31, 2019, 03:20:28 PM »

I'm working on a lathe at the moment and I'm running into some issues.
1.  Zero Brane won't let me step through and debugg a macro.  I start debugging and it just runs through it.  It doesn't even really run through it because it doesn't show any results that I have requested in the macro (mc.mccntlSetLastErorr()).  I have to run the macro from MDI to test it, it is very cumbersome.  This happened on a mill I worked on recently as well. Both running Mach4 Build 4300.

2.  I'm trying to get a visual representation of what Gear the lathe is in.  I have a dc linear actuator that changes the spindle gear.  This actuator has two limit switches on it to tell my PLC when it reaches it's limit to shut off the gear motor, I have two LED's set up in Mach to monitor the input state.  This isn't working correctly.  It doesn't update unless I go into Machine Config and exit out of the config screen then it will update the LEDs.  I have no idea why this isn't changing correctly. 

3.  I tried to bypass this and just force the LED value to 1 but the code I use to do this on other machines doesn't seem to work. 
scr.SetProperty ("ledTest", "Value", 1 or 0)
I try and run this in a macro and it doesn't change anything. 

4.  How do you get the state of an input?  Usually I get the handle, get the state of the handle and then use that state.  I have done this a lot in the past, but it isn't working right on this lathe.  I'm wondering if it has something to do with the Zero Brane editor.

Anyone have any ideas on these issues?