Plasma THC switch output
- Thread starter jcoldon
- Start date
zombieengineer
ZombieEngineer
@jcoldon
Disclaimer: I don't have a plasma system.
The THC on command appears to be generated by the appropriate CAM post-processor. Looking at the SheetCAM variant the THC ON/OFF codes are only inserted if the move was greater than some minimum radius/length (configured at the top of the post-processor for 10mm).
It would be a fairly simple matter to modify the post processor. Change "M667" to "M667 M64 P1" to enable THC and turn on auxiliary output #1, similarly change "M666 M65 P1" to disable THC and turn off auxiliary output #1).
The question that comes to mind is "Why?" - If this is the Proma SD THC controller then Masso will loose track of the Z axis position while the Proma SD controller moves the torch up and down. Bad things are likely to happen.
Disclaimer: I don't have a plasma system.
The THC on command appears to be generated by the appropriate CAM post-processor. Looking at the SheetCAM variant the THC ON/OFF codes are only inserted if the move was greater than some minimum radius/length (configured at the top of the post-processor for 10mm).
It would be a fairly simple matter to modify the post processor. Change "M667" to "M667 M64 P1" to enable THC and turn on auxiliary output #1, similarly change "M666 M65 P1" to disable THC and turn off auxiliary output #1).
The question that comes to mind is "Why?" - If this is the Proma SD THC controller then Masso will loose track of the Z axis position while the Proma SD controller moves the torch up and down. Bad things are likely to happen.
looking to hookup a nuron simplicity THC to the masso..
.masso internal plasma THC control lacks good THC control ability the nuron will make a masso a top plasma control
im also wondering if masso has an input for command to move i know thers arc ok .
not sure that going to work based on how long it wate for the arc ok unless i can set the time
dont want it to time out before the initual hieght sence and cut height goes active
.masso internal plasma THC control lacks good THC control ability the nuron will make a masso a top plasma control
im also wondering if masso has an input for command to move i know thers arc ok .
not sure that going to work based on how long it wate for the arc ok unless i can set the time
dont want it to time out before the initual hieght sence and cut height goes active
zombieengineer
ZombieEngineer
@jcoldon
It appears that the "Arc OK" input does pause the motion, from the documentation:
The M03/M05 commands turn plasma on/off, this would map to the "Cycle Start" input of the Neuron Simplicity THC module. It appears that the Neuron Simplicity controls all Z axis operations (I didn't see the home switch for the Proma SD controller). Be aware that there is a 15 second timer from issuing the M03 command and "Arc OK" being received (details are near the bottom of the linked documentation page, search for "NO ARC OK").
If you replace the M666 / M667 commands with the appropriate M64 P# / M65 P# you can use the auxiliary output to disable the THC functionality.
Providing you can modify the post-processor for your CAM package I believe you can make this work.
What CAM package are you intending to use?
It appears that the "Arc OK" input does pause the motion, from the documentation:
- Arc ok This signals MASSO when the Plasma arc is struck to let it know that it is ready to continue with the cut.
The M03/M05 commands turn plasma on/off, this would map to the "Cycle Start" input of the Neuron Simplicity THC module. It appears that the Neuron Simplicity controls all Z axis operations (I didn't see the home switch for the Proma SD controller). Be aware that there is a 15 second timer from issuing the M03 command and "Arc OK" being received (details are near the bottom of the linked documentation page, search for "NO ARC OK").
If you replace the M666 / M667 commands with the appropriate M64 P# / M65 P# you can use the auxiliary output to disable the THC functionality.
Providing you can modify the post-processor for your CAM package I believe you can make this work.
What CAM package are you intending to use?
Hello!
Looks like the Neuron Simplicity can work with MASSO G3.
One thing - G3 serie has only TTL Outputs which can be configured for the Plasma On/Off (Start cutting) and M64/M65 P# (THC, AVC (Automatic Voltage Control) OFF/ON) macros.
In the user manual there is information about max 5 mA output current for the TTL output (74HC14 driver). Neuron Simplicity has a optocoupled 10 mA 5V inputs for this signals.
Now I think - better to add solid state relay between Masso G3 TTL outputs and Neuron Inputs (regular relays are slow for the THCOFF) .
OR... It possible to use CW and CWW otputs for spindle (open collector) for same purposes? Possible to route Plasma On/Off and M64/M65 to this outputs?
In the G2 serie we have a open collector 400 mA Relay1-7 oututs for this purposes.
I would be very grateful to the developers if they would help in this matter.
Looks like the Neuron Simplicity can work with MASSO G3.
One thing - G3 serie has only TTL Outputs which can be configured for the Plasma On/Off (Start cutting) and M64/M65 P# (THC, AVC (Automatic Voltage Control) OFF/ON) macros.
In the user manual there is information about max 5 mA output current for the TTL output (74HC14 driver). Neuron Simplicity has a optocoupled 10 mA 5V inputs for this signals.
Now I think - better to add solid state relay between Masso G3 TTL outputs and Neuron Inputs (regular relays are slow for the THCOFF) .
OR... It possible to use CW and CWW otputs for spindle (open collector) for same purposes? Possible to route Plasma On/Off and M64/M65 to this outputs?
In the G2 serie we have a open collector 400 mA Relay1-7 oututs for this purposes.
I would be very grateful to the developers if they would help in this matter.
Attachments
zombieengineer
ZombieEngineer
@andrewn
To paraphrase Shakespeare: "A PCB, my kingdom for a PCB". (PCB = Printed Circuit Board).
The parts required to increase the current output is about 50 cents, a transistor and couple of resistors - wiring it together is the hard part. Apologies if the following becomes an "Electronics 101" as I try to explain one of the basic building blocks of electronics.
The common NPN transistor (BC546 / BC547 / BC548 / BC549 / BC550) acts as a current amplifier. The base current (Ib) controls the collector current (Ic) following the equation Ic ? Hfe x Ib where Hfe is the current gain of the transistor (for the BC54x series the gain is between 110 to 800, the maximum current for these devices is 100 mA).
You have mentioned that the opto-coupler input is expecting 10 mA, for the purposes of this exercise I am going to use 25 mA to ensure that the transistor isn't the bottleneck. Using the lowest gain (110) the required base current is 25 mA / 110 = 0.227 mA.
We need a resistor between the Masso output and the base of the transistor. There is always a 0.6V voltage drop between the base and emitter for all silicon transistors, we should assume that the Masso output is 4.5V due to switching losses. Therefore the resistor must drop 3.9V for a current of 0.227 mA : R = V / I = 3.9V / 0.000227A = 17,180 ? (the nearest common resistor value is 18k ?).
Finally we need a voltage drop resistor for the opto-coupler. Assuming a 24V supply minus 5V for the opto-coupler and minus 1V for the transistor leaves 18V. R = V / I = 18V / 0.010 A = 1,800 ? (the nearest common resistor value is 1.8k ?).
The final circuit:
To paraphrase Shakespeare: "A PCB, my kingdom for a PCB". (PCB = Printed Circuit Board).
The parts required to increase the current output is about 50 cents, a transistor and couple of resistors - wiring it together is the hard part. Apologies if the following becomes an "Electronics 101" as I try to explain one of the basic building blocks of electronics.
The common NPN transistor (BC546 / BC547 / BC548 / BC549 / BC550) acts as a current amplifier. The base current (Ib) controls the collector current (Ic) following the equation Ic ? Hfe x Ib where Hfe is the current gain of the transistor (for the BC54x series the gain is between 110 to 800, the maximum current for these devices is 100 mA).
You have mentioned that the opto-coupler input is expecting 10 mA, for the purposes of this exercise I am going to use 25 mA to ensure that the transistor isn't the bottleneck. Using the lowest gain (110) the required base current is 25 mA / 110 = 0.227 mA.
We need a resistor between the Masso output and the base of the transistor. There is always a 0.6V voltage drop between the base and emitter for all silicon transistors, we should assume that the Masso output is 4.5V due to switching losses. Therefore the resistor must drop 3.9V for a current of 0.227 mA : R = V / I = 3.9V / 0.000227A = 17,180 ? (the nearest common resistor value is 18k ?).
Finally we need a voltage drop resistor for the opto-coupler. Assuming a 24V supply minus 5V for the opto-coupler and minus 1V for the transistor leaves 18V. R = V / I = 18V / 0.010 A = 1,800 ? (the nearest common resistor value is 1.8k ?).
The final circuit:
- Power supply positive => 1.8k ? resistor => Opto-coupler => Transistor Collector
- Masso output => 18k ? resistor => Transistor Base
- Transistor Emitter => Power supply negative
Attachments
Hello!
Thanks for the detailed explanation. Apparently I expressed my question a little incorrectly and it is more global
Now our controller has this schematic for the inputs signals and this is works with any BOB on the market, based on the 74HC14 chip and on the 74HC245.
I want to clarify whether the MASSO G3 controller has a current-limiting resistors (5 mA) at the TTL outputs. If yes, we need to change schematic and PCB for using our THC with Masso G3.
If not - One 74HC14 buffer will be enough to work with the current version of the circuit.
And another question - can a one signal (for example Plasma on/off) can be be assigned to two TTL outputs at once?
Thanks for the detailed explanation. Apparently I expressed my question a little incorrectly and it is more global
Now our controller has this schematic for the inputs signals and this is works with any BOB on the market, based on the 74HC14 chip and on the 74HC245.
I want to clarify whether the MASSO G3 controller has a current-limiting resistors (5 mA) at the TTL outputs. If yes, we need to change schematic and PCB for using our THC with Masso G3.
If not - One 74HC14 buffer will be enough to work with the current version of the circuit.
And another question - can a one signal (for example Plasma on/off) can be be assigned to two TTL outputs at once?
Attachments
zombieengineer
ZombieEngineer
@andrewn
This is going to be a long e-mail, I will try and break it into parts for clarity.
Just a bit info of my background to put things into context. My day job is building training simulators for chemical plant operators, chemical engineer by training but need to be familiar with multiple disciplines including control systems. Electronics is something of a hobby.
I want to clarify whether the MASSO G3 controller has a current-limiting resistors (5 mA) at the TTL outputs. If yes, we need to change schematic and PCB for using our THC with Masso G3.
I do not work for Masso.
According to my digital microscope camera the output chip is a CD40106B CMOS Hex Schmitt-Trigger Inverter. The output voltage should be just about rail-to-rail but have an output source of 3 mA according to the Texas Instrument data sheet. This would suggest the 5mA recommended limit is pushing the design envelope a bit...
I am uncomfortable with your circuit diagram - a full wave bridge rectifier on an opto-coupler is going to eat into the available voltage for the resistor to regulate the LED current. The E:357N-G (from the data sheet) has a forward voltage between 1.2V to 1.4V. The BAS40 has a variable forward voltage drop depending on current, I am going to use 0.5V as a working value. The total forward voltage drop excluding the resistor is going to be roughly 2.3V (1.3V+0.5V+0.5V). This leaves 2.7V voltage margin for the resistor to work with, however every 0.1V change in voltage input will result in 4% change in LED current.
If we use TTL logic levels as our input reference then the opto-coupler should trigger at 2.7V thus only having 0.4V margin for the resistor.
It is easy to criticize, but harder to provide an alternative. *scratches head*
I think I have a suggestion for the input side but you need to review the suggestion to see if it would work for your problem. Instead of a full wave bridge rectifier use two opto-couplers which are connected in parallel except for the input LEDs, connect the LEDs such that one will aways conduct. Instead of a resistor use a JFET current source (you will need one for each opto-coupler, a JFET current source is a N-Channel JFET and a resistor). Potentially over engineered solution which should happily switch on if the voltage difference is between 2V and 24V across the inputs.
I will try and draw this up in Eagle CAD and post a circuit schematic later.
And another question - can a one signal (for example Plasma on/off) can be be assigned to two TTL outputs at once?
From memory you can't however if you could modify the post processor to turn on/off multiple auxiliary outputs.
This is going to be a long e-mail, I will try and break it into parts for clarity.
Just a bit info of my background to put things into context. My day job is building training simulators for chemical plant operators, chemical engineer by training but need to be familiar with multiple disciplines including control systems. Electronics is something of a hobby.
I want to clarify whether the MASSO G3 controller has a current-limiting resistors (5 mA) at the TTL outputs. If yes, we need to change schematic and PCB for using our THC with Masso G3.
I do not work for Masso.
According to my digital microscope camera the output chip is a CD40106B CMOS Hex Schmitt-Trigger Inverter. The output voltage should be just about rail-to-rail but have an output source of 3 mA according to the Texas Instrument data sheet. This would suggest the 5mA recommended limit is pushing the design envelope a bit...
I am uncomfortable with your circuit diagram - a full wave bridge rectifier on an opto-coupler is going to eat into the available voltage for the resistor to regulate the LED current. The E:357N-G (from the data sheet) has a forward voltage between 1.2V to 1.4V. The BAS40 has a variable forward voltage drop depending on current, I am going to use 0.5V as a working value. The total forward voltage drop excluding the resistor is going to be roughly 2.3V (1.3V+0.5V+0.5V). This leaves 2.7V voltage margin for the resistor to work with, however every 0.1V change in voltage input will result in 4% change in LED current.
If we use TTL logic levels as our input reference then the opto-coupler should trigger at 2.7V thus only having 0.4V margin for the resistor.
It is easy to criticize, but harder to provide an alternative. *scratches head*
I think I have a suggestion for the input side but you need to review the suggestion to see if it would work for your problem. Instead of a full wave bridge rectifier use two opto-couplers which are connected in parallel except for the input LEDs, connect the LEDs such that one will aways conduct. Instead of a resistor use a JFET current source (you will need one for each opto-coupler, a JFET current source is a N-Channel JFET and a resistor). Potentially over engineered solution which should happily switch on if the voltage difference is between 2V and 24V across the inputs.
I will try and draw this up in Eagle CAD and post a circuit schematic later.
And another question - can a one signal (for example Plasma on/off) can be be assigned to two TTL outputs at once?
From memory you can't however if you could modify the post processor to turn on/off multiple auxiliary outputs.
zombieengineer
ZombieEngineer
@andrewn
Using a JFET current source with back-to-back opto-couplers was a little too complicated for me to wrap my head around the implications.
I looked at the design challenges for a bipolar opto-coupler that was TTL compatible (historically 1 TTL input load was 1.7mA).
The circuit is highly dependent on the JFET which has a Gate-Source cut-off voltage of -0.6V, your choices of devices with similar cut-off voltages are extremely limited. The particular JFET specified (2SK923-23-TB-E) has a maximum working voltage of 15V. The turn-on voltage should be 2.6V (almost on the lower limit for TTL voltages) - the split of voltage drops are 0.8V for the diode bridge, 1.3V for the opto-coupler LED and 0.5V for the JFET current source. The circuit should be able to handle input voltages up to 17V without issue and only draw 1.8mA. The 4.2k pull-up resistor has been calculated based on a worst case CTR of 50% and still result in a valid low logic signal for a CMOS input. According to the datasheets the maximum switching frequency would be limited to about 30 kHz.
Using a JFET current source with back-to-back opto-couplers was a little too complicated for me to wrap my head around the implications.
I looked at the design challenges for a bipolar opto-coupler that was TTL compatible (historically 1 TTL input load was 1.7mA).
The circuit is highly dependent on the JFET which has a Gate-Source cut-off voltage of -0.6V, your choices of devices with similar cut-off voltages are extremely limited. The particular JFET specified (2SK923-23-TB-E) has a maximum working voltage of 15V. The turn-on voltage should be 2.6V (almost on the lower limit for TTL voltages) - the split of voltage drops are 0.8V for the diode bridge, 1.3V for the opto-coupler LED and 0.5V for the JFET current source. The circuit should be able to handle input voltages up to 17V without issue and only draw 1.8mA. The 4.2k pull-up resistor has been calculated based on a worst case CTR of 50% and still result in a valid low logic signal for a CMOS input. According to the datasheets the maximum switching frequency would be limited to about 30 kHz.
Attachments
@zombieengineer
Now everything is clear to me.
You describe the circuitry in great detail and it's just wonderful and very professional!
Thank you!
CD40106B explains everything. I think I need to change the input circuit by adding a NPN transistor (Just like you described earlier) because the output current of the CD40106B is quite small and cannot be used directly. It's not a problem.
Just the circuit was originally designed so that a 5 volt signal could be connected without regard to polarity (to make the connection easier). Therefore there is a bridge.
@breezy
Thank you! Can you tell me:
Sorry for the lot of questions))
Now everything is clear to me.
You describe the circuitry in great detail and it's just wonderful and very professional!
Thank you!
CD40106B explains everything. I think I need to change the input circuit by adding a NPN transistor (Just like you described earlier) because the output current of the CD40106B is quite small and cannot be used directly. It's not a problem.
Just the circuit was originally designed so that a 5 volt signal could be connected without regard to polarity (to make the connection easier). Therefore there is a bridge.
@breezy
Thank you! Can you tell me:
- it is possible to using spindle open collector outputs CW and CCW for the Plasma On/Off and M64/M65 macro?
- it is possible to add a button on the screen for enable/disable THC mode (wait for the ArcOK from plasma cutter)without F1-Setup.. - just button
- it is possible to add a macro for the same THC on/off from gcode? For example if we using plasma and scriber in same cutting program...
- How the Masso controller behaves if an plasma arc is lost during a cut (ArkOk signal is lost from the cutter)? Does it stopping XY motion with deceleration and return to the point where the arcok was lost so that you can easily continue the cut from that point? And in general, is it possible to continue the execution of the program from this point, not from the beginning of the gcode line, where the point is located?
Sorry for the lot of questions
))It would be help full if We could get masso support to answer Andrew .
He the builder of the neuron plasma Torch height control .any one in plasma knows there no better THC then neuron .
I was looking at connecting a neuron THC to a masso so i can build a few masso plasma controllers with one of the best THC control out there.
So far it looks like it going to work . just need to get the TTL masso outputs with the correct draw information Andrew asking
can masso support answer Andrew
as far as a post processor i can edit it to turn on masso outputs to operate the thc on and off from g codes
might need the arc ok input time longer not sure on that
I been doing plasma a long time this would be a good setup neuron on a masso
He the builder of the neuron plasma Torch height control .any one in plasma knows there no better THC then neuron .
I was looking at connecting a neuron THC to a masso so i can build a few masso plasma controllers with one of the best THC control out there.
So far it looks like it going to work . just need to get the TTL masso outputs with the correct draw information Andrew asking
can masso support answer Andrew
as far as a post processor i can edit it to turn on masso outputs to operate the thc on and off from g codes
might need the arc ok input time longer not sure on that
I been doing plasma a long time this would be a good setup neuron on a masso
zombieengineer
ZombieEngineer
@jcoldon
The questions that Andrew asked are valid questions that should be directed to @masso-support. Either mentioning them in the forum post or alternatively e-mailing Masso support directly.
I can appreciate the need for something better than On/Off style THC control (in the chemical process control world we refer to it as bang-bang control due to how brutal it is on control elements).
I have had a look at my Masso system (milling machine) and the CW/CCW are not assignable.
The questions that Andrew asked are valid questions that should be directed to @masso-support. Either mentioning them in the forum post or alternatively e-mailing Masso support directly.
I can appreciate the need for something better than On/Off style THC control (in the chemical process control world we refer to it as bang-bang control due to how brutal it is on control elements).
I have had a look at my Masso system (milling machine) and the CW/CCW are not assignable.
Andrew going to change his end to use the masso ttl outputs getting masso to do anything plasma never happens .
the neuron just requires an output to turn the unit on that be M3 spindle then the THC on and off will use the m 63 64 there instant .
input go to arc ok for ok to move hoping 15 sec should be enouth time , if not hope masso can extend it that update should be easy
neuron controlls the z axis driver not masso . all the needed thc settings are in it even ohmic and torch slide . it reacts realy fast
I could even use the mill screen if it had some ok to move input i have to look in to that .
as far as a scribe goes i have to build an external arc ok input so i can get masso to move . to scribe and plasma in the same post
sheet cam can do the all the codes needed u do it know with uccnc .
this is my second masso plasma build the g2 failed .hoping to make the g3 work this time with neuron thc .
since 3 years masso never did anything to plasma plus the g2 was slow . so will see if not it go on a mill retro im doing or a router
the neuron just requires an output to turn the unit on that be M3 spindle then the THC on and off will use the m 63 64 there instant .
input go to arc ok for ok to move hoping 15 sec should be enouth time , if not hope masso can extend it that update should be easy
neuron controlls the z axis driver not masso . all the needed thc settings are in it even ohmic and torch slide . it reacts realy fast
I could even use the mill screen if it had some ok to move input i have to look in to that .
as far as a scribe goes i have to build an external arc ok input so i can get masso to move . to scribe and plasma in the same post
sheet cam can do the all the codes needed u do it know with uccnc .
this is my second masso plasma build the g2 failed .hoping to make the g3 work this time with neuron thc .
since 3 years masso never did anything to plasma plus the g2 was slow . so will see if not it go on a mill retro im doing or a router
zombieengineer
ZombieEngineer
@jcoldon
I appreciate the challenges trying to get improvements in the Masso controller. The best way based my experience is to provide Masso with a "compelling reason" to make the improvements - for example selling an extra 20 to 50 controllers per year.
I can see two ways to build a "compelling reason":
Value Driven Feature Prioritization:
If you can prove the value of a feature - it tends to sell itself.
Community Driven
From my outsider perspective the CNC plasma cutter environment / "ecosystem" is similar to the small CNC milling environment about 10-12 years ago. Something of a wild west of components (of various quality) being thrown together and for some people it works, for others it doesn't. The Masso CNC controller is only one part of a CNC plasma cutter solution, what are the other components to make a working system? Unfortunately there is a lot of interactions between the various components of a CNC system - if there is an issue is it due to a single component or interactions between components.
What is required is community to share their experiences of what works and what doesn't and for someone in that community to curate a list of recommended components with reasons why they should be used. If you could enlist someone who has reasonable experience with CNC plasma cutters and can create YouTube videos then you would be all set (think of someone like CNCNutz for plasma cutters). Once you have someone who can represent the community then it is easier for Masso to understand what is required (they only need to talk to one person rather than 20).
Perhaps you need to find a way to get Peter to come over to the dark side of gurgling water tables, hissing air, blinding flames and heavy metal (steel plate).
Footnote : My experience has been influencing software development budget which paid the salaries for 10 to 15 people.
I appreciate the challenges trying to get improvements in the Masso controller. The best way based my experience is to provide Masso with a "compelling reason" to make the improvements - for example selling an extra 20 to 50 controllers per year.
I can see two ways to build a "compelling reason":
- Value driven prioritization of required features (I know that is horrible "business speak")
- Develop a community around building / retrofitting CNC plasma cutters
Value Driven Feature Prioritization:
- What do you see as the top 5 areas that require improvement with the Masso controller for use in a CNC plasma cutter?
- What is the cost ($/year preferably) for an operator of a CNC plasma cutter if they don't have that feature? (ruined jobs, scrap, etc)
If you can prove the value of a feature - it tends to sell itself.
Community Driven
From my outsider perspective the CNC plasma cutter environment / "ecosystem" is similar to the small CNC milling environment about 10-12 years ago. Something of a wild west of components (of various quality) being thrown together and for some people it works, for others it doesn't. The Masso CNC controller is only one part of a CNC plasma cutter solution, what are the other components to make a working system? Unfortunately there is a lot of interactions between the various components of a CNC system - if there is an issue is it due to a single component or interactions between components.
What is required is community to share their experiences of what works and what doesn't and for someone in that community to curate a list of recommended components with reasons why they should be used. If you could enlist someone who has reasonable experience with CNC plasma cutters and can create YouTube videos then you would be all set (think of someone like CNCNutz for plasma cutters). Once you have someone who can represent the community then it is easier for Masso to understand what is required (they only need to talk to one person rather than 20).
Perhaps you need to find a way to get Peter to come over to the dark side of gurgling water tables, hissing air, blinding flames and heavy metal (steel plate).
Footnote : My experience has been influencing software development budget which paid the salaries for 10 to 15 people.
What your asking is for me to do all the leg work for masso to build a better controller . i know what it takes to have a better plasma controller. i been doing plasma longer then masso building controllers . Thats why im trying to just get some information and try to use a neuron THC controller on the masso no one does THC better then Neuron . Andrew knows plasma well . It masso that should be working with neuron. I simply looking to put a good non pc based controller package together to sell . I chose to give masso another try this time with a neuron . so far it looks like it will work.. time to try it .
I run a FB page cnc plasma table builders. lots of people out there building plasma tables in the us . i have a good running UCCNC controller setup . neuron even has a adaptor board for uccnc runs realy well . so now i am going to try to make a masso run plasma the right way. with a top of the line THC unit . hoping it work
i make some working video because of it guys will buy a masso .just like they did with uccnc when i started using it 3 years ago for plasma .. plasma is the hardest cnc to run because of the THC . up down inputs just dont cut it with out lots of on screen features and control not in g code like masso does . neuron removes that from masso takes over z axis control . so i be getting all the parts together hopfully make it work . neuron and masso sell more units . lots of guy buying masso now and using it with out the thc . the no pc is a nice setup .
I run a FB page cnc plasma table builders. lots of people out there building plasma tables in the us . i have a good running UCCNC controller setup . neuron even has a adaptor board for uccnc runs realy well . so now i am going to try to make a masso run plasma the right way. with a top of the line THC unit . hoping it work
i make some working video because of it guys will buy a masso .just like they did with uccnc when i started using it 3 years ago for plasma .. plasma is the hardest cnc to run because of the THC . up down inputs just dont cut it with out lots of on screen features and control not in g code like masso does . neuron removes that from masso takes over z axis control . so i be getting all the parts together hopfully make it work . neuron and masso sell more units . lots of guy buying masso now and using it with out the thc . the no pc is a nice setup .
Quote from AndrewN on January 27, 2021, 1:25 am
Can you tell me:
- it is possible to using spindle open collector outputs CW and CCW for the Plasma On/Off and M64/M65 macro?
- it is possible to add a button on the screen for enable/disable THC mode (wait for the ArcOK from plasma cutter)without F1-Setup.. - just button
- it is possible to add a macro for the same THC on/off from gcode? For example if we using plasma and scriber in same cutting program...
- How the Masso controller behaves if an plasma arc is lost during a cut (ArkOk signal is lost from the cutter)? Does it stopping XY motion with deceleration and return to the point where the arcok was lost so that you can easily continue the cut from that point? And in general, is it possible to continue the execution of the program from this point, not from the beginning of the gcode line, where the point is located?
Sorry for the lot of questions
- is it possible to using spindle open collector outputs CW and CCW for the Plasma On/Off and M64/M65 macro?
The Spindle outputs cannot be reassigned or addressed by M64 / M64. You cannot address the spindle outputs in Plasma software using M3.
- is it possible to add a button on the screen for enable/disable THC mode (wait for the ArcOK from plasma cutter)without F1-Setup.. - just button
The buttons on the screen are not user programmable. The only way to switch the type of THC you have, ie with Arc ok or Without Arc ok is to use the F1 screen.
One possible thought is send a dummy Arc ok signal when you want to disable the Arc ok. You could potentially use the Flood Coolant button on the F2 screen to operate a relay to send a dummy Arc ok signal to the Arc Ok input. Isolate each input going to the Ark ok Input using a diode to ensure they do not back feed.
- is it possible to add a macro for the same THC on/off from gcode? For example if we using plasma and scriber in same cutting program...
If you use the Coolant button you can turn it on and off using M8 to turn it on and M9 to turn it off.
- How the Masso controller behaves if an plasma arc is lost during a cut (ArkOk signal is lost from the cutter)? Does it stopping XY motion with deceleration and return to the point where the arcok was lost so that you can easily continue the cut from that point? And in general, is it possible to continue the execution of the program from this point, not from the beginning of the gcode line, where the point is located?
When MASSO looses the Arc Ok signal it does not stop the machine. You need to manually stop it. I am not sure of the restart process in this situation.
If the arc does not strike with the initial M3 command you can press cycle start to start again. The video below shows the restart process when the plasma fails to strike an arc. It will start playing where the Arc fails.
I hope I have understood your questions correctly and this helps
Cheers Peter
You can assign Plasma on / off and the Auxiliary outputs to any of the 18 outputs.
Spindle outputs are not used in Plasma Software.
I know you know more about Plasma that I ever will but the first page shows the MASSO interface and Gcode commands it uses.
How THC works
Cheers Peter