09-27-2021 12:44 PM
Hello,
I have a table in excel in this format:
The second row is the data value $AC01 in hex, with the binary conversion along the rest of the columns. The row above that is a description of the block of bits.
I wanted to know if there is a way to get this table into LabVIEW?
09-27-2021 12:50 PM
It would MUCH easier to work with the raw data rather than to convert a conversion. Do you have the raw data before it goes into Excel?
09-27-2021 12:59 PM
Not sure what you want to convert to what and from where (there is no excel and both elements are controls). Can you be a bit more specific? Thanks!
Maybe something like this?
09-27-2021 12:59 PM
The input data values is a hex array. I have updated the VI for the input array. The left column is the address array and the right column is the data array.
Thanks!
09-27-2021 01:06 PM
I have attached the excel file to draw the data from. How can this data be displayed in LabVIEW for processing downstream? That is, take the excel file in and display the excel file entry in a LabVIEW table?
The operation of the program should:
1. read the excel file
2. display the table (as is excel) and
3. manipulate the data row like changing bits
4. use those changed bits for further processing.
The main idea is to bring in the excel file into labview with the description and data so the respective bits to change can be easily viewed.
09-27-2021 02:39 PM
I guess the hardest part is getting the data out of Excel. You have to use the Report Generation Toolkit.
09-27-2021 03:57 PM
@billko wrote:
I guess the hardest part is getting the data out of Excel. You have to use the Report Generation Toolkit.
That's the easiest way, but if you like headaches, you can use Active-X instead.
09-27-2021 04:17 PM
@paul_cardinale wrote:
@billko wrote:
I guess the hardest part is getting the data out of Excel. You have to use the Report Generation Toolkit.
That's the easiest way, but if you like headaches, you can use Active-X instead.
RGT is just a bunch of ActiveX wrappers, I think? I don't like the dependency on Excel because changes to Excel could very well break the code. Too bad this wasn't a .csv file.