Fast Hole EDM from Hacked Parts

Hi all, 


I apologize for the delay. I have been busy with this and another project. 

So the new rackrobo does have a way of modulating power output.  I was able to get my hands on a power supply at no cost to me. They are having some issues but it seems like the probability of an issue occurring is still pretty small.  If I do have issues I'll look at swapping the power supply. 

Yes I imagine sinker would draw a lot more power then wire and especially hole drilling. 


As far as linuxCNC control of EDM. Does anyone know if the ones like tommy was showing are using reverse feed rate and short detection?  It seems like it wouldn't be too difficult to pause the program when a short is detected, but does anyone know if it is possible to get reverse feed to pull out of the short and then reengage? I know this is how professional machines operate and I would think someone has figured out how to do this with LinuxCNC...  Any LinuxCNC wizards out there know how to do this?


Best,
-Dylan

Hi Aciera,

Thank you for the response and sorry again for the delay.  

I am glad to hear that motion.adaptive-feed is available and useful for what I am trying to do.  I have a couple questions. First, and more basically, how do I turn on motion.adaptive-feed? I found some info on the "motion" page, but it doesn't seem to show how to manipulate it.  Is it on the .ini file? 

Second, and more specifically, how would I get the machine to move backwards, but only when it is sensing a short.  There is an output from the EDM power supply that goes either high or low (I am not sure which) when the supply senses a short. Probably what I want is when a short is detected for the machine to move back a specific amount (in either distance or time) to make sure the short is completely gone before reengaging. The other option is simply to reverse feedrate until the short is no longer detected and then proceed with forward motion.  

I have no idea where to even begin to program this though... :/

Best,
-Dylan

Aciera,

Thanks for the response. 


First and unfortunately, I told you wrong.  The Powercore is not outputting a HIGH or LOW signal but a PWM signal.  Here is a excerpt from the GitHub:

“The Powercore V2.0 provides digital telemetry on the spark ignition rate via the ALRT port. The spark ignition rate, defined as the ratio of 'observed discharges' to 'possible discharges'. The spark ignition rate is a key indicator of feedrate efficiency. A low rate suggests the feedrate can be increased, while a high rate indicates an excessive feedrate or a short circuit. Telemetry is reported as a PWM duty cycle, which can be read by a control board or microcontroller. This port enables closed-loop feedrate control, ensuring optimal material removal. An ignition rate of approximately 80% has been observed to be optimal.”

Here is the link as well: github.com/Rack-Robotics/Powercore-V2.0


So I have a few thoughts.  First is hardware compatibility.  My machine is running on a Mesa 7I96S and a 7I85S.  The 7I85S is essentially unused right now. I am looking through the technical documents and it seems like the 7I85S has ports that can be designed as PWM output ports.  I am not sure if they can be configured for input though.  Perhaps you would know?  There are also a bunch of unused IO ports on both boards, but the technical documents don’t specify if those ports can be used for analog/PWM.  The Powercore also doesn’t specify what the voltage would be at 100% duty cycle so I am wondering if it will be compatible with the Mesa in that regard.  I suppose if the Powercore is opporating at 3.3v and the Mesa is operating at 5v for example, a multiplier could be added to the input. But if the voltages are reversed there could be an issue of overwhelming the Mesa or damaging it. 

If the Mesa does not have a PWM input, it seems like the next option would be to use something like an arduino to interpret the PWM signal from the Powercore and then talk to the Mesa via serial communication.  This sounds like a can of worms…


Second, software.  'M52 P1’.  Does this need to go into the main hal file? I assumed I would find 'M52 P0' somewhere but I did not.  So maybe it is currently on the default for my machine..  My machine is called the hackbot. So it would go somewhere inside the hackbot_srt.hal file? And then would the float variable go into this file as well? Plus whatever logic/code needs to be written to account for the above info from the GitHub (changing the federate based on PWM)?  Sorry, I can talk hardware all day long but software I am slow with.. 

Third, interface.  It would be really awesome to have a widget or something on the GUI that shows the PWM spark rate.  This is obviously not necessary but it would be very classy.  I have no idea how to do this… 

Also, it would be very cool to have the machine responding to the PWM and updating the feedrate to keep things at the perfect 80% duty cycle.  But if this is too challenging, it could be kept at default federate unless duty cycle goes over some limit (maybe 95%) then federate is briefly reversed. This would also make control via an arduino (or something else) easier as the arduino can just output a high or low which will avoid serial communication…


Thank you for the help. 

Best,
-Dylan