Jump to content

Porter

Members
  • Content Count

    157
  • Joined

  • Last visited

  • Days Won

    17

Porter last won the day on September 21

Porter had the most liked content!

Community Reputation

45

1 Follower

About Porter

  • Rank
    Very Active

Profile Information

  • Gender
    Male
  • Location
    Canada

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2008

Contact Methods

Recent Profile Visitors

2,831 profile views
  1. I'd be happy to work on it in my free time... when I have free time (newborn baby girl waiting for me at home)
  2. It would be nice to be able to modify .mnu palettes with the GCode manager. This way you don't need to add the palette to your palette set just to edit it (as you have to do with the built-in palette editor). Shouldn't be too hard to implement 😜 There is a Palette API that ships with LabVIEW.
  3. Thanks @Michael Aivaliotis for taking the time to do this.
  4. As someone contributing code on LAVA, I would like to see the certified LAVA repository packages made available through the GCentral package search tool.
  5. Be sure to double check the ASCII/RTU mode setting. Make sure that you are specifying the starting address in hex format. The PV value is supposed to be at holding register 0x1000. You could also try increasing the timeout value to 1000 or 2000ms (instead of the default 300ms). A screenshot of the dwyer communication setup and the Plasmionique Modbus Comm Tester setup would be useful.
  6. When you say Love Controller, do you mean a Dwyer "Love" Temperature Controller? They definitely work with this library. For configuring the USB-RS485 adapter, I have never used labview to specify 2-wire or 4-wire mode. That is usually done via hardware (dip-switches or jumpers) or the driver (device manager). I have never used the Tripp-Lite adapter though. I typically use USB-Serial converters from Moxa or Sealevel Systems. They have proven to work very will with labview. If you can provide the model number or user manual of the Love controller, maybe I can give you some example commands to try.
  7. I finally had a moment to take a look at this. Nice job! I particularity like the conditional auto-indexing tunnel vim and the delete elements from array vim. I will have to tell our developers to start moving away from the openG array VIs. Are you going to put this up on github or the NI Tools network?
  8. It is solved now. I unchecked the exclude PPLs and DLLs in the build spec of LF.lvlibp And moved the resulting LF.lvlibp to the same directory as the other PPLs.
  9. I have been transitioning my framework's core libraries to packed project libraries. Unfortunately, the higher level PPLs depend on lower level PPLs, but i think that I've managed to sort out all of the broken connections. Now the issue that is bothering me is that whenever I open a project containing a higher level PPL, I get a bunch of "VI cannot be found on disk errors" that refer to VIs within the higher level PPL. My initial thought was that the file paths were too long, but that doesn't seem to be the case. Has anyone else come across this behavior when using PPLs?
  10. I wonder if they will also release a community edition for Linux.
  11. It would also allow open source developers to maintain their projects after they have changed jobs. I'm glad to hear that NI is moving in this direction. How are they going to prevent companies from just using the community version though?
  12. Its easiest to use VI Package manager. Just search for Modbus, select the package and install.
  13. I would highly recommend that you use one of the existing modbus libraries to communicate with the E5CN. See: OR: https://github.com/NISystemsEngineering/LabVIEW-Modbus-API
  14. v1.3.5 has been released: Improved RTU CRC calculation speed Added Slave ID input to "Open TCP Session.vi" Updated documentation
  15. @Masony, something like this?
×
×
  • Create New...

Important Information

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