ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
05-09-2013 04:13 PM
Hi,
Can anyone advise on the :-
Running :-
National Instruments LabVIEW 2012 (32-bit)
VI Package Manager 2012
Arduino Uno
First attempt a vi
I followed all the proceedures here http://www.youtube.com/watch?v=RGRhIQneO6w and i get some comms (the Rx led on the arduino uno flashes rapidly) when i hit run on Labview vi , but the led on the board does not flash ..its on, but very dim. Led works ok on arduino ide...any thoughts ?
labview vi screenshots attached.
any help would me much appreciated, if you need more info please ask
thank you.
05-09-2013 04:33 PM
You need to use the correct baud rate. The default baud rate for the UNO is 115200. If you leave the baud rate terminal unwired, it will use the default of 115200 but you can wire if you like.
Also, if the pin mode of a pin and the pin number never changes, you can call set pin mode VI before the loop (it will make the loop run faster).
05-09-2013 10:40 PM
hi Nathan,
thanks for your reply....i changed the baud rate to 115200, still no state change on the uno led !, but the LED on the front panel is "ON"...any idea of next step ?
thank you
05-10-2013 12:06 AM
Do you get any errors? Have you tried the Blink LED example that comes with LIFA? Are you sure that the firmware uploaded to the Arduino successfully?
05-10-2013 04:05 PM
I will have a bit more time over the weekend to investigate it, i will get back to you with some answers then thanks
05-11-2013 12:52 PM
No errors at first When i run the Blink example with LIFA i get RX led on UNO, but no Blink from the board led , it appears as an RGB example, not a pin 13 blink is that right or ? !!! not sure about that , Fimware appears to load ok ..please see attachment
...tried a gain and got this error, it was'nt there before
05-12-2013 02:08 AM
If you google the error you can find the official documentation of it and look through the possible solutions.