Messages

1

General Mach Discussion / Re: RFH not working in Plasma

« on: December 04, 2016, 07:35:11 AM »

RFH, set next line, reverse run all = nightmare. IMHO some of the buggyest areas of Mach and VERY version dependent.

What version are you using?

2

General Mach Discussion / Re: Question for Plasma guys on material sensing

« on: December 01, 2016, 11:44:39 AM »

good stuff

3

General Mach Discussion / Re: Arduino and Mach 3

« on: December 01, 2016, 08:35:18 AM »

AFAIK, a GRBL shield is just 3 or 4 small stepper drives on a board that plug into the top of the arduino that's running GRBL. If so kaspis245 could just discard the arduino and wire a PP Mach3 straight into his shield.

4

General Mach Discussion / Re: Question for Plasma guys on material sensing

« on: December 01, 2016, 08:30:55 AM »

Curious. I can't really see why if it works from the MDI, it doesn't when called from gcode.

Just took a look at the CSLabs site M31 macro: This comment makes me wonder:

Probing with M31 macro is done mainly by CSMIO/IP motion controller as an internal function. M31 macro can be freely extended and modified as you wish, what gives an user great opportunities.

Well G31 is always in the controller so I don't get why they've made the first point.

As far as the second point goes, I'm struggling to see what "great opportunities" their macro offers over putting G31 in your own macro.

All sounds a bit kludgy to me.

What happens if you just put a single simple G31 line in a macro? If that doesn't work I think I'd be asking CSLabs why not.

5

General Mach Discussion / Re: Question for Plasma guys on material sensing

« on: December 01, 2016, 07:24:56 AM »

Try putting a while isMoving loop after each of your last two code statements. i.e.

Code: [Select]

Code "G92Z" & PierceHeight                      'Set Z DRO to Pierce Height
While IsMoving()
Wend
Code"G90"                                       'Set back to absolute mode
While IsMoving()
Wend

I'm wondering if the gcode buffer is getting corrupted

6

General Mach Discussion / Re: About V.B. script

« on: November 09, 2016, 11:16:00 AM »

OK - but at least that shows the beep capability is there.

In the cmd window type:

help

you should get a list of all the internal commands - is echo in there?

alternatively you could just try:

echo <Ctrl>G<return>

if not - it looks like echo is not an internal command in W10

7

General Mach Discussion / Re: About V.B. script

« on: November 09, 2016, 10:31:23 AM »

Can you run a cmd window and type:

<Ctrl>G<return>

does that beep?

8

General Mach Discussion / Re: About V.B. script

« on: November 09, 2016, 10:03:37 AM »

what flavor windoze Tweakie? I'm on XP here.

9

General Mach Discussion / Re: About V.B. script

« on: November 09, 2016, 08:10:37 AM »

try the following in CB

Shell "echo " & Chr(7), 2

10

General Mach Discussion / Re: Mdi is not a MODE

« on: November 08, 2016, 12:05:20 PM »

Mike

I think I may know where you went wrong.

I think you've assumed that because Alt-R does nothing on the MDI screen then somehow cycle start can't happen on the MDI screen. That's not the case however.

You hit Alt-R on the Program Run screen and sure enough it does a cycle start. The reason it does that is two-fold. One: there's a button on that screen that has its hot-key code set to Alt-R and two: that button's function is set to cycle start.

On the MDI screen, there simply isn't such a button. That's the only reason ALt-R does nothing. The MDI screen is just a screen - it has no special merit. (Check out the Toolpath screen - you can't jog on it. Why? simply because there's no Jog Control - that's all - a pendant would still allow jogging though)

An OEM trigger is just an input that can be configured to automatically execute an OEM code when it goes active. If that simplistic behavior suits your particular requirements then all well and good. However if your requirements have caveats then triggers are of no use. You have to resort to the dark art of the macropump or brains.