ooth

I like the map option. If you still want a control that looks like the ComboBox maybe try a Multicolumn Listbox but hide the second column that contains the value. forum.vi

Seems like if you just write a normal enter character (\n) in the string, the text in Excel will be on two lines just as if you press Alt+Enter.

Maybe try this https://forums.ni.com/t5/Feedback-on-NI-Community/How-do-I-get-a-snippet-from-the-board-into-my-block-diagram/m-p/3763571#M15575

If you wanted to mess around with a free version of NPOI here's a github project. https://github.com/Benji667/LabVIEW_NPOI

Dan, Maybe something like this could help https://www.ni.com/en-us/shop/software/products/xlr8.html

I know you can't manually extend the bottom of the function like you can with other array functions, but if you wire in a 2D or 3D array then the Delete From Array function will automatically resize.

Also I have found that ActiveX needs to work with the 32bit version of Excel. I don't have any experience with Office 365 and not sure if it has 32bit support.

If the ActiveX property nodes are blank (show "No Properties" when selected) then it is probably related to what Rolf described when Office was installed. This is a work around https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KZNSA2&l=en-US

Same thing happened to me. This article solved it for me. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KZNSA2&l=en-US

For anyone else that might have this problem. (since Michael already provided the file) I needed a legacy NI-DAQ recently and I sent an email to NI explaining why I needed it. They provided a link that was valid for 24 hours. So that's a possible solution to take. Apparently NI pulled all the legacy DAQ because it never checked for malicious 3rd party devices.

Here's a pic of the comm setup tab

Antonio, You are correct that it probably doesn't respond to the IDN? cmd since it wasn't listed in the document. So I would suggest to try the first cmd "Model name code access". So change the cmd to #0A0000RA60D0A (this is taken from 2. Model name code access under Ex) Also be sure to change the comm setting per the document 19200,E,8,1

Sometimes I do make it to UK, but not so far this year. My suggestion would be to turn on Highlight Execution and run the VI. Check if an error occurs out of any of the VISA VIs. Now if that doesn't help I would: 1. Open NI MAX 2. Right click on the ASRL4::INSTR resource and select Open VISA Test Panel 3. Select the Input/output tab 4. Try sending the default message of *IDN?\n by clicking the Query button. I first get the instrument to respond to the IDN cmd using MAX before I start programming a VI. This tells me the connection is good.

That error code says, "VISA: (Hex 0xBFFF0072) The resource is valid, but VISA cannot currently access it." I would think that another program has control of that comm port. Make sure all the other programs are closed and then run the LabVIEW VI. You might have to close and re-open LabVIEW after you closed the other programs.

Hi, First, I would not use the VIs I made before since they were formatted just for that meter's protocol. I built a VI based on the protocol you supplied. It takes a command string (ex. #0A0616N), calculates the checksum, and then sends the command. I didn't parse the return message but you can do that based on which kind of command you send. The VI is saved with LV 2012. Good Luck Omega.vi