Leaderboard

Hi guys; Check out what we are doing with LabVIEW and Arduinos. http://www.tsxperts.com/arduino-compiler-for-labview/ We created an actual LabVIEW compiler for Arduino targets that allows Arduinos to be programmed in LabVIEW. Figured to share this with the community. Cheers Filipe

Very nice! My kids' elementary school has the district's only school-based MakerSpace program. I volunteer teaching 3rd-6th graders to use Lego Mindstorms NXT. With that giving them the background into graphical programming, this would be a great next step.

Inspiration? http://en.wikipedia.org/wiki/Category:Messenger_gods I sort of like Isimud

Considering your other thread about DMAing data around, this must be about the other extreme in performance! One UDP message per 4 byte floating point value!

Michael is right. It does not use the C code gen toolkit; otherwise it would cost $10k + a tinny little bit for the Arduino piece. This way we can charge just $(a tinny little bit for the Arduino piece). Not only that but we have better control over the type of optimization we do that is more specific to the Arduino target. As you can imagine, if we were to leave the result of the LabVIEW code interpretation without any optimization on the code generation side, we would starve an Arduino Uno before we could complete the "Hello World!" sentence of the test VI. Btw; check out this video we just posted showing a demo of the compiler. https://www.youtube.com/watch?v=DE2we6o7erI

I'm not sure I fully understand your setup, but if you have a .NET assembly compiled as a dll, you should be able to call that using the normal labview .NET interface on the connectivity pallet. Checkout https://decibel.ni.com/content/docs/DOC-9138 for a quick example.

I would strongly suggest NOT using Excel to save your data. Pick a method to save your data (examples include a simple binary file, TDMS, CSV files, databases, etc.) and if you want to see the data in Excel, export a copy of the data to a format that Excel understands. That way, your data will not be dependent on what the user does.

What a bizarre workflow. Are many people doing this? I leave code at - what could you call them? micro checkpoints?. Points in the day to day development that you can draw a line under and say "that bit is working". Maybe not enough of a leap forward to warrant a commit or tick off a milestone. Maybe even a test to "see if it flies" sort of thing, but a meaningful juncture in the development. If it means I have to go and have a coffee or chat with other developers for 1/2 an hour before the end of day-so be it. If it means an extra hour or so after the end of day, so be it. I suppose if you are a militant clock watcher, then I guess you just drop your tools when the bell rings regardless of the state of the code. I don't have any issues remembering where I am in the code on a day-to-day or week-to-week basis but for commits and at the end end of day, the code is never broken and the recently used lists usually has the last VIs and projects I was fiddling with.. It reminds me of an argument I had once about the trunk in SVN. A colleague said that it was ok for the trunk to be broken and waved some kind of book in my face that apparently was the word of god on the subject. My position was that he he was nuts and should stay away from my repositories but I fell short of telling him what I would do with the book if he broke any of my repository trunks