Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Hi, Explanation from NI website: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KZNSA2&l=en-IL Regards, Joseph.
  3. Hi, I found a solution: when using Labview 32 bit I get the error :-41106 If I open the same .vi with labview 64 bit i don't get the error anymore. it seem to be an error using different format system (32bit and 64bit together). so I renew my question: How can I run vi running with labview 32 bit and Office 64 bit ? Regards, Joseph.
  4. When reading data from excel file with labview 2017 (32bit) I get the error code: Error -41106. Week ago everything worked properly. I uninstall and install Office again. what can I do to make it work again? Regards, Joseph. Windows 10 Home Excel Version: 2016 MSO (16.0.11901.20170) 64bit Labview 2017 32 bit Untitled 1.vi
  5. Yesterday
  6. Last week
  7. DVRs can be upcast and downcast with To More Generic and To More Specific. So if you have a public type that is the ancestor of the private one, you can upcast to the public one in public and then downcast when you need to actually use it. That's all completely type safe. (Note: DVR of LabVIEW Object works without you having to create a new ancestor class.)
  8. The instructions in KERNEL_SOURCE.txt are pretty good and work well for me. I use a Ubuntu 18.04 VM for cross-compiling, I would suggest at least 70 GB hard drive space. More help can be found here: https://forums.ni.com/t5/NI-Linux-Real-Time/ct-p/7013 And you can watch this if you'd like:
  9. Why would you want to do that? Compiling a Linux image for embedded hardware is not a trivial feat. Yes NI does provide the scripts that are necessary to do that but you also need to have the perfectly setup development system with the right version of gcc toolchain to even hope to get that working seemlessly. Even slight version differences can mean that you might have to edit scripts and all and such edits are really not for the faint at heart. You need a very deep knowledge into Linux in general and especially embedded kernel compiling of Linux in order to hope that your edits will cause anything else than more errors. Googling with errors is in these cases usually also not a solution because you mostly find only answers from other noobs who have no idea what they are doing and just post random recommendations.
  10. Wow, conditional auto-indexing in loops has been around since Labview 2012? How the heck did I not notice this?
  11. Which kind-hearted person can give you some advice: How to recompile an image that can run on ZYNQ according to the LINUX RT source code on GITHUB? The links are as follows: Https://github.com/ni/nilrt/tree/nilrt/15.0
  12. I wouldn't do this. Its probably ok in this limited case, but its possible to make labview crash in this way. A better route is the variant, which has the same capabilities (cast to an opaque untyped blob and back again) but without the danger.
  13. Even as a pointer, that wouldn't work in C++. Any use of the type in a public signature must be public, even by pointer, even by reference.
  14. I am trying to generate arbitrary pulses from keithley 2614B SMU. I downloaded driver files from keithley website and added to the labview drivers, but the there were multiple VI files and no files to generate pulse pulse voltage and measure current. Do i need to use these driver files to create a new program or shall i can use the same driver file to generate pulse. If any of you are having VI files for pulse generation in 2614B please attach it here.
  15. Hi, You can actually typecast your DVR reference to U32 value (pointer) and back. You can store this U32 number in a helper class, that will represent your API. Or, if you decide to go with a helper API class, then you actually don't need to typecast it to U32 - just store the DVR inside the public API helper class:
  16. Just to say that I have also had the same issue for quite some time. Several months ago I sent a message using the Contact Us link at the bottom of the website, but have not had a response.
  17. Thx for your sharing sir! But at my current project, I got the a EXE file, and I would write some commands after i execute it, and i can't finished it with SYSTEM Exec or your tool, could you pls help me to figure out it ? the yellow part below are the commands, thx again! D:\DESKTOP\VIG\BLE>BLE_GET_RSSI.exe Loading... <<READY>> Connect FDB06556E922 <<READY>> 7C1ABEE86B33 Connectng Connecting to FDB06556E922, Device name: VIG2_BLE_FDB06556E922 Connected to FDB06556E922 Discover Complete SEND VIG_BYPASS TX: VIG_BYPASS <<READY>> RX: MAC CHK OK SEND soc_ver? TX: soc_ver? <<READY>> RX: 0.762 quit D:\DESKTOP\VIG\BLE>
  18. I found a post with the exact same error codes: https://forums.ni.com/t5/SystemLink/Package-deployment-failed-through-SystemLink/td-p/3839425 (Google had exactly 1 hit on ni.com) JoshuaP suggests installing ni-certificates first. (His solution is for SystemLink rather than NIPM, so I'm not sure how applicable it is to your case)
  19. Getting absoerrorlog.txtlutely nowhere with this. Reinstalled my OS, managed to install LV2019, now cannot install any RT stuff. Package managed is choking on NI-Serial. ===== 2019-Aug-12 22:44:11.734283 ===== Exception in ni::pkgclient::TransactionBase::StartInternal. Error code: -125083 Request type: 30 -125083: An error occurred while installing a package: ni-serial-runtime (19.0.0.49152-0+f0) File: source\nipkg_client\pkgclient\PluginInteraction.cpp Line number: 237 Additional error information: -125530: An error occurred while installing the MSI at 'serialRuntime64.msi'. File: p:\AST\PackageManagement\components\nipkg\trunk\19.0\source\shared_agents\WinInstall/ErrorHandler/ErrorInfo.h Line number: 111 Anybody know what these error codes mean?
  20. Earlier
  21. Rather than have a bunch of links floating around, I'm creating this "one stop shop" for my contributions to the LabVIEW community. This is my Cilino Suite aka "C Suite". Presentations My YouTube Channel of Presentations (bit.ly/ChrisCilino_Presentations) including: My LabVIEW Champion Interview NIWeek 2018 Keynote Presentation Soliton Customer Testimonial LabVIEW Architect's Forum Q3 2018 - LabVIEW Auto Documentation Software LabVIEW Architect's Forum Q4 2016 - Automated Build Process 2018 Certified LabVIEW Architect Summit - Everything a Software Engineer Needs to Know That Has Nothing to Do with Software Engineering My First Keynote Presentation at VIP Days in Germany Code - Reuse Libraries Automated Build System - Software Module Builder Summary: A system that turns source into exports. The exports can be of any type. Also determines build order of hierarchical modules, updates dependencies, and allows you to move the exports to the location you need for your end users to find and install the export and its dependencies. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/software-module-builder.git Dependencies LabVIEW Container (see link below) LabVIEW SCC API Summary: An API designed to abstract server based source code control providers. BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-scc-api.git Distributed as a part of the Automated Build system NI Package Manager Build Spec API Summary: An API to programmatically interact with and edit the LabVIEW NI Package Build Specification. BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/ni-package-manager-api.git Distributed as a part of the Automated Build system Software Module Template - NIPKG and VIP Summary: A template LabVIEW Project designed to be built into an NI Package and VI Package by the Software Module Builder (see above). With this template, a user need only put their code in the "source" directory and edit some build specification information and the build process will do the rest. Distributed with the Software Module Builder BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/software-module-template-nipkg-vip.git Watchdog Framework Summary: A software observer of "situations" that can notify when something of "interest" happens. The observer is the "WatchDog", the thing being observed is a "Perpetrator", and the notification is a "bark". Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-watchdog-framework.git Sequencer Summary: A simple design pattern that organizes code on a single block diagram without the inappropriate/excessive use of subVIs. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/sequencer-pattern.git Auto Documentation Summary: Think of this as Doxogen for LabVIEW. Given a Project, Lvlib or .class, this software generates report. The report is "printed" to a confluence page. The software is Object Oriented and designed to be extended through inheritance. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-auto-documentation.git Dependencies LabVIEW Atlassian / Confluence / Jira APIs Summary: An API that allows you to control Atlassian assets such as Confluence and JIRA from LabVIEW BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-atlassian-api.git LabVIEW Container Summary: A dynamic data structure that combines the strengths of a cluster and an array. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-container.git Custom Install Step Launcher Summary: Enables NI Package Manager to execute VIs as a Post-Install/Post-Install All/Pre-Uninstall action. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/custom-install-step-launcher.git History/Credentials/Social Media LabVIEW Champion Page LinkedIn LabVIEW Champion Badge Certified LabVIEW Architect Badge Twitter NI.com Profile
  22. Doing a quick search, C++ doesn't permit access scope for the class itself -- only at the member level. In other words the class itself is always public
  23. Raw TCP. Make your application respond to SCPI commands and the other engineer can treat it like any other instrument. Can even be over a network (remote). It's a simple method which is programming language independent and can be added to existing applications without much problem. Also has no additional installation or distribution requirements.
  24. Hi Francois, I was seeing the DVR more like a 'pointer' (the address in memory) on the class, not a representation of the class itself. To me, if it is really a pointer, and the variable containing the pointer is public, I should be able to access the pointer everywhere. But of course, I wouldn't be able to use what's pointed (because it is private). This is the way I was seing this, I am maybe far away from the truth 🙂 Anyway, I wonder if it is the same behavior in C++ (or other OO language using pointers).... For the 'interface' part of the problem, yes the lvclass is a lib. But I guess that originally, the code was designed to allow building a PPL. So I guess that's why the interface is in a LVLIB and it contains the lvclass.
  25. DLL functions or shared variables? Or something else? I have a Labview 2014-64 executable (or I can build a DLL) that runs one piece of equipment, the X-ray. The other engineer has a large CVI Labwindows 2015 + MS Visual Studio 2012 (C++) executable that runs everything else. I want the Labview code to be a slave of the CVI code, accepting commands to turn X-ray On or Off, reporting failures, and the like. Translating the X-ray code into C++ would be possible in principle, but not fun. Shared variables look easy, but I'm kinda scared of them. I would define all the shared variables in my LV code, since I'm more familiar with LV, then use them in both. There's a thread in here called "Shared Variable Woes" so maybe I should be scared. In the alternative, I tried building a proof-of-concept DLL in Labview, and calling its functions in CVI/C++, and it works, but it's kinda clunky. (I'm attaching it below in case you want to play, or advise.) Your advice would be appreciated. XrayDLL.zip
  26. @hooovahh is right, this is not doable. Your executable doesn't contain the source code and without the source code you cannot compile the application. If the source code is lost, you can either re-program the application (probably very costly) or convince your IT department to allow installing the LV2009 RTE for this particular executable. That said, it is possible to copy the executable and the entire RTE to the target computer manually, for example as part of the "installer" for your executable (IT department mustn't know 😉). We have done so in the past (for the same reasons) and it works like a charm. Of course, this only works for utility applications. It doesn't work if your application depends on other drivers like VISA and the like. If this is not a problem for you, just copy the RTE folder from the NI installation directory ".\Shared\LabVIEW Run-Time\2009", put your executable inside and be happy. I just ran your application on a clean Windows 10 virtual machine and it starts without errors and terminates after a few seconds. It's worth a try in my opinion.
  27. No you can't do what you are asking. There are a few things you might want to know, but none will totally fix your situation. Starting in LabVIEW 2017 there is a forward compatible runtime engine. Meaning binaries build in LabVIEW 2017 can be ran in the 2018 or newer runtime engine. When you build a EXE there is an option to force it to run in that one version of LabVIEW, or the newest one installed. Then if you wanted to run a new version all you'd need to do is install the new RTE and it would run in that. Obviously that is a relatively new feature and not going to be useful for you now. Also there is the fact that LabVIEW 2009 while not official supported in Windows 10 will most likely run just fine. I've installed LabVIEW 7.1 in Windows 7 and had no issues, other than tracking down old drivers to support it. So you might be able to convince your IT team that the 2009 RTE should be used. Without the source that really is the only way to run that EXE. The binary is compiled for that RTE and can't be recompiled for another target or platform unless you have the source.
  1. Load more activity
×
×
  • Create New...

Important Information

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