Jump to content

eberaud

Members
  • Posts

    297
  • Joined

  • Last visited

  • Days Won

    10

eberaud last won the day on January 25 2022

eberaud had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Riorges, France
  • Interests
    Rock climbing

LabVIEW Information

  • Version
    LabVIEW 2023
  • Since
    2006

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

eberaud's Achievements

  1. My team and I didn't have any of those excuses back in 2012, we were running on Windows only, 'My Computer' target only, and were only dealing with LabVIEW 2011. We were probably guilty of starting coding without a clear enough understanding of how PPL work. We thought we could create a Plugin archiecture based on PPL to avoid having close to a hundred plugins built inside the executable. But this created a 2-way dependency that made this impossible. I later realized that every dependency of the PPL needed to be themselves in PPL, but this felt like a lot of work and we gave up!
  2. And if possible, at each write operation write the same channels, this will prevent the creation of a new segment, as Hooovahh hinted.
  3. You mean you're overlapping the subpanel and the tabcontrol on purpose? This is usually seen as a bad practice. That being said, this is a interesting "bug", I had not seen it before.
  4. There is a section for job postings further down the main page. Please move your post if you can. Thanks!
  5. Can you explain what you mean by "key" in this context? Maybe you can post a little screenshot of the code you have so far?
  6. 5 years later... Have things happened in the recent years with PPLs that would remove some of the reasons people may have abandonned them in the past? I was one of those people back in 2012, I'm thinking that 12 years later I could give them a try again...
  7. Just curious, anyone knows why there are sometimes those shadows around the wires? They seem to disappear when I make a modification to the code, and then reappear after I run the VI.
  8. Only 17 years later 😅 ... Has the situation changed? Or is it still impossible to change the grid size programatically? Thanks!
  9. Thank you Darren, I upgraded to 2023 Q3 and it did fix the issue. I had managed to strip down my code to the point where all I had was one empty class with just a .NET refnum in its private data (System.Windows.Forms.NotyIcon), and only a "DAQmx Start Task.vi" in the startup VI. Same thing was happening if instead of the daqmx VI, my startup VI contained a "XNET Create Session.vi". Any chance you could explain what the issue was? If I removed the .NET refnum or the DAQmx (or XNET) subvi, then it would compile fine. I am attaching a zip file with the files I mentioned and the .lvproj itself (in LV2023Q1) in case somebody want to test it on their own PC (you would need to install DAQmx and/or XNET drivers of course). Anyway, now that this is fixed, I resumed building my whole project and I'm now running into an error 2 "memory is full" 🤯. Cheers, error 13 investigation.zip
  10. it would help a lot if you could post a snapshot of your code
  11. Hexadecimal is just a display representation. At the end of the day, the data in the background is an integer value. So you don't really need to worry about "staying in hex". If you use a combo box, which is purely text, then yes you'll need to choose hex when you convert your numeric values to strings. When the user picks a value you will need to convert back to an integer by telling LabVIEW to interpret the string as hex. What you want to achieve sounds totally doable (and easy).
  12. Hi everyone, I recently installed LabVIEW 2023Q1 and am trying to compile (create an executable of) my company's application, that we can successfully compile with LabVIEW 2019. Unfortunately, at the end of the compilation I get an "error 13" message, just like in this link: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000g34oSAA&l=en-CA However, I don't think it applies to me, since this was supposed to be only in LabVIEW 2017, and that my "Use fast file format" is already disabled anyway. When trying to remove/add back part of my source code, I notice I tend to have problems when I include code that have dependencies inside the new LVAddons folder (C:\Program Files\NI\LVAddons) that NI came up with in LabVIEW 2022Q3 (specifically, xnet and daqmx). Googling specifically for building errors with LVAddons, I came across this issue reported by JKI: https://github.com/vipm-io/vipm-desktop-issues/issues/17 Since it's related to building a package and not an executable, I'm not sure it's relevant for my situation. What makes it hard to troubleshoot is that everything looks happy in the lvproj. All dependencies are found in LVAddons instead of C:\Program Files (x86)\National Instruments\LabVIEW 2023\vi.lib, which seems to match NI's intentions. And the error only occurs at the very end of the compilation. Has anyone encountered this problem while building with either LV2022Q3 or LV2023Q1? I have installed the latest versions of NI-XNET and NI-DAQx drivers (2023Q2). The whole error message is as follows: Error 13 occurred at Invoke Node in AB_Engine_Write_Linker_Wrapper.vi->AB_Build.lvclass:Copy_Files_Core_Old.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller Possible reason(s): LabVIEW: (Hex 0xD) Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format. ========================= LabVIEW: (Hex 0xD) Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format. ========================= Shareable board exclusively owned. Method Name: Linker:Write Info To File
×
×
  • Create New...

Important Information

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