Jump to content

TomWP

Members
  • Content Count

    9
  • Joined

  • Last visited

    Never

Community Reputation

0

About TomWP

  • Rank
    LAVA groupie
  1. Sorry, wasn't supposed to be an advert. Have changed it to a post rather than a link. Was just trying to save posting it here.
  2. OK, have coded an example using this architecture, see below. Please feel free to download it and comment on it. Download File:post-12-1077199446.zip
  3. Firstly, this is just an extension of Jack Hamiltons ideas on the State Machine Architecture, so credit where credit is due. I have taken the queued message handler from the NI examples and added a variant to the queue. This enables you to pass data directly to a state, this saves memory if this data only has a short lifetime. It also alows the introduction of a general error handling frame. I have also added the event structure with a 50ms timeout as a frame in the main application. Best thing is to look at the example.. Has anyone employed this architecture before, if so how did it pan-out? Otherwise it would be good to hear your views on this idea. Must stress, I haven't used this in anger yet; i am posting it here for comments. Thanks, Tom. [EDIT: Just spotted some mistakes in the first version i posted here, have updated the file.] Download File:post-12-1076669963.llb
  4. I have used LabVIEW for a number of years and believe in reusing code. If i have a complex problem to solve i often scour the internet to see if anyone has solved it before. Have been thinking that it would be great to have a centralised repository for everyone wishing to share code. This could be accessed through a plug in menu to LabVIEW, i.e. you click Tools -> Code Repository on the main menu and it list, in categories the availiable VIs. These could be submitted then peer reviewed before apearing on the list. The list could be stored at a central LAVA server. The problem is that at the moment there are so many places you can get VIs from. I realise OpenG.org are trying to centralise things, perhapse we could use this as the basis for the plug-in. Tom.
  5. Sounds like a good idea! If you hear of anyone else in the UK looking for LabVIEW help I would be glad to assist. Just in the process of setting up a LabVIEW consultance here, when that is going I will devote some effort to getting things going.
  6. Hi guys, I am a LabVIEW user based in the UK. I would be interested in helping with the development of any open source test stand type product. Please email me if i can help in anyway. Is there any representation of LAVA here in the UK? Regards, Tom.
  7. I have been using the merge modules supplied with LabVIEW application builder inconjunction with third party install builder applications. All modules compile correctly into MSI files EXCEPT the 3D graph module. I have contacted NI about this problem. It seems that this problem was noticed a number of years ago and solved but has re-apeared in recent versions. The recent versions seem to be upgrades of modules without the bug fix.
  8. Hi, I have just read Jack Hamiltons presentation on Deploying LabVIEW applications using a custom installers. I have been faced with the same problem that is trying to be solved here. How to make custom, professional installs that may include more than just labVIEW or require more options. However when i was faced with this problem i had not seen this presentation. I solved the problem by using an off the shelf install builder (install shield express) and using the merge modules that come with the application builder. By selecting the relevant merge modules all the required components can be installed, including device drivers and registering ActiveX components. However when using this approach i did encounter some problems, some of the NI Merge Modules are not fully compatable (3D graph module), i spoke to NI and they are looking into it. On the whole i think this is a much simpler solution to the problem, install shield express only costs
×
×
  • Create New...

Important Information

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