02-22-2023 06:34 PM
02-25-2023 07:23 AM
Are you trying to hire a LabVIEW developer? There is a Forum here for that purpose. If you want to learn LabVIEW and do this job yourself, you need to provide us with more information so we can understand your problem and suggest "learning paths" for you. Begin by letting us know what version of LabVIEW you are using (and whether you are using 32-bit LabVIEW or 64-bit LabVIEW), as well as the (NI) Hardware that you will be supporting.
Bob Schor
02-25-2023 03:14 PM
I am guessing that the One Wire interface is a USB device that appears as a Virtual Com Port through the FTDI drivers. Like this one: https://www.ibuttonlink.com/products/linkusbi because FTDI does not make a One Wire interface.
More information on the interface device would be helpful...
But if it is indeed using FTDI VCP drivers then the One Wire interface will appear as a Com port in Windows and LabVIEW. Therefor Windows should "ask for" the driver when you plug it in. No special driver will be needed in LabVIEW and communicating with it using VISA will be basically the same as communicating with any other instrument or device on a Com port.
02-25-2023 03:42 PM
Not trying to hire but looking if somebody here have tried it and have a working vi.
i am using Labview 12.
02-25-2023 04:39 PM
My apologies for not providing clear information.
we are currently using a Maxim 17330 EV kit interface to communicate to BMS with Maxim 17312 fuel gauge. The Maxim 17312 Fuel gauge communication protocol is 1-wire.
The Maxim 17312 EV Kit interface have FTDI Chip on it with a virtual com.
i can communicate to Maxim 17312 EV Kit using FTDI Labview driver thru serial communication without any issue.
the issue i am having is the communication to the BMS with Maxim 17312 Fuel Gauge 1-Wire communication.