Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


ensegre last won the day on March 27

ensegre had the most liked content!


Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since

Recent Profile Visitors

7,706 profile views

ensegre's Achievements

  1. Frankly, It seems more that you don't know what you want, than that you don't know how to do it on a FPGA.
  2. I don't know exactly how your collection looks like and in what the NI Web Server as it is fills in, but as for linux and serving http I have been positively impressed by this: https://github.com/illuminated-g/lv-http-server In fact I did some preliminary evaluation of it some time ago, and I was planning to build on it for a project which has been delayed. If you look into, I'd be interested in hearing your opinion as well.
  3. your attachment links are broken, could you see if you can correct them?
  4. For my experience, when it is about lab equipment, each device comes along with its own serial communication command set, if not all together proprietary handling dll. Which creates a job case for a lab automation integrator like I act for, many times. Industry standard bus protocols are implemented only in devices which scale to factory floor. Robotic components, generic remote i/o and plant controllers are the exceptions which come to my mind, as they cater to the generic PLC ecosystem.
  5. When I tooled with programmatic generation of EIOnodes (not that this makes me an expert of them, nor that I remember too much of my trials and errors of then), I got the impression that the little set of EIO scripting VIs is all but complete and bug free, less to say documented. To understand the state cluster was way too esoteric for me, and I wasn't able to use AddChannel. In the end I achieved what I wanted by using ModifyChannels and SpecifyEIONode. Even with that the result was not yet sane, and cherry on the cream, the trick to fix up things automagically was to cut all I created and repaste it on the BD. Meaning to me, that to complete the operation the necessary methods are not exposed in the undocumented set given, but luckily some internal sanity cleanup is enforced when dropping clipboard contents. Maybe my task was easier, because I knew a priori the type of the terminal I wanted to connect to (i.e. U8 or int16 or boolean, determined by the name itself), so I only had to wire a control or an indicator of the right type to the node I created, and not to find out that type.
  6. Oh, thx for the insider information. So there has been a quick followup, comforting to know.
  7. Could someone kindly check and confirm this bug on some other installation? I'm having hard time convincing the correspondent Technical_Support_Engineer_NI_is_now_part_of_Emerson that the bug is reproducible (it is for me on two different Ubuntu 20.04). Subbug 1: (happens with any LV version I tried) cd ~/natinst/LabVIEW\ Data/Shared\ Library/ rm HeaderParserResult.xml touch HeaderParserResult.xml labview64 --> select Tools/Import/Shared Library (.so) --> SIGSEGV Subbug 2: (happens with LV2023Q3f0 and f1) copy the attached file in ~/natinst/LabVIEW\ Data/Shared\ Library/ (to save you from doing the process from scratch) mkdir /tmp/LVimport labview64 --> select Tools/Import/Shared Library (.so) --> Update VIs --> Next --> Next --> ... --> SIGSEGV HeaderParserResult.xml
  8. For the record (self note?) Narrowing down with some more use of ddd. It seems that there is a bug in 2023Q3 at the stage of the generation of the library. There is a segmentation fault in HEADER_PMSave () from /usr/local/natinst/LabVIEW-2023-64/resource/headerparser.so apparently when calling xercesc_3_2::IconvGNULCPTranscoder::transcode(char const*, char16_t*, unsigned long, xercesc_3_2::MemoryManager*) () from /usr/local/natinst/LabVIEW-2023-64/resource/libnixerces.so.3 which produces an empty file /home/xxxx/natinst/LabVIEW\ Data/Shared\ Library/HeaderParserResult.xml. Once that empty file is created, any other version of labview will segfault when attempting to start the Import wizard. Removing that file allows earlier version of LV to complete the import process. Now if I would understand in which status we are under our SSP, Emerson, SAS transition or whatever I could report it as a bug, and get perhaps a CAR... Btw, when the empty xml is present, the crash occurs, in 2023Q3, at the 12th call of xercesc_3_2::XMLString::transcode(char16_t const*, xercesc_3_2::MemoryManager*) () from /usr/local/natinst/LabVIEW-2023-64/resource/libnixerces.so.3 within HEADER_ProjectManagementInitialize () from /usr/local/natinst/LabVIEW-2023-64/resource/headerparser.so
  9. Maybe I wasn't clear enough: replacing Compound arithmetic +++ with Multiply x3 in my BD I did get the same timing (in contrast with Mads), whereas using CompoundArithmetic x3 I got 10ms more. And now to further elaborate I put several variants of the x3 in a Diagram Disable, and surprise, times become ~150ms for all variants but ~144ms for Multiply x3. But back on demo2,vi, I also now get ~150ms instead of ~120. Say compiler optimizations, cache, or I don't know what. Formally you're right, but in this case I observed no difference - I guess the gettick gets executed as soon as possible when entering the frame, and on my system that's early enough, even if not guaranteed to be the first operation demo2+.vi
  10. I don't want to be picky, but with that solution I get the same ~117ms with compound +++, twice + x3 and 3x, whereas ~127ms with compound arithmetic 3x or x3. Platform and optimizations 🤷‍♂️
  11. in my case I don't see appreciable differences between x3 and compound +++. Maybe there is something platform dependent, if at all.
  12. Indeed, it is buffer preallocation what makes the difference. In my first solution I presume that the compiler is implicitly allocating the output buffer, knowing N and the sizes of the input. Shaun's solution beats all because is in place and the allocation of the input is not accounted for, but destroys the original input. demo3.vi
  13. This is about three times faster for me: demo2.vi
  14. I'm getting immediate segmentation faults when trying to run the import .so wizard, on an ubuntu 20 machine where I have installed LV14, 19, 2021 and 2023 (up to date). All versions of LV appear to behave normally during my usual workflow, but now crash immediately after choosing Tools/Import Shared Library, and displaying the first window of the wizard. I tried to launch LV through ddd, and the only hint I'm able to get is that there is a segmentation fault in early /usr/local/natinst/LabVIEW-XX/resource/headerparser.so. I've tried different versions, running LV as root, clearing cache at no avail. Only a couple of times I was able to go through the dialogs the wizard down to the point of starting the compilation (after choosing .so, .h, include dir, functions to wrap, arg types), but since then not again. Any idea about what could be wrong and how could I debug further?
  • Create New...

Important Information

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