Happy programmer's day! Does your DAC have an SDK? DAC interface library released.

[cfavreau]

And... I finally was able to find a picture of it. A nice one with hi-res.

It uses a FT245RL which is a USB to parallel converter. You can still get drivers for that for modern windows.

Follow this link to the manufacturer's page FT245RL (NRND) - FTDI (ftdichip.com) and then follow the driver links. You will want the D2XX drivers and not the VCP drivers.

Here's a link to the picture:

IMG_2901.JPG (1600×1200) (joeyhagedorn.com)

Here is the picture:



The USB chip is the one closest to the USB connector.

[Zoof]

And... I finally was able to find a picture of it. A nice one with hi-res.

It uses a FT245RL which is a USB to parallel converter. You can still get drivers for that for modern windows.

Follow this link to the manufacturer's page FT245RL (NRND) - FTDI (ftdichip.com) and then follow the driver links. You will want the D2XX drivers and not the VCP drivers.

Here's a link to the picture:

IMG_2901.JPG (1600×1200) (joeyhagedorn.com)

Here is the picture:



The USB chip is the one closest to the USB connector.

Thanks, that did the trick!!!!

[drlava]

Thanks CFavreau, that is correct. For me, the EasyLase (version 1) shows up as USB\VID_0403&PID_DBD0
The standard FTDI drivers don't automatically work with it, and updating their .inf makes windows drivers signing check unhapy.

In my case in the device manager I right-clicked the device and chose 'update driver'
then 'browse my computer for drivers'
then 'let me pick from a list...'
then chose 'FTDI' manufacturer under USB devices, and by some amazing luck the 'FT4222 Interface A' from 2016 works. This driver has backward compatibility for the FT245RL, at least on Windows 10.

For me, this works under the 'netlase' DAC type in this library, using the newer 'jmlaser.dll' driver which supports the various JM Laser-built DACs.

[dinther]

This SDK has now been updated to version 2.1, supporting more DACs

Thank you for writing that library. I have two 2.5W LaserCubes I am trying it on.
Couple of questions and suggestions if you don't mind.

1 - Have you considered to put your project on Github so others can contribute to it? So far I failed to find it.
2 - The constant N_FRAMES is defined in the demo as 400 but on line 66 and 183 the number 400 is hard coded.
3 - I would love to see more comments in your demo code.

It all works but the scan speed gradually gets worse over the time the demo runs. The perfomance data written to log.txt when running LDL.bat is similar to your included log_LaserCube.txt

Information: 
           Wrote 400 Frames to DAC 
           Checked DAC's buffer status 2360 times 
           DAC's API averaged 2.006 ms per send request 
           and averaged 1.932 ms per status check 
           totalling 13.406 ms used by the DAC API per frame 
Histogram of wait time used by status function calls:
0 ms: 0
1 ms: 154
2 ms: 2132
3 ms: 74
Histogram of wait time used by frame write function calls:
0 ms: 0
1 ms: 24
2 ms: 347
3 ms: 25
4 ms: 1
5 ms: 0
6 ms: 0
7 ms: 1
8 ms: 2

By the way the LaserCube performance is not great when compared to the other log files in your SDK zip.

Regards

Paul

[dinther]

I just realise why you have wo main routines in the demo. The simple version without histogram logging runs just fine and is simple to understand.