Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Mellroth last won the day on May 7 2018

Mellroth had the most liked content!

1 Follower

Profile Information

  • Gender

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since

Recent Profile Visitors

3,192 profile views

Mellroth's Achievements


Newbie (1/14)




Community Answers

  1. Thanks for the reply, the thing for us is that the customer needs ZMQ (ZMTP) on a Pharlap-based cRIO (no inter-process stuff). We are essentially evaluating our options; either implement in pure G, or recompile for Pharlap and change the wrapper VIs to handle this. Any chance you could share the G code? /J
  2. I know this is a really old thread, but I just saw Darins post about implementing ZMTP in LabVIEW. Was this a native LabVIEW implementation or did you use a wrapper around the ZMQ windows DLL? /J
  3. I might misunderstand what you are trying to do, but do you really need the GUID conversion? Once you get to the BuildSpecs and its OwnedItems you can query each OwnedItem for the TypeString. This typestring is different depending on if you have a build script that is EXE, Source Distribution, Zip etc., but you can cast any of them to BuildSpecification. /J
  4. First of all, thank you for posting this I've used this in a couple of internal projects, and doing so I've seen and fixed a few issues. The changes are: * Fixed Dispose Notification Icon.vi so that it correctly removes the tray icon even if error * Updated Set Tray Icon (string).vi so that you can have any image type stored as string on your block diagram * Updated Set Tray Icon (string).vi VI description to reflect this change * Added basic error handling to the example (dialog and clear) The changes were made in a later LabVIEW version and backsaved to 8.6. /Jonas NotifyIcon_updated.zip
  5. I think it is the Linux based cRIOs that come without FTP enabled.
  6. I use TortoiseSVN exactly like this, I only want to point out that the main reason I press cancel and then save again is that this prevents me from saving over another file by accident. You set this up in the TortoiseSVN client configuration file. 1. Enable auto props (uncomment ###enable-auto-props = yes) 2. add a line at the end of the [auto-props] section that reads *.* = svn:needs-lock=True You can also have a pre-commit hook set on the server to detect if any commited file lacks the needs-lock property. /J
  7. Just a bit of warning regarding the built-in json methods. If you flatten a cluster containing a string with \00 characters in it, it all converts nicely to json, but the built in functions fails to convert the strings back to the original value. The reason is probably that the json parser stops decoding the UTF8 encoded string at \00 (IMHO this is clearly a bug since strings are not NULL terminated in LabVIEW). /J
  8. I think I would argue that the LabVIEW RMS calculation is more correct; if you want to get the same reading as the DMM, you would have to estimate your data to be a clean sine-wave (or calculate the RMS over more periods). /J
  9. Maybe I'm stating the obvious, but if you develop on LabVIEW for Mac, you use the command-key + the short cut, but when you switch to the virtual machine you will have to use the ctrl+shortcut instead. In the link Hooovahh gave you (https://lavag.org/to...ing-in-labview/) you can find a solution for ctrl-key shortcuts not working in the Virtual machine. /J
  10. On my MacBook Pro, I use a number of Virtal Machines running with VirtualBox regardless if I boot MacOSX or Windows. The only issue so far has been that one USB device driver failed to load in the Virtual machine. /J
  11. I do all my development on a MacBook Pro in Bootcamp and VirtualBox, and I have yet to find something that doesn't work in LabVIEW for Windows. The only thing I've found that doesn't work all the time, is that USB access in virtual machines can be a bit shaky. But, this seems to be more related to VirtualBox than the MacBook. /J
  12. Thanks for the comments Yair, sorry for the delay in response. The WireQueue service is mostly intended for Live data monitoring, and the data posted online is defined by the user of the LabVIEW API. Videos and more information are in the works. Since it is an open beta we expect the phone interface to change a lot while we get comments from users, but the Andoid app is available on AndroidMarket, and the iPhone app should be available within 24h. We have discussed to open up a public test account sometime after NIWeek, but have not decided on which parts we can make public (read access only should not be a problem). I'll post here once we have that in place. If you are attending NIweek, I would suggest visiting booth 923 for a live demo. /J
  13. WireFlow enters the world of IoT! Today we are proud to announce an open beta of WireQueue; our cloud based service that allows customers to build secure IoT solutions for data logging, monitoring and control of LabVIEW/LabVIEW RT targets. The WireQueue system consists of: a LabVIEW driver that makes it easy to exchange messages with other clients, monitoring apps for mobile devices and a cloud based server. WireQueue uses open standardized protocols and all communication is secured with SSL/TLS. Sensitive commands can be further protected with hardware authentication using WireFlow dongles. Visit https://www.wirequeue.com for more information, and to request a trial account. You can also find us at NI-Week in booth 923. //The WireFlow Team
  14. At the moment I don't think you can. It is my understanding that EtherCAT requires the Slave ethernet interface to be more advanced, because it is the slaves that manages the us synchronization between nodes etc. So in order to get a PXI chassis to be an EtherCAT slave a special network card would have to be used. I think there was a third party library posted on NI.com that allowed you to interface the beckhoff modules, but I don't remember if it was also possible to use for this scenario. /J
  15. I know this was an issue with LabVIEW 2010, but got the impression that it was fixed in later versions?
  • Create New...

Important Information

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