Advanced Search

The best way to know is testing for yourself, it all depends on what you mean by "real work", if you find issues for your use case politely post them here.
I did my own testing, and it is getting closer to my "real work", it is very exciting, but there is still a lot of work, and I'm extremely impressed and grateful to Grotius and co to be tackling this, much appreciated...

Should be fine

Is this the correct type of modbus usb adaper?

www.digikey.ca/en/products/detail/dfrobot/FIT0737/13688358

Will get here friday if I order it now.

Interesting. But for us newbies, how do we use this mesambccc command? There's a detailed description, but no example of how to use it.

Generally people use separate power supplies. Something like a Meanwell MDR-60-24 24 volts and a similar one for 5 volts. Meanwell MDR-10-5?

These are not expensive.

I want to add a rotary encoder to my mill spindle so that I can do rigid tapping. 
I see that there are choices for PPR from 100 to 600. I'm going to be using a Mesa 7i96 card.
Is there a reason to pick one resolution over another?

50:1 would be OK with with thcad 5 volt scale.
on 10v scale, Use 20:1 which is 200 volt full scale. That will be more accurate. It will probably go off that scale briefly when piercing but  it won't matter as we don't care about the voltage until it settles back to cut voltage of about 130 volts. The THCAD can handle the over voltage.

Hi Rodw,

My automation card divider is 50:1 by default but can be set to 80:1, 40:1, 30:1, 20:1, and 16.7:1. Would you still suggest the 20:1 or would the default 50:1 work just as well?

SwitchWitch wrote:

 As you mentioned before usb to rs485 is an option, I will go that way until I will be able to spend the next bucks for an ethercat VFD.

I think once you get that going, you will find it works so well, you will never go to an ethercat VFD.
Does Optidrive have a separate ethercat interface module for your VFD? A number of manufacturers do.

You don't need a relay as your card has 2 amp relays built in to the high current outputs, Use one for the torch on. Adding a relay would just add an additional failure point and add some lag into the signal.
I think your plasma has the same divider as the TD  A120 I had. In which case, use a 30:1 divider without any scaling resistors on the THCAD's 10 volt scale. If you do have a 20:1 divider (I didn't)  you could use that. set the frequency divider to 1/32 and scale the sticker frequency by the same amount when configuring qtplasmac
You do need to use a pull down resistor on the ArcOK input which is discussed in the QTP manual.

oops here is the new file.

Here is a slightly different file to try. replace the one I gave before.
I think there still will be a focus problem if you click the gcode display then spacebar.
But clicking the window or graphics display should refocus so space bar works again.

If you can confirm these things, I will look further into the gcode display problem.

Focus problems are always a pain!
Thanks

Hi,

I'm converting a Crossfire Pro to LinuxCNC using a Mesa 7i95t and THCAD2.  I have the automation interface card in the cutmaster 60i so it has the torch start/stop, voltage divider, ok to move, and ohmic sensing on the CPC connector.  I'm still waiting for the THCAD2 to come in but the wiring for it seems pretty straight forward.  I've attached the wiring diagram from the service manual and I'm not quite sure if I can just wire the start/stop directly to a 7i95t output or if I need to use a relay.  If I understand the qtplasmac docs I should be able to connect the ok to move directly to an input but may need a resistor if the current draw isn't enough.  I may hook up ohmic later but would I need another THCAD2 for it as well?

Thanks,

Kevin

I've been slowly getting a homebuilt CNC router up and running and keep running into an error when opening my programs in LinuxCNC. The error states "radius to end of arc differs from radius to beginning". I've searched the interwebs and I've seen recommendations for reducing pass tolerance (greatly increases tool path generation time) and switching from a helix to plunge when lowering the bit into the work piece. These help for some programs but not all. Does anyone else have an issue like this? Thank

You lucky ....
You are welcomed, always.