basically you want the max power on the ruida controller to be set so that it just begins to lase. (is that a word?) This will allow you to use the pulse button to setup your mirrors. Pulse button is only used for that or testing if it’s working or maybe a laser power reading.
I set mine up for about 20%, as a general rule. In association with the duration of the pulse, also set in the Ruida, I can get a pretty good mark. I can pulse it multiple times if I need to.
My machine will laser below 10%, so I wouldn’t change it to something on the edge. Just a change in temperature could cause it not to lase.
Make sense?
To clarify… settings on the console itself can be set at 20 min and 99 max??
Minimum power is only used in vector engraving. You are not vector engraving pulsing the machine.
I was referring to maximum power.
I just found a bizzare problem with My RD6445G, it appears that any changes I make on the display pannel I can write then read from the pannel and all appears fine, BUT it does not seem to be actually writting to the control Board, I have to make changes Via the software (reads and writes fine) for it to write to the board (I am guessing their is an EPROM on the display panel that is storing the changes but not sending to Controller board, so it reading and writting as far as the EPROM but has a comms failure between Display EPROM and Contoller Board ???)
You lost me here…
The console is plugged into the controller. Anything going to the console display must go through the controller.
The best we know about these, is it’s an 8 bit data path to the controller… Don’t know how they use it – 8 bit, 16 bit or some other application.
I’ve never seen these fail as I’m understanding you, not that they can’t but I’ve never seen one.
Maybe a better explanation of what you are doing and why you don’t think the information is sticking.
Yep like I said it’s bizzare, the only difference I can see is that the data on the panel (on the top of the laser) is not correctly sending the data to the controller (inside the laser where all the wires are attached) and the changes done by the software are sent to the controller either via the usb port or ethernet port directly to the controller, which is why I suspect it is a comms problem between the panel and the controller, unless there is something else so obvious I am missing it ? 50+ plus years IT experience so you can get a bit technical in description of any ideas you might have. I was surprised that changes done on the panel would write and read back correctly but not be actually updated on the controller, the only way I can see that happening is if there is data storage on the panel that is not getting from panel to controller. I really can’t think of a reason why they would have memory on the panel as it is just an input/output device for the controller other than using it as a display buffer for the panel.
Which settings are you changing?
The speed / power values shown on the display when the machine is not running a job do not match any values set in the layers, which often comes as a surprise.
Screenshots / display photos will let us look over your shoulder and see what you’re seeing.
It was actually the Steps per rotation that highlighted the problem for me, my Y axis was only travelling 200mm instead of the 300mm it should have been, checked everything mechanical and couldn’t find a problem, so started checking software settings and that is when I found the steps were updating on the panel but not on the controller. a rectangle 100x300mm would cut 100x200mm even after recallibrating the Y axis, the panel settings were changing to different values but the rectangle was still only cutting 100x(2/3 of Y axis) changing the steps should have solved the problem but didn’t. It wasn’t until I was at the computer rather than the laser that I found the changes made in Lightburn or RDWorks were being updated on the controller, and on the panel on the laser it was still reading the steps that I last set using the panel but would cut the 100x300mm from the software settings.I am not near the laser for a day or so so I can’t take pics/video. Hopefully this explains it well enough that people can follow.
If this is a Ruida controller, then AFAICT they all use distance/step units: my machine is set for 12 µm/step.
GRBL controllers use step/distance units, with typical diode lasers around 100 step/mm.
Does the 6445 display the distance/step value for the axes on the machine display?
I think this can only be shown through pictures of the machine display and screenshots of the controller settings, so let’s wait until you can do that.