Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Porter last won the day on March 16 2021

Porter had the most liked content!

Profile Information

  • Gender
  • Location

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Contact Methods

Recent Profile Visitors

5,891 profile views

Porter's Achievements

  1. That's what I was thinking. Thanks for the clarification.
  2. It seems that there are now two forks of the erdosmiller TOML library: https://github.com/AntoineChalons/lv-toml https://github.com/justiceb/BlueTOMLSerializer @bjustice is the BlueTOML a fork of the original erdosmiller library or of Antoine's library?
  3. Anything else that should be VIMed? Median, mode, standard deviation? Everything NI_GMath and NI_AALbase please. They greatly impact application build time.
  4. I couldn't get it to return a non-zero error code. I tried Inf and NaN in the array. Dividing once for each element feels expensive. It doesn't seem like lvanlys uses it either. Both the native "dumb" mean algorithm and lvanlys overflow around the same value. Whereas a divide at each element algorithm can handle higher values. Mean Value Test.vi
  5. I'm just going to throw this out there... LabVIEW's included mean value of array function calls and external dll (lvanlys). It takes close to twice as long (depending on array size) to execute than just doing a native sum of array elements then divide by array size. Is there any advantage that the lvanlys function has over this simple native mean? Why aren't most of the lvanlys functions implemented as native LV code instead of a dll? I'd imagine that we could get some performance boost on some of them by using inlining, VIMs, and parallelized loops. Mean Value Test.vi Mean Value Test SGL.vi
  6. I've been using Synology at work for about 6 years and at home now for 2 years. Although the initial price tag seems high, the amount of time you save in setup and maintenance (vs my old open media vault setup) pays for itself. I also set it up in RAID5. I've had 1 disk fail, I was notified right away and was able to replace it with no downtime or data loss. The Synology's collection of apps for small business are quite powerful, allowing easy setup of automated snapshots, backups, remote backups (and recovery). You can even set it up to be a domain controller. Hopefully Open Media Vault will someday fully embrace BTRFS and integrate its setup and maintenance into the web UI. But until then, I'm sticking with Synology.
  7. Glad to hear that a new converter did the trick. I can remember having an issue like that a long time ago and it was due to incompatible hardware. The main reason why I don't like the synchronous mode is because it allows only one serial read at a time, across the entire system. So for a system with multiple serial ports, you can only poll them one at a time. I recall being very confused when using the old NI Modbus code and watching the status LEDs on our multi-port USB-Serial converter light up sequentially. It had a very detrimental impact on the performance of the system.
  8. That's the first time I've heard of such a problem. I'm reluctant to implement this because from experience, synchronous R/W usually causes more problems that it solves. Would you be willing to privately share the code with me? What kind of serial port are you using? Can you try using a FTDI-based USB-Serial converter to see if you get the same behavior? Other USB-serial converters that perform well with VISA are: https://www.sealevel.com/product/2105r-usb-to-1-port-rs-232-db9-serial-interface-adapter/ https://www.moxa.com/en/products/industrial-edge-connectivity/usb-to-serial-converters-usb-hubs/usb-to-serial-converters/uport-1100-series/uport-1150
  9. Hello Paolo, Since you will be using Modbus RTU (over serial port) you would probably want to modify the "RX MEI Data.vi" in the MB_ADU_RTU class to have some logic to determine the end of the response message. Otherwise the default behavior is to wait 200ms and assume that the entire message has been received during that time. If you are OK with the 200ms wait time, then you don't need to modify anything here. Next you would want to call the "Querry.vi" from MB_Master_Serial class with function code set to 43, and the first data byte set to 13. Note that if you do modify "RX MEI Data.vi" you can use the RTU_DataBytes parameter to tell it how many bytes to expect to receive if you are able to know this before calling Querry.
  10. A nice feature would be to optionally preserve top-level comments (lines that start with #). I don't think that this is a trivial to implement, but it could be useful. And it might even be simple to preserve inline comments while we're at it (keep the comment with the key-value pair).
  11. Thanks Antoine for taking on this project. Looks like you are making some good progress already. Just a little detail, you might want to add some text at the top of the license file along the lines of: Contributions up to v1.2.1 Copyright (c) 2017, Erdos Miller Unless you received written permission to from the original owner to change the copyright.
  12. I've been toying with the idea of implementing a new TOML library for LabVIEW. I've been using OpenG variant config for years, but I would prefer to use a more standardized format for my ini config files. TOML is the best candidate for this. Erdosmiller's library is pretty good, but as the author points out, it is no longer maintained, and it didn't gracefully handle all of the datatypes that I wanted to use. It would be great to have the flexibility of jsontext but for TOML format. I'll post back here if I manage to get the project off the ground.
  13. Thanks Darin for hitting the nail on the head. Always Copy was the first thing that came to mind when looking for a workaround, but muscle memory brought me to IPES first (which does the same thing if I recall correctly). For completeness, I have added Always Copy to Loop5 of my test vi. It solves the problem nicely: Destroyed Event Ref Test_loop5.vi
  14. Porter

    Dear NI

    - LVCompare and LVMerge should be unlocked with the LabVIEW base edition. Or even better, an open source merge and compare tool could be released to the community.
  15. I think that I've encountered a bug in the behavior of Not a Number/Path/Refnum? when checking an array of event references within a loop. *LabVIEW 19.0.1f3, 32-bit, Win10* I would expect Loop1 (below) to stop within 6-7ms, however it is consistently timing out (>500ms). The result of the Not a Number/Path/Refnum? is always false even though the event refs are no longer valid. I suspect that this is related to compiler optimization because adding an in-place structure results in the correct behavior. So is this actually a bug? or should the need for an in-place structure be expected for some reason? Here is my test VI (LabVIEW 2019) to demonstrate this behavior: Destroyed Event Ref Test.vi
  • Create New...

Important Information

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