By Yaw Mensah
I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.
My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option.
I will be grateful for any suggestions.
Thank you in advance.
By Shuvankar Das
I want to connect My ccd camera with labview. The details of my system is given bellow. I cannot connect it please help OS: WINDOWS 7, 64bit LabView Run-Time 2013(64-bit) NI-IMAQ 4.8 NI-IMAQdx 4.3 Camera: QICAM Monochrome Cooled (QIC-F-M-12-C) Model QICAM Resolution 1392 x 1040 Sensor 1/2" Sony ICX205 progressive-scan interline CCD Pixel Size 4.65 x 4.65µm Cooling Type Peltier thermoelectric cooling to 25˚C below ambient Digital Output 12 bit Video Output FireWire (IEEE 1394b) Max. Frame Rate 10 fps full resolution @ 12 bits Pixel Scan 20, 10, 5, 2.5MHz Mount Type C-mount optical format
Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
Check it out and let me know what you think 😀
I'm taking the CLA exam in a few weeks and would like some feedback on the solution I put together (attached). A few specific questions:
Can I dump tags in the VI Documentation of the VI like I did in Error Handler - Console Error.vi and get credit since there are instructions for developers to complete this work? This would be my strategy if I run out of time.
Does this seem like a passing solution? Why/why not?
Where do you think I would lose the most points in this solution?
Any other feedback on this exam or general strategy tips are greatly appreciated!
I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020.
For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package. The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included.
However, after I am seeing issues on any PC other than the PC where the package was built.
Is there a setting I am missing?
Showing the (System) package as a dependency:
Package Configuration in the VI Package Configuration Editor
Package installed, on the PC where the package was initially created (no issues, no exclamation mark)
Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).