Jump to content

Dan DeFriese

  • Posts

  • Joined

  • Last visited

  • Days Won


Dan DeFriese last won the day on July 24

Dan DeFriese had the most liked content!

Profile Information

  • Gender
  • Location
    Milwaukee, WI USA
  • Interests
    Golf, Guitar, and Barley Pop

LabVIEW Information

  • Version
    LabVIEW 2010
  • Since

Dan DeFriese's Achievements


Newbie (1/14)



  1. Try: http://opengtoolkit.cvs.sourceforge.net/viewvc/opengtoolkit/pipe/
  2. There is a symbolic path, [iNSTALLDIR], that you can use in the installation builder for this purpose. See attached.
  3. Just out of curiousity... What's the use case for applying password protection on the VIs? I've never really thought about this before. ~Dan
  4. No I've never done it but you should be able to iterate through your VIs using the LockState.Set Invoke Node. There is also a setting for applying a password to source in Source Distribution build spec. Okay just created and example which will set a password on all VIs in a directory recursively - BE CAREFUL what you point it at Batch Password Example.vi
  5. My imagination is limited so I selected the context help - it sends you to '(Incomplete) Beta Function'. So I'd guess that either it dropped off someone's radar at NI or there was a problem with the implementation and someone forgot to remove it (and dropped off the radar ever since!).
  6. Hey Jon, There is a little task manager tool that was discussed a while back. Maybe it can help you. http://lavag.org/topic/14921-labview-task-manager/page-2 ~Dan
  7. I've never seen the lvlib resort to absolute paths, but if it is modified while in the LabVIEW directories (vi.lib, instr.lib, user.lib, etc...) it may get saved with symbolic paths instead of relative paths. As in this example from my instr.lib folder: <Item Name="Aardvark Convert Error.vi" Type="VI" URL="/<instrlib>/aardvark/aardvaru.llb/Aardvark Convert Error.vi"/> <Item Name="Aardvark GPIO Set.vi" Type="VI" URL="/<instrlib>/aardvark/aardvark.llb/Aardvark GPIO Set.vi"/> <Item Name="Aardvark GPIO Direction.vi" Type="VI" URL="/<instrlib>/aardvark/aardvark.llb/Aardvark GPIO Direction.vi"/> Could your source have been in these LabVIEW directories? ~Dan
  8. The simple answer it that clock speed is the only contributing factor to performance. In either case, it appears your application needs some attention with regard to efficient programming techniques. My first step would be to run the program in your development environment and use the Profiler (Tools -> Profile -> Performance and Memory) to find which parts of the program are consuming the most resources. ~Dan
  9. Sorry I didn't realize this is a homework assignment. In that case, you can learn about TFTP and implement your own solution by reading RFC 783 and RFC 1350. This will also give you an understanding of what chunks are. Good Luck! ~Dan
  10. There's a TFTP example on the NI website: https://decibel.ni.com/content/docs/DOC-8301 No need to reinvent the wheel.
  11. This is not a bug. Rings are not bound to the string values like they are in an enum. This is why you can change the strings in the ring, but can't change the strings of an enum at runtime. LV's Help explains it better. See: "ring controls, compared to Boolean and enumerated type controls " in the LabVIEW help.
  12. I couldn't agree more. The best thing I took away from the CLD is that my approach was way too complicated for what I was being asked to do. My submission was good-enough to pass, but I didn't complete all the features. I've really concentrated on the KISS principle ever since. Thanks NI!
  13. From the manual's example code in QBasic. OPEN "COM1:1200,E,7,1,DS,RS" FOR OUTPUT AS #1 I see that the port settings are Baud Rate = 1200 Parity = Even Data Bits = 7 Stop Bits = 1 ...and there may be hardware handshaking "DS,RS" (I've never actually used QBasic... just seen it once on the History Channel!) Are these the settings you're using?
  14. Have you looked into to pointing the user(s) to Signal Express? It sounds like you're reinventing the wheel here.
  • Create New...

Important Information

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