wrote: I was actually downloading the incorrect bit version (64 versus 32) and that was giving me problems. Thank you all for the help.
That would cause a problem
I'll mark your solution for the next developer that does the same thing.
Thanks are given with Kudos
Then post your VI.
We can't debug paragraphs.
Can you post your code for review as well?
wrote: Then post your VI.
We can't debug paragraphs.
Sure we can. I'll bet you a beer that there is a miss configured DDT in there somewhere.
The driver uses Call Library Function nodes.
LV 16.0f2 works great.
I suspect a restart of the PC works. Will give it a try. I'll also check for a dealloc call.
We can at least help in terms of the hardware. What type of signal does your cartridge heater expect? Which LabJack are you using and which output on that LabJack?
That is why I love this community! Thanks for the information!
Excuse me. Please find attached the VI.
I started to use LabVIEW only recently.
Therefore, I am not an expert.
1. You might want to consider using the Serial.readStringUntil() function in your Arduino code, which will simplify things.
2. DO NOT USE THE BYTES AT PORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
As has already been stated, your Arduino is using the PrintLn command. This means it adds a Carriage Return (0xD, CR) and a Line Feed (0xA, LF) to the end of the message. So all you need to do is enable the termination character and set it to the Line Feed (both defaults on the VISA Configure Serial Port). Then you just tell the VISA Read to read more bytes than you ever expect in a message (I like to use 50) and the VISA Read will wait until it reads that termination character, it reads the number of bytes you tell it (again, set the number of bytes to be larger than any message will be), or you get a timeout.
So from RavensFan's code, I would just delete the constants on the top of the VISA Configure Serial Port and it will work just fine.
It is very hard to debug a picture .
Zip and attach your project for the benefit of everyone else who wants to help you.
But first, open First Look U Point Calibration2.vi and change the absolute path on the block diagram to a relative path. Then open the build specification and add the dynamically called vi to the always included list.
wrote: Excuse me. Please find attached the VI.
I started to use LabVIEW only recently.
Therefore, I am not an expert.
That's ok, you know enough to post and follow advice. You'll be an expert in no time
Thanks Bob, that clarifies -Inf values. And also seems logical.
One query still remains, why isn't there -Inf values for 'Expected Output'.
I tried following with no success (i) enabling PSD only after 4 sec of data is gathered, with no success. (ii) generating timestamp for waveform at 4 seconds interval (iii) making 'restart averaging' TRUE before PSD starts.
Thanks. That's encouraging, but I'm not afraid it's not that easy.
Hi Ramon,
Thanks for your solution. It works!
I also found another way. xlsx files are simply zip files. Inside the zip files are a bunch of xml files spread through a small number of folders. Inside the folder xl\charts, inside the zip file, there are xml files for every chart - CHART1.xml ... CHARTn.xml. The axis labels are stored in these xmls files under a specific tag: XPATH //chartSpace/chart/plotArea/valAx/title/tx/rich/p/r/t.
You do need to strip out the namespaces first. See in the snippet.
I don't see any reason why your chart wouldn't show more points once you have set the X-axis to autoscale.
What I do see is that your VI will execute the For Loop 5 times, and that will be as fast as the DAQ Assistant can return a data point. If you keep hitting the run button, you'll see more data points in groups of 5.
I hope you are doing this with a LabVIEW project. If not, you should. Project files help to manage all of the path stuff and makes moving files much easier. The y also help to reduce cross link errors.
The OP does not fully understand the behavior of the Arduino when a connection is made to the Arduino's serial port. His answer and his "fix" shows that.
What does he do with the Arduino is ready that he carelessly sends out the serial port to LabVIEW. Is it for "show"?
.
1. Right-click on your chart and choose Visible Items->Digital Display. There will be an indicator attached to the graph which will show the latest value. Now you can delete the "Numeric" indicator from your VI. That will make your diagram slightly simpler and eliminate a possible issue.
2. I am very concerned that you do not have a delay in your loop. You might want to add something like a 50ms delay.
3. Your VI does not have the X-axis being autoscaled. Be sure to turn that on.
Hi Dpak,
That seems much more straight forward. You should mark it as solution 
Your question is kind of vague.
When you say you want to "blink an LED N times per minute", does that mean: