LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Creating a VI to control a laser driver(High power laser diode driver – 36 V/21 A with TEC & Air Cooling from Aerodiode)

I have been trying to create an vi to control my laser driver from aerodiode. I have a software for that but I want to control it with labview, simultaneously the daq should also be connected to the vi and both laser and daq should start at the same time. I have attached various VI's sent by the company but i need to make a proper vi so i can give current and voltage to the laser driver and turn it on and off at the same time with daq. And i have also attached SS of what i have done so far which is not working btw the laser is not even turning on and also documents sent by the company. 

So if someone can create a vi or if someone can help me create a vi it'll be a lot of help.

So in short need VI's for driver and daq where both driver and laser turn on simultaneously and also ill be able to set current and voltage for laser driver.

 

need to connect these both vi but both are not workingneed to connect these both vi but both are not workingSoftware provided by aerodiodeSoftware provided by aerodiodevi for daq workingvi for daq workingvi for laser driver not workingvi for laser driver not working.

 

0 Kudos
Message 1 of 3
(153 Views)

Hi Push,

 


@Pushpank1601 wrote:

i need to make a proper vi so i can give current and voltage to the laser driver and turn it on and off at the same time with daq.

… is not working btw the laser is not even turning on and also documents sent by the company. vi for laser driver not workingvi for laser driver not working


Because your VI misses the LabVIEW basics, like error handling and enforcing dataflow…

 

Mind to cleanup that VI and avoid parallel device access by using DATAFLOW?

Mind to open and close the device just once before/after the loop?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 3
(131 Views)

You should also be looking into producer consumer architecture and using queued state machines. I am guessing the next step is to record the data to a file. The producer consumer will help with in the future. Keep in mind that the example code provided by the supplier is not necessarily the beast way to do this. It was an example to get you started.

Tim
GHSP
0 Kudos
Message 3 of 3
(91 Views)