Messages

1

Mach4 General Discussion / Mach4 Rotary Feedrate

« on: June 18, 2017, 01:11:21 PM »

Hey Everyone,

Currently running a system that uses the following for cutting tubing:

X-Axis (Tubing Sliding forward and back)
Y-Axis (Rotation of tube based on circumference)

My Y-axis is setup to where I need to enter counts per unit based on a circumference of a tube. To my understanding this is just about how everyone is doing it. This treats the tube as if it were just cutting flat sheet.

However, I am determined to find a solution to make it work with the Y-Axis reading a 0-360 degree to rotate the tube.

Unlike Mach3, I cannot find any way for the user to input a rotational radius for Mach to adjust the feedrate for the angular Y-axis commands.

Desired control would be as follows:
X-axis (tubing sliding forward and back)
Y-axis (angular 0-360 commands)
Diameter input (input to tell mach at what rotational diameter the tube is to compensate the feedrate for the angular commands)

Does anyone know how to make this happen in Mach 4?

Thanks!

2

HiCON Motion Controller / HiCON Board Review

« on: December 15, 2015, 01:35:46 AM »

I am the crazy guy that decided to build my own laser... what a journey it has been, from the design all the way to the finished product. Nearly 6 months of teaching myself new things. In the end I ended up with a 30 foot laser plate and tube cutter capable of cutting square or round tube up to 24 feet long.

I started out with a company called Camsoft (terrible experience, going to leave it at that) and was making my journey down to figure out what to do next. I always ventured the idea of using Mach but never looked at it as a source that would be able to handle what I could do. After further researched, I came across Mach 4 and wanted to give it a try. With a laser, it is necessary to be able to control all aspects such as the I/O and each individual axis.

After days of research and forum reading I came across Vital Systems. Spent a lot of time on the phone with these guys and ended up having a board overnighted to me. First thoughts unpackaging the item were great. Quality was everywhere throughout the board and uses reputable brands for circuitry components. Had the board wired up in my control box and had the system running my machine in a matter of minutes. There is a bit of a learning curve with Mach 4, but once you learn how to use it, program the screen, write lua, then your limits are your imagination.

The guys at Vital Systems provide hands down the best customer service in the industry. I cannot even explain how wonderful and helpful they are. I am using there arcpro screen for Mach4, which is used to give the height following controls that you find in Mach3 to be available in Mach4. The arc pro screen is the only one of its kind for Mach4. I spent a lot of time with them giving them feedback and things I would like to see and I would receive updates for the program within the same day. This really shows that they are listening and they care about what they have to offer.  

Every question and concern I had they were able to help me. As of right now I have a ton of hours (days) on my board and not a single problem. Absolutely wonderful, and connects to my computer every time. I never have any connectivity problems. It is just a flawless system. I am going to stop preaching about this and say...  buy this board!!!

3

Mach4 General Discussion / Mach4 Macros to enable outputs in an order

« on: August 18, 2015, 11:49:29 AM »

Hey Everyone!
I am new to the forum. Figured after reading and getting so much help from all the topics, that I should share with people what I am working on. For my senior project, me and several other students designed and built a 30 foot laser cutting machine. Absolutely massive. I am using Mach4 to get it going. I wanted to get some feedback on some of the coding that I have stirred up. Let me know if I am wayyyy off or if it looks just about right. The laser has to receive three outputs in the order given below. The M codes will be called out in the post and should be run at every pen down and pen up from the cam program. I am using a Hicon Integra board as well. The board I am setting up today and that is why I have not tested yet. If the code is right, then I am happy I posted it for everyone to share if they need to make something similar happen.

When M101 is called:
1) Turn on gas (output 3)
2) Open shutter (output 2)
3) pause for 0.25 seconds
4) Enable beam (output 1)

Code for M101:

function m101()
    local inst= mc.mcGetInstance();

    local out1= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT1);
    local out2= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT2);
    local out3= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT3);

    mc.mcSignalSetState(out3, true);
    mc.mcSignalSetState(out2, true);
    wx,wxMicroSleep(250);--250ms delay
    mc.mcSignalSetState(out1, true);
end

When M102 is called:
1) Disable beam (output 1)
2) pause for 0.25 seconds
3) Close Shutter (output 2)
4) Turn gas off (output 3)


Code for M102:

function m102()
    local inst= mc.mcGetInstance();

    local out1= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT1);
    local out2= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT2);
    local out3= mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT3);

    mc.mcSignalSetState(out1, false);
    wx,wxMicroSleep(250);--250ms delay
    mc.mcSignalSetState(out2, false);
    mc.mcSignalSetState(out3, false);
end