Jump to content

Mellroth

Members
  • Posts

    602
  • Joined

  • Last visited

  • Days Won

    15

Posts posted by Mellroth

  1. On 12/2/2016 at 9:33 PM, Darin said:

    Holy blast from the past, but back in the day I did create a pure G implementation of a limited subset of ZMTP.  Basically I implemented what I needed for REQ/REP and PUB/SUB peers over TCP and some other low-hanging fruit.  A few MUSTs and several SHALLs in the RFC were ignored along the way to suit my needs (mostly self-educational).  It was strictly version 2.0, no dealing with v1.0 peers (plus it is now at least v4.0).  Looking back I will just say that I was not lazy, I was guarding against downgrade attacks....

    These days I use 0MQ a lot, but mostly over inter-process connections which requires platform-specific bits so pure-G is out, and at that point I strongly suggest just wrapping libzmq (actually if pressed I would suggest wrapping it in all cases).   I do not say this about very many libraries, but this one has been a pleasure to work with across several platforms with many different language bindings.  In my use cases I have not run into any problems with my wrappers

    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.

    On 11/27/2013 at 6:05 PM, Darin said:

     

    Been there, done that.  I have G implementations of ZMTP (at least most bits I need) and AMQP (0.9.1 not the 1.0 trainwreck).  I tend to use AMQP most often since my code is more complete (and there was more adoption of it when I wrote it), but they are both great.  The brokerless nature of ZMQ can be great when you need it, turns out most times I was implementing a de facto broker and could have stuck to AMQP.

     

    Unfortunately the specs are really laid out seductively in terms of classes and methods so I gummed up the works by using a bit too much LVOOP (not to mention busted my carpal tunnels).  Performance is ok, but as I de-LVOOP it is finding another gear.  I create worker pools consisting of simple  LV workers and similar C++, Java, or Python workers and see what share each worker does.  LV is behind, but getting up there with the big boys.  The LV9 to LV12 performance kick was also welcome here.

     

    The AMQP implementation gave rise to one of my new mantras:  No LVOOP in a loop.

    Was this a native LabVIEW implementation or did you use a wrapper around the ZMQ windows DLL? 

    /J

  3. I'm walking through a LVRT Project using the VI Server API, trying to find a particular build spec on my FPGA target. I can get the target ("FPGA Target") by name and use that ref to find the build spec by its name, but the reference returned can't be cast to type ProjectItem:BuildSpecification. If I probe the reference wire, the only interesting thing I see is the type GUID...

    {F4C5E96F-7410-48A5-BB87-3559BC9B167F}

    Does anybody know of a way to deduce the VI Server object type from this GUID so I can perform a downcast on it?

     

    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 :thumbup1:

     

    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. So if I'm working on a VI and I don't have the lock I will hit save, and LabVIEW will prompt saying it can't save it is read-only and the explorer window will be opened asking me where to save it.  I will in this window right click my file and get the lock.  I'll then cancel that window and save again, and this time it will save because I have the lock and it isn't read only.  

     

    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

    • Like 1
  6. I have a Mean of ~0.013 for the 0.65V sine wave. Not enough to offset it. However my sine waves are not always nice. It captures the Glitch Energy and seems to be offset to the positive by much more.

    It can reach the 1V at times. Not sure how it can get those kinds of values...

    gallery_17307_121_4263.png

     

    Both the 6723 and the 6225 are in the same PXIe-1073 chassis.

     

    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 

  7. i tried both command keys on the mac...to no avail

    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

  8. I am forgoing the option to dual boot Windows on my Mac so performance is not affected. Rather, I am looking for a reliable virtual machine that LabVIEW performs the best on. 

     

    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

  9. I use LabVIEW for Mac on an iMac regularly. What do you expect to not work?

     

    You don't have many hardware IO interfaces on the Mac but running LabVIEW for Windows in a virtual machine won't give you more options for sure. And BootCamp or whatever that is called nowdays likely will be also not a full solution since Windows doesn't come with drivers for every hardware component in a MacBook Pro.

     

    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

    • Like 1
  10. Sounds interesting, but I don't think the functionality is clear enough (things like "Is this for live data? Historical data? What does the web app look like? What does the phone app look like?", etc.). I would suggest creating some videos and examples and maybe also adding a public test account which people can connect to (at least for reading, if you don't want someone flooding your server with useless data) to see how the system works.

     

    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

  11. 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

    post-5958-0-09010200-1436449530.png

  12. Hello Experts,

    I would like to operate a Labview RealTime system (PXI) as EtherCAT Slave. The master system should be a Beckhoff control. Is it possible to operate the Labview RealTime system as EtherCAT slave?

    Thanks in advance

     

     

     

    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

  13. Is there a way to "Find Callers" or "Find all Instances" that excludes the instances that are currently in a disabled case of a (conditional) disabled structure?

    What if you use "Get VI Dependencies", with commented diagram disabled, on all VIs.

    post-5958-0-30491400-1429883757.png

    Put each dependency in a variant lookup, and then you should be able to return all callers for a specific VI from the Variant lookup.

    /J

  14. The bad news is lack of documentation makes it difficult.  I tried by taking an existing plugin and modifying it and I didn't get very far.  Even so I think this could be a good tool for quickly turning settings on and off with a simple right click.

     

    The documentation is only bad if you don't go to the original source...

     

    Right clicking to toggle Conditional Symbols would be very nice indeed, but I think one problem would be that the valid range is not specified anywhere.

    The conditional disable symbols only define strings and it is up to the code to handle the correct case etc.

     

    But I guess it would be quite easy to make a project provider that defines valid ranges that could be selected using right-click

     

    /J

  15. No problem, I figured you of all people would be interested and I was hoping you'd see this.  There is plenty of room for improvement but I've been using it without any problems for a while.  I sorta feel bad that I didn't share it sooner.

     

    When we talked about it I had multiple LabVIEW versions installed on my dev machine, but since then I've moved on to use separate VM's for the different LabVIEW versions.

     

    I do still have one laptop with multiple LabVIEW versions, used occasionally for building old SW packages, and this tool is very handy to have.

     

    /J

    • Like 1
  16. I know this is an old thread. 

    But does anyone know what can cause an Asynchronous launched VI to stay running even though the entire code is done?

     

    I ended up just switching back for that particular VI to using Run VI method and that worked.

     

    Thanks,

    Fab

     

    I'm not sure it applies to your problem, but using a Strictly typed Static VI reference as an input the the Open VI reference has been a big problem for me leaving all kind of processes running in the background.

    The workaround has been to replace the Strict VI reference with a strict-constant, and use a non-strict reference to get the VI name/path.

     

    This workaround also applies to Actor Framework since I believe it uses the same design as the OP.

     

    /J

  17. Our data logging engine is based on a timed loop, and the Actual Start left node is used to log the current absolute time. 99% of the time it works perfectly, but once in while it will give the value 11/11/1903  10:57:12.702 PM. Each time it gives an erroneous value, it's this exact value. Has any of you ever seen that? We use LV2011 32bit.

     

    I've never seen the Actual Start return other than a local timer value.

    It should start at 0 (or the offset you specified in the loop setup), then increment with the specified loop delta using the current timing source as timing unit.

     

    How do you do the conversion to an absolute timestamp? Adding timer value to a loop start timestamp?

     

    /J

×
×
  • Create New...

Important Information

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