Do you need EzCad3 Testers?

Thank you, Travis.
If I knew who you were, I wouldn’t have asked about the COM port! :wink:
Nice channel! https://www.youtube.com/@diyfiberlaser

We have received your separate support request, and our developers are looking into it.

Ha! Thanks for your help Aaron

Mine is reported as:

Windows Driver: BJJCZ Laser Mark Control Board DLC Version 1
EzCad About HW:

  • Board Type: DLC_2D
  • Version: 216e-0116 20211015
  • Function Code: FLY
  • Laser interface card type: (empty)
  • Laser interface card version: 0-0

I also tested the Z-Jog buttons:

  • First use of the Up or Down arrow on the Main GUI will trigger a rehome first
  • After that it goes up and down according the value set in a text box next to the arrows (in mm).

Since this hasn’t been corrected yet, the 2.1 version of LightBurn includes 16 bit image support, so you can get 65535 unique depths.

Here’s an example showing 512 and 1024 passes from the same 16 bit source (image by Victor Wlonsky) :

Very Very nice and thanks for the clarification. I’m more than happy to cover STL to Depth Maps and it will be good to see how to mix and match these with a live Z-Axis to keep the laser in focus.

FWIW - I not only do direct coin engraving (where stair stepping is an issue currently), but also create Dies for metal stamping and this would be ideal as it will help reduce the amount of polishing that is needed.

One idea for using Depth Maps on a live Z-Axis, would be to let the user input the desired Z-depth movement for the engrave and use that to calculate the required Z-Steps (or even inputting a start / end point for the Z-Axis) instead of asking the user how many Z-Steps per layer(s).

That way you could use a Depth Map and simple ask Lightburn to advance the Z-Axis down .5mm, 5mm or whatever.

Of course you would need a profile that ablated at the same rate on that particular material, but this is not that hard to work out IRL. You simply load up a test image of a cylinder, run it on some scrap, and then measure how accurate the hole is. Adjust speed / power (etc) till it is correct an you have your profile. I’ve already got profiles for:

  • Aluminium
  • Copper
  • Graphite (99%)
  • Mild Steel
  • Tin Alloys (Pewter)
  • Zinc Casting Alloys
  • Silver Alloy (95%)

…and have a bunch of sample pucks for another dozen or so alloys.

That said, these are EzCad profiles, and I will need to convert them over (and would be happy to share). One thing I’ve found with EzCad is setting like Hatch Pattern makes an enormous difference in speed / quality and while I’ve no experience with LightBurn, I have the time and patience to work it out…and will post the profiles.

Yup I do (being a Lightburn newbie) :slight_smile:

  • Can I run it on the same Windows PC as EzCad3 without conflict for either SW?
  • Will it use the same Window Driver as already installed (BJJCZ Laser Mark Control Board DLC Version 1)
  • What (if any) setting or config files should I import from EzCad3?
  • What version of Lightburn should I wait for before starting?
  • Any other hints / links / ???

Thanks
Nathan

Also, if it helps from my HW Z Axis setup in ExCad I see:

  • Pulses Per Round = 12800
  • Distance Per Round = 5 mm

…so it looks like I have a:

  • 5 mm pitch leadscrew
  • 1.8° stepper motor (200 steps/rev)
  • 64× microstepping driver

…and that gives me a potential 0.39um (0.00039mm) step size.

This docs page will help achieve the same result in LightBurn.

Yes, but to use LightBurn, you’ll need to swap the driver with Zadig, as explained here:

To switch to EZCAD3, simply uninstall the driver in the Windows Device Manager and power-cycle the laser to reinstall the correct driver.


Preferably, these three files mentioned in the Wizard:

You can probably wait for the upcoming RC-8. It includes a fix for some Z Axis control toggles on some controllers.
But feel free to give the current one a try, and let us know: Index of /LightBurn/RC/LightBurn-v2.1.00-RC-9/

Importing the Motors.ini should already populate the stepper settings correctly:

One thing that comes to mind is that many config files don’t hold any Delay Defaults and therefore, LightBurn defaults to 100μs

You’ve probably already seen these values in EZ3, and you can enter them manually later. Because calibrating accurate galvo timings isn’t exactly fun :slight_smile:

But it is exciting. Check out this thread for example.

@Aaron.F Thanks for the comprehensive response. I’ll have a read and get going :slight_smile:

I’ve installed RC6 and imported the 3 different machine files without issue successfully setting up LB.

I’ve issues with the driver however:

  • Laser does not appear as “connected” (with just the original OEM EzCad3 Driver installed), and
  • I can not get the LB Ezcad 2/3 driver to install (either via the LB or dedicated installer). It just fails to install (tried installing it with the original OEM driver both disabled and then removed)… So I don’t get as far as needing ZAdig to “swap” between drivers.

I believe you have to use 2.0.05 to install:

Thanks @parsec - I might wait for RC8.

I see that RC9 is out so I’ll give that a test. One thing that caught my Eye, is RC9 is almost twice the size of RC6… would that be normal?

Correct. :slight_smile:

Good news, is that with RC9 the driver installs and LB can see my Laser so I can test it!

Apologies if I have missed something obvious (being new to LB), though in my quick test I found the following.

LB seems to work for controlling functions like:

  • Draw the bounding outline of the job
  • Fire the laser to engrave the job

…however, the manual Z-Axis adjustment buttons do not seem to work at all:

  • Home the laser (using the Home button)
  • Focus the laser by moving the Z-Axis up or down (using the Up / Down buttons)

Also, from a “feature” POV, I did not notice any way of specifying what “0” is (eg -500mm from Home to the top of the table), or what height of the work piece on the table is (eg +10mm over the table) so that the Z-Axis will be automatically brought into focus.

Did you import the Motors.ini config file when you added the device?

That’s correct. Until recently, Z-axis control was not possible at all with galvo scanners.

From the 2.1 Release notes:

Did you select the correct axis in the Device Settings here, and can you confirm that homing and jogging are working with these buttons?