Jump to content

Porter

Members
  • Content Count

    150
  • Joined

  • Last visited

  • Days Won

    17

Porter last won the day on September 21

Porter had the most liked content!

Community Reputation

41

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,736 profile views
  1. 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.
  2. 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?
  3. I wonder if they will also release a community edition for Linux.
  4. 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?
  5. Its easiest to use VI Package manager. Just search for Modbus, select the package and install.
  6. 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
  7. v1.3.5 has been released: Improved RTU CRC calculation speed Added Slave ID input to "Open TCP Session.vi" Updated documentation
  8. @Masony, something like this?
  9. I thought that it would be nice to extend the muParser library's functionality to include automatic CVT tag lookup. This means that if you input an expression that contains CVT tag names as variables, their values will automatically be substituted during eval. This new CVT expression parser IS AN expression parser. So I tried to make a child of the mupExpr class. Who's silly idea was it to pass this class by reference?! LabVIEW doesn't support dynamic dispatch on class DVRs. So I've re-worked the mupExpr Class to wrap only the muparser handle (hParser) in a DVR. This gives a similar protection as wrapping the class in a DVR but allows us to pass the class by value instead. If anyone objects to this change, please shout out now before I commit changes to github. The code is attached, with an example: NICVT Expression Test.vi You need to install NI Current Value Table v.3.3.0 before opening the project. NICVTExpr.zip
  10. Since your input registers are contiguous, I would suggest reading all of them with one call of read input registers. See attached. Modbus Read Waveform.vi
  11. How much data are you transferring? For example, if you are reading 1000 input registers, one register at a time, then you can't expect to get a sample rate of 100ms. Screenshots or sample code would be useful if you are looking for help. Are you using the Modbus Comm Tester?
  12. Just in case anyone is still interested, the source is now available on github: https://github.com/rfporter/SET-Toolkit
  13. It should show an error on every subsequent read... but it doesn't: It just keeps going as if nothing is wrong.
  14. His code has not fixed the issue yet. It does catch the error, as did Plasmionique Modbus Master, but it is up to you to catch the error and reset the connection. If you don't reset the connection, this can happen: Yikes! No errors being reported and read register 0 is returning the value for register 1. Tanner's proposed fix works. I implemented it in the Plasmionique Modbus Master. With it you can have multiple pending transactions. The responses will be matched up with the requests using the transaction ID. TCP Test.vi
×
×
  • Create New...

Important Information

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