Jump to content

Antoine Chalons

Members
  • Posts

    854
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by Antoine Chalons

  1. Running on Linux RT with the libpq.so compiled by NI : so they did build the library as thread safe and I get the same on Windows with the libpq dll deployed with the VIP.
  2. I've just pushed new branch to Dr Powell's repo, and built a new version of this package. I used LabVIEW 2017 SP1. What's new : added support for Linux Rt targets (possibly Linux in general but not tested) (issue #1) added support for boolean parameter (issue #2) fix a weakness in parameter detection (issue #3) VIP 0.2.2-b16 can be downloaded from here.
  3. 😮 How many of these are use to control the Large Hadron Collider ? 😄
  4. Very true!! I do use nested combinations of set and map - not hugely deep but it does turn out to be very useful. And yes it might not be trivial to handle ALL possible cases. But let's engineer ambitiously, no?
  5. Would it be possible to add support for maps / sets - as if they were arrays - ? I can really remember if they were added in LV 17 or 18 or 19....
  6. Do you have access to any hardware? "Technical task" is a bit vague... A few years ago I started playing around with https://projecteuler.net/ It was a fun way to practice algorithms with LabVIEW, I think I solved the first 50 or 60. I'm not sure if this is "technical" Any idea on what you like to do? Any special interest? What's your course?
  7. Welcome! What you're looking for is called a shift register : https://www.ni.com/getting-started/labview-basics/shift-registers
  8. You can run multiple instances of the same LabVIEW version by adding the following key in your LabVIEW.ini file AllowMultipleInstances=True I have never tried to have more than one L Instance running the application builder at the same time... Now that I think of if it, I've never even tried to use an instance for coding while another instance is compiling. LabVIEW crashes so well without trying all that... I rarely run multiple instances at the same time anyway. The alternative I can suggest is to use a dedicated build machine (virtual or not depending on you IT infrastructure)
  9. I've just installed the whole LV2020 SP1 env and updated my IC-3173, and now I can't reproduce these issues.
  10. Bug described on NI Forum : https://forums.ni.com/t5/LabVIEW/Map-weirdness-on-Linux-RT/td-p/4114641 With video and code. I would be eternally thankful if anyone could try to reproduce on various Linux RT targets with LabVIEW 2020.
  11. I'm confused... what is the connection between SQLite and PostgreSQL?
  12. Here is a nice one, see my post on NI Forums found in LV2019 SP1, if someone could check LV2020, it would be nice.
  13. My informations from inside NI is that this is largely untrue. NXG team will be re-assigned to other projects and a large part focusing on non-Windows OS support 😮 I don't have much details but different sources corroborate this.
  14. Here is the best I could find : https://forums.ni.com/t5/LabVIEW/Isn-t-it-time-for-LV-2020-SP1/m-p/4108112#M1184087
  15. I think when NIWeek was moved to may instead of august they said the release cycle might change, I think AQ posted something about that on LAVA, can't find it though.
  16. I'm sure you'll get plenty of different opinion on that topic. My rule is to only use SP1 versions for customer release (not sure NI will continue using the 202X and 202X SP1 pattern though). I remember reading a blog post from John Pasquarette in which he described the bi-annual release cycle that started in 2009 but I can't spot the article again.
  17. - I have no idea if what I'm going to say makes sense or not - on Windows the CLFN were all "any thread" and it worked fine.
  18. Ok, it took me some time but in the end, all I had to do to make it work is to set all the CLFNs to run in the UI thread. I'm not a regular user of CLFNs so I'm not sure why and if it was the obvious thing to do but there we are.
  19. It just wasn't installed by default... https://forums.ni.com/t5/NI-Linux-Real-Time-Discussions/LDD-on-NI-Linux-RT/m-p/4111499/thread-id/3368#M3369
  20. It look like ldd should always work... 😢
  21. yeah... well I've tried various different amounts and waited for the full moon but it's still stuck. After doing some digging 9.6 and 9.4 seem to have the same function names and the same arguments for the functions, so now I'm looking at the dependencies. On Windows, Dr Powell includes libeay32.dll, libintl.dll & ssleay32.dll, so now I've got to rabbits to chase : - my Linux RT is 64bit, so could that be an issue - I can't find equivalent *.so file for these 3 dll When I run # opkg depends libpq* I get this And all 3 are installed with correct permissions If anyone has any idea...
  22. Actually - for me - Linux is always a big roadblock 😢 I've taken a similar approach to what you did with SQLite - finding the lib path once at connection, store it in the class private data and setting all the CLFN with a library path input. Of course running that on Windows goes fine, but when trying to run it on a Linux RT target (I have an IC-3173), as soon as the running code gets to a VI that calls the libpq.so.5.7 the execution stops and I get a message that the target was disconnected. I checked the access right for the file /usr/lib/libpq.so.5.7 and they look fine for the account "lvuser" I'm now thinking the issue in libPQ version because I followed this tutorial to install PostgreSQL client on NI Linux RT, it installs version 9.4.17 (latest available on http://download.ni.com/ni-linux-rt/feeds/2019/x64/core2-64/) and the version used in the package is 9.6 How can I install PostgreSQL client 9.6 on NI Linux RT ?
  23. cool, I'm on it. I'll clone your bitbucket repo and create a branch to add RT support. Also, I only have LV2019 SP1, I guess once I'm done someone else can save back to an earlier version.
  24. In reply to Neil's opening, here's my 2 cents about what I suggest NI should do : From what I read in this thread It seems that NI's NXG dev team was made of people who didn't have enough love for LV-CG- or enough experience using LV-CG for real world applications. Well now that NI's plan is to move forward with LabVIEW, my suggestion is that they make every NXG dev spend 50% of their time contributing on LabVIEW related open source project. There's a lot of great project on GitHub, Bitbucket, GitLab, etc. started by passionate LabVIEW users who have the greatness to share their toolkits, frameworks, API, etc. They have limited resources in most cases, so now that NI has a full team of developers with no real purpose and and not enough understanding of what makes LV-CG great, then let's make them contribute to growing the LV-CG eco-system. edit : if you agree >> https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-NXG-dev-team-contribute-to-LV-related-open-source-projects/idi-p/4110996
  25. Actually swiss cheese doesn't have holes, french cheese does. Sometimes proverbs are inaccurate. I'm french.. so no 😉 Lots of white flags in my code 😆
×
×
  • Create New...

Important Information

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