Jump to content

vito

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0

About vito

  • Rank
    Active
  1. How much is Wezarp? Had a look at the website and couldn't see a price. Went looking for Wezarp on the LabVIEW Tools Network, as indicated on the Wezarp website, and nothing showed up.
  2. This looks great. I've been urging NI to provide this solution for years. Good to see that others are taking care of user needs. I'm seeing a lot of this lately. LabVIEW may finally become versatile if a user interface can be presented on a tablet or mobile device. Others are also making LabVIEW target other devices. It's starting to look good. Kudos for a great product!
  3. Thanks Michael. I didn't know that one of the Arduino offerings has built in Ethernet.
  4. hooovahh, one of the features of LabVIEW is parallel loops. Sure you can get things done without it, but one of the significant features is not there. I hope single loop operation will be attractive enough, as I'd like to see takeup of this product so that it continues to be developed. I'd like to see LabVIEW compiler for Arduino become what LabVIEW Embedded for ARM was supposed to be. I programme microcontrollers in C. A single loop works, but then I have a SysTick event that fires every 10 ms to lets me do other things and all "events" fire an interrupt that allows the "event"
  5. Filipe, Great to hear that the first release will support the Arduino Due. Given that the Texas Instruments TM4C1294 LaunchPad can be programmed with Energia and that Energia uses Wiring and Arduino framework, do you think it would be a big effort to target it? The big attractions are built in Ethernet (and lots more) and a $20 price tag. If I understand you correctly, the first release will only allow a single loop operation. If so, this will be very limited. Good enough to get a taste for what it can do, but not good enough to use for serious applications. Even a simple mechanism whe
  6. Filipe, this is great. I've been programming with LabVIEW (desktop, Real-Time and FPGA) for about 10 years and this is the best thing to happen to LabVIEW since the Event structure and FPGA programming. It's the best thing to happen to LabVIEW in 10 years! I've been requesting, some would say badgering, National Instruments to do something like you've got under development for 3 years now. Thanks to Arduino Complier for LabVIEW, I don’t have to wait for NI or rely on them. This is a game changer. The fact that you got it to work on a very resource limited Arduino UNO is impressiv
  7. I suspect the board only version may be much cheaper since it does not have WiFi (if you don;t need it). I'm also on Sydney and would like to get one when I have the time to play with it.
  8. Hi Shaun, From my brief look into the various technologies so far, I suspect that NI's Data Dashboard and what you mentioned will become the two standards. The websockets solution will need to be packaged for easy consumption and include a decent user manual. I like the idea of two competing technologies . If it wasn't for such competition, we'd still all be using DOS! Regards, Vito
  9. I've put together a list of the various methods/products that allow a remote device to be used as a user-interface for LabVIEW. The post can be found at http://forums.ni.com/t5/LabVIEW/Using-a-remote-device-tablet-phone-etc-to-provide-a-user/td-p/1813504. I'm interested in hearing your comments and info.
  10. ned, Thanks for your insightful and detailed reply. There's one thign I didn't understand. You mentioned "(... as an aside, in your template code, you could simplify by using the reference provided in the event data node to clear your boolean, rather than using an explicit property node ...)". Which Event Data Node reference do I use and where is it wired? Regards,
  11. QUOTE(JDave @ Nov 14 2007, 12:24 PM) JDave, Yes, it can become confusing to differentiate from actual UI and programatic interaction. This is a strength and weakness of the ESSM architecture. The beauty is that you can click in one place and see all your handlers. The problem is that once you have 50 of them you loose track of which are front panel controls and which you have used. As with most things there are workarounds. You could always label the programmatic interactions starting with, say and asterisk or some other character that you like. This change is easy and reliable since all
  12. QUOTE(ned @ Nov 14 2007, 01:31 AM) ned, I see that you are not impressed with the new proposed Event Structure As State Machine (ESSM) architecture. Firstly, thanks for taking the time to show me the equivalent functionality using a conventional Event Loop And Consumer Loop (ELCL) architecture. My objective is to put up for consideration a simple, effective and expandable architecture for LabVIEW programs. The ELCL architecture requires queues to be established, wired up and destroyed and an additional loop. So it's not as simple, therefore it needs to have other advantages to make up fo
  13. I think that an Event Structures As State Machine architecture works well. It's what I'm using for my project. It's not the sort of structure that is taught by NI, however I think it has some distinct benefits. Three other architectures have been mentioned in this topic: 1) State Diagram 2) Producer/Consumer (Producer can either be a normal While Loop or an Event Structure) 3) Event Structure With State Machine Inside An "Idle" Event Case As EJW stated "The program I have seems a whole lot more complicated in regular diagram form that it would be if I just used the event structure with a
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.