Jump to content

Phillip Brooks

Members
  • Posts

    875
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by Phillip Brooks

  1. Isolation? I've always wanted a reason to check this out: optical USB cable... https://www.corning.com/optical-cables-by-corning/worldwide/en/products/usb-optical-cables.html You would need to provide your own power to the camera at the far end.
  2. Someone reported a similar issue on the dark side. Are you using typedefs? https://forums.ni.com/t5/LabVIEW/chm-help-file-and-executable/m-p/2703303#M802558
  3. Don't use this functionality, but the NI Doc reference has a note: Maybe the exe is expecting to find the help file in the support directory?
  4. You have to be in the control editor. Drop a control on a VI FP, select the FP control and use Edit -> Customize Control... from the pull-down. Now, in the control editor, select the control and select Window -> Show Parts Window
  5. I would suggest posting on the NI forums and seeking out Mark Yedinak. He's works at Zebra and has been answering LabVIEW / ZPL related questions for a long time.
  6. Look for vi.lib\Platform\fileVersionInfo.llb\FileVersionInfo.vi
  7. Yikes! http://forums.ni.com/t5/LabVIEW/LV-2016-Known-Issue-583670-Can-I-really-no-longer-build-for-Win7/td-p/3341369
  8. Are the client and server both running LabVIEW? Do you have tftp client or server available on either of the systems? tftp is UDP based, but takes care of the handshaking. https://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol
  9. https://medium.com/@cscalfani/goodbye-object-oriented-programming-a59cda4c0e53#.4476pk9xq
  10. I remember reading about a VISA Python library a couple of years ago. Might make traditional instruments easier to interface to... https://pypi.python.org/pypi/PyVISA ( edit: Looked at PyGMI and it uses PyVISA and PySerial )
  11. I found the root cause of the problem. I had an LLB file that contained a VI with an invalid character in the file name. LabVIEW would compile the VIs, but at the end of the compilation process, the files are copied into a folder named for your .exe. The invalid Windows file name could not be created, but the error message never contained the name of the file. I sent the LLB to NI and declared that I think this is a bug. I found it by converting all of my LLBs to folders using the LLB Manager. When I got to the problem LLB, the conversion reported an error on the badly named file. I copied the LLB, deleted the offending file, converted the copied LLB to a folder without error. I manually saved the offending VI as a file into the folder without an error. Then I could compile. I've had bad experiences in the past when I use "Save As" into an LLB to create a new VI. The "Save As" dialog is not a standard dialog and can act wierd when you use the control keys to move about within the name box. I might have somehow inserted a TAB or control character that LabVIEW was willing to accept as a VI name inside an LLB. LabVIEW just didn't know how to fix the name when saving it outside the LLB. I spent over a week screwing around with creating new projects, mass compiling and re-installing LabVIEW because of this. I know that many people will say "don't use LLBs", but this is the first time I have been bit by them in such a bad way.
  12. So, Seven years later, I have a project in LV2014 that has been fine for months and it suddenly starts giving me a 'dirty-dot' on open and the same cryptic message "An attribute of the project was changed." when closing: I also can't create an executable: But the code runs fine from the development environment. I created a new project file and it has the same problem. Error when building: Anyone know how to fix this?
  13. I hope the LAVA forums don't copy the new NI forums UX. Ugh...

    1. Ajayvignesh

      Ajayvignesh

      You hate the new NI UX as I do? :D

  14. http://themacview.blogspot.com/2014_08_01_archive.html LabVIEW 2014, First 64-bit Version for Mac POSIX Paths This was long overdue. Paths in 32-bit are formatted in HFS Classic format. 64-bit uses the more common POSIX paths. It's mostly showing slash (/) instead of colon ( between path elements (although there is more to it than that). There is also a little bit of magic that happens in 64-bit when a path in a string is converted to a path type that allows either format, and then converts it into POSIX style. You can try this by copying the path from the 32-bit path indicator and paste it into the 64-bit indicator. Once focus leaves the indicator, the path will be converted to POSIX format (it's pretty fun to watch). This magic also happens when using the String to Path primitive. You can have a string of either format and it will convert it to a POSIX path. This makes it easier to transition between 32-bit and 64-bit as you are testing your VIs in 64-bit. Some other VIs that assist in dealing with paths between 32-bit and 64-bit are Path to Command Line String.vi and Command Line String To Path.vi inProgramming -> String -> Path/Array/String Conversion palette. These VIs are helpful in building a path that can be used in System Exec.vi or system shared libraries in a cross-platform manner. They have actually existed in LabVIEW since before 2009, but are added to the palettes now to assist in transitioning between 32-bit and 64-bit on Mac. Another path related VI that is helpful for Mac users is Executable Path To Command Line String.vi. This VI helps in getting the path to the executable in an app. This is particularly helpful writing cross platform code that will launch LabVIEW built apps, LabVIEW itself, or other GUI applications. Windows and Linux just take the path to the EXE. On Mac, the .app is really just a folder. This VI will give you a path to the executable you can call from System Exec.vi, in a cross-platform way. This VI did not make the cut for the palettes, but you can find it in vi.lib/AdvancedString.
  15. No, it's not about LabVIEW, but makes me think about why I collect so much data FlowingData - http://goo.gl/C8Am

  16. I was traveling last week, so I didn't get to spend much time on this. While searching salesforce.com I discovered that you can override the POST method with an arbitrary method name by appending to the URL. https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_update_fields.htm Append "?_HttpMethod=PATCH" and Bob's your uncle!
  17. I'm trying to use the LabVIEWHTTPClient.lvlib functions to communicate with Salesforce.com I can authenticate, but my Salesforce IT guy tells me that Salesforce uses a concept called "upsert". It's update and insert combined; but I need to use the PATCH Method instead of a PUT or POST method. I can't seem to find any reference to the PATCH method. I believe the LabVIEW library uses curl under the hood. Anyone have any ideas? HEADER: HTTP/1.1 405 Method Not Allowed Date: Fri, 16 Oct 2015 19:20:35 GMT Sforce-Limit-Info: api-usage=36839/7918000 Allow: GET,HEAD,PATCH,DELETE Content-Type: application/json;charset=UTF-8 Transfer-Encoding: chunked BODY: [{"errorCode":"METHOD_NOT_ALLOWED","message":"HTTP Method 'POST' not allowed. Allowed are GET,HEAD,PATCH,DELETE"}]
  18. When searching for a USB-RS232 adapter, look for those that use an FTDI chipset. If it has a Prolific chipset, it is probably more like epic ( fail that is ) I recall reading that the Prolific chip is often counterfeitted in China and ends up in the cheaper devices. http://stackoverflow.com/questions/32087482/how-to-diagnose-visa-rs-232-communication-failure-in-labview/32134821#32134821 I've purchased the 6' Sabrent CB-FTDI from Amazon (~$15 US) many times and never had a problem with it.
  19. I prefer Airwolf... ( http://users.elite.net/gurpal/tv/airwolf.mid ) Convert from MIDI format? http://www.skytopia.com/project/articles/midi.html http://subsynth.sourceforge.net/midinote2freq.html
  20. I did something similar, but no LVOOP http://forums.ni.com/t5/LabVIEW/Plink-PuTTY-works-30-of-the-time-using-System-Exec-vi/m-p/3006795#M860452
  21. I posted an idea on the NI forums about a year ago that is long overdue; the ability to define a regex for VISA message termination. http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-regex-based-termination-string-option-to-NI-VISA/idi-p/2859152 I had the idea after tinkering with a .NET library called SSH.NET. One of the methods of a stream is Expect. http://forums.ni.com/t5/LabVIEW/Plink-PuTTY-works-30-of-the-time-using-System-Exec-vi/m-p/3006795#M860452
  22. Maybe you can use this to resolve the path? https://decibel.ni.com/content/docs/DOC-13708
×
×
  • Create New...

Important Information

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