I have a Ruida controller (RdC6445GT5) and I’m trying to setup my automatic air assist to turn on a second before the laser tube turns on for a cut. So it’s blowing before the laser fires.
I connected to RDworks 8. And I updated the “blow on Delay” to 900 ms. But it still just turns on the air assist right when the laser fires.
I also tried changing “status on delay” to 900 as well but that didnt do anything.
I have my selinoid connected to Wind and 24v and it works fine, just can’t get the delay to work.
I also have read and wrote to the controller many times, and it’s saving the settings correctly.
This being a Lightburn site, bringing up RDWorks isn’t advantageous to your quest. However, I understand some of the settings are not available within Lightburn.
I also don’t know the Chinglish version of what blow on delay actually means, I would expect it to delay the blow, so to speak, not add a delay for it’s lasing.
There is a start delay within Lightburn, although it’s stated in the docs, it seems to be undocumented as far as where it is or exactly what it does…
I’ve looked at the in the device settings using grbl and the Ruida and I don’t see it… Never having to use it I haven’t spent much time looking for it…
The Auxi air mode pulldown has three or four options, with only Blow when cutting doing what you’d (well, I’d) expect. With that selected, then the Open auxi. air value delays the start of the cut while the air pump gets up to speed, which is what we both want.
However, those selections require the LightBurn Vendor Settings value for Enable air assist output to be turned on before anything happens.
That console display page doesn’t match the description in the KT332N manual, so I’m not going out on a limb based on what I see in the 6445 manual, but getting the output delay to match what you expect may require trial-and-error spelunking through all the options in all the places.
Thank for taking your time to reply, really appreciate it. It seems there is a lack of documentation when it comes to these controllers and different software. I’ll be sure to post any discoveries I make along the way!
I’m thinking you are correct, I’ll have to try different things. I’ve read that some people were using the status connection on the controller instead of wind. So I may try that and see if anything changes.
I’ll post an update once I have some time to dig around in the settings and test them out!
Status goes active when the machine is in run mode or when executing a layer.
Wind should become active when a layer that has air assist enabled is executing.
If Wind isn’t working, it’s got to be a controller setting to enable it, or it’s got a bad port… Doubt it’s a bad port, so I’d follow up on using RDWorks to check some of the settings.
I have an OMTech and mine works fine and was configured correctly for the port to operate.
