Jump to content

Kurt Friday

Members
  • Content Count

    246
  • Joined

  • Last visited

  • Days Won

    7

Kurt Friday last won the day on September 8 2009

Kurt Friday had the most liked content!

Community Reputation

36

About Kurt Friday

  • Rank
    Very Active
  • Birthday 12/18/1971

Profile Information

  • Gender
    Male
  • Location
    Sydney NSW
  • Interests
    LabVIEW, Riding my Triumph, playing with my dog Milo

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    1996

Recent Profile Visitors

2,991 profile views
  1. Thanks Eventually I'll add the ability to edit an item and read back the cluster Also right click and view an item such as an array as a waveform graph. If the item is another object then display its attributes as well. The Variant Probe looks cool I'll take a closer look
  2. Hi All I'm playing around with visualising clusters as a tree structure. I've got some nice code working that I thought I would share. It's part of an abstract data viewer that I'm working on. Code is based on Open_G Variant and Open_G Config File tools ClusterViewer.zip
  3. I had a similar issue thanks for the post I found I had to manually copy LabVIEW 2014\resource\lvimptsl.dll into the root of my exe
  4. Hi All Apologies for not replying I didn't realise that there were posts here. Regarding the Pump example, its just a simple demo of the capability of the framework. Probably the best way to handle not pushing another pump volume command while it is already pumping is to have a busy state in the datamembers and don't allow any new pump volume commands to be placed in the queue until it is not busy. Spot on! In most cases all you need is the command queue to send commands into the process, however there are situations where you would want the process to message up to the public l
  5. Maybe Symbio could send the GDS and AddQ vi's that are in question to an independant 3rd party. Once the 3rd party has recieved the vi's Symbio could provide the passwords to their Vi's and AddQ can provide the passwords to theirs. The independant party can then provide a report on the level of similarity.
  6. So some developers jumped ship from Endevo/Simbio to start AddQ, took the GDS sourcecode, repackaged it as their own and added a few bells and whistles to it, without your permission. The crazy thing is that if anyone wants to add OOP farmeworks into GDS all you have to do is contribute, and if you have ideas or sugestions on new features to GDS then Mikael would love to hear it. I'll keep using GDS, it Rocks, and I'm looking foward to contributing more.
  7. Yeah, definitely but it seemed to have issue with this file as well. LV2009_ENG_32.exe->(ZIP)->Products/MDFSupport/MDF/MDFSupport1.cab->misetup.bin.F5D87C60_CF9D_4AC4_8480_40189BD11225
  8. OK, I think this is a false alarm but I I think this needs to be investigated. I downloaded LV2009_ENG_32.exe from the standard download and evaluate LabVIEW link https://lumen.ni.com/nicif/us/lveval/content.xhtml However when I run the downloaded file "LV2009_ENG_32.exe" through F-PROT virus scanner I get the following virus detected W32/Virut.AI!Generic See the following report generated by F-Prot -----------------------------SCAN REPORT----------------------------- F-PROT Antivirus for Windows Antivirus Scanning Engine version number: 4.5.1 Virus signature file from: 11/4/2009, 3:2
  9. Hi Hacti Do the crashes now occur even tough you don't work on the original conflicting VI? Can you tell more about the particular vi that caused the issue?
  10. Jim she is awesome, congratulations mate
  11. I've just released GOOP Developer 2.3 This latest version is built under LabVIEW 9.0 and appears to resolve the Vista issue and also provides LabVIEW 9.0 compatibility. The source code for GOOP Developer 2.3 is also available. You can download the GOOP Developer 2.3 Installer and source code here
  12. Looking forward to the long weekend

  13. OK so you have a RS 485 to 232 converter. Probably the first thing to do is check that your serial interface is OK and your cabling is fine, this is always a gotcha. In my experience the first time you plug some serial device into your PC it doesn't work first time, its either that I need a null modem or my com port isn't setup correctly, so check all that. Add into the mix that you have a 232 to 485 converter you have compounded the issue. Probably try sending packets via hyperterminal and check them on the 485 side with a scope, its a good reality check.
  14. Hi Hacti Does this happen when working on a specific project or VI, or will it occur if you start with a fresh VI and start playing with it? Does it happen in development or run environment? Take a look at this link from NI, it may shed some light.
  15. The NI-OPC Server supports the UDC 3000 and UDC 2500 see the following Link http://zone.ni.com/d...p/id/6417#toc17 So with the NI-OPC Servers you can communicate to your UDC controller, in LabVIEW you just use DataSocket to read and write to items. Alternatively Honewell probably have their own OPC Server which you should be able to connect to. You mentioned the Burr Brown Converter, what type of converter is it? do you have more info?
×
×
  • Create New...

Important Information

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