Finally, engraving at a speed of 50 mm/sec. The problem remains. Maybe you should still consider the version that problems are detected during the preview and the algorithm does not process the drawing quite correctly. And in those places where there is gray, the power is set to that. Or you can say that I am wrong and leave everything as is. The program is yours, it is up to you to decide.
Following this now, I think I’m dealing with the same probs, will try to v2.0.00-RC2
Something to be aware of. The max constant-energy pulse rate is now RADICALLY different with the newer sources.
The M7 60W is common, I have a manual for the YDFLP-60-M7-L1-R which says there’s a 4MHz max pulse rate, but there’s a “cutoff frequency” for each Q-pulse type. For a 6ns Q-pulse, it’s 650KHz. The way I read the manual, BELOW the cutoff, it’s constant energy per pulse. As such, with 100% power, average energy output is proportional to freq. Above that, it will throttle back the power of each pulse to cap the average energy. So while it’s spec’ed to pulse as high as 4000KHz, the power is scaled back by freq above 650K. As best I can guess, that power limiting is doing the same thing as the “% power” field. e.g. asking for a 6ns 4000KHz pulse rate will deliver 6ns pulses with the pulse energy profile you’d get by entering 16% in the Power field when the pulse rate is below 650K.
What confuses me (a little) is, what happens if you are at 6ns 4MHz and only ask for 50% power? My best guess from reading the text is that entering power will have NO EFFECT, because the system already capped the power at 16% for that freq. If so, grayscale would fail above the cut-off. Or, well, it could be implemented so entering 50% power would scale within the available 0%-16% available power scale, but I doubt it.
Anyhow, I have a YDFLP-E-300-M7-M-R and the cut-off is WAY higher. 6ns is the full 4MHz, so it never throttles. At 80ns, the cutoff is still 1050KHz whereas the 60W has a 100KHz cutoff. So the usable rep rates below the cut-off are MUCH higher, by roughly 10x.
I’m trying to understand what LB does “under the hood” here with the BJJCZ, does this affect the bandwidth needed, or does LB just update one power target every time it starts a new pixel and doesn’t care how many pulses get fired within a pixel?
Basically that, exactly. We do not have any direct control over the laser source - we send commands to the board, and the board controls the source. For grayscale mode in older versions we were sending a “set power” command only when required because the current pixel was a different power level than the last one.
In 2.0 we send the “set power” command in grayscale mode for every pixel generated.