m7 m9 and other things

[kawarider]

Hello,
Last week switched from mach3 to UCCNC with proma thc. Neuron Lite is with a friend that burned his, hope to change that too in the near future.
Table is an old esab rebuild and now 3-1,5m
Hypertherm powermax45. I know 65 is better but this one is doing the job now for one year and I am very happy with it.

Now, a friend wrote some code via brains in mach3 for the fumes extractor and that's lost now in uccnc. It would be nice if the fan start at run program and stops 10 sec after end program. What is the easiest way of arranging this? I am not to familiar with progamming or macro's but happy to get all things wired up the right way so far.

Any ideas would be more than welcome.

Thanks

[cncdrive]

You can write "brains" in the UCCNC, it is called macroloops. You can write them just like in Mach3...

[kawarider]

Yes, thanks for pointing me in the right direction. First time for everything, so I am very unsure about all this.

I am trying macroloop with callbutton(19) en then start coolmist, but no idea if I am doing the right thing. Any simple example? M7 because in spindle setting fan runs 10 sec longer.

Thanks

[kawarider]

So far this is the result, There is some error somewhere.
Hopefully it's something small. Can anyone have a look?
It would be very nice, the machine has to start running again.
Thanks

[kawarider]

This works better. Only at the end of the program code everything stops, mist (fan) included. M9 is programmed with delay 10 sec. M30 overrules this probably. Let's see if it's possible to macro direct to an output.

[kawarider]

Yahoo! It works! First steps in macro's!

[kawarider]

UCcnc is great! Love it already and haven't even cut anything yet! Reliable dry running went from 15 m/min with mach paralel port to more then 20 m/min! That was not expected. Brains is a little complicated ,as far as I looked over a shoulder, compared to macroloops. Very easy to change a macro.

Thanks, looking forward to start working with uccnc!

[cncdrive]

Just some help for your coding:

- You find an error text file in the macros folder if a macro compiles with an error.
From the error text you can get some ideas about what error the macro code has. It helps debugging.

- In the newest test release 1.2108 you can redirect the compile error text to the debugger console of the console plugin. You just have to enable the console plugin and check that checkbox and then you can see the macro compile error text in the console window.

[kawarider]

Very nice, and in Dutch! How is that possible?

[cncdrive]

Because it is handled by the .NET framework and if it is Dutch then...