bbean

sounds like they were too busy updating NI Logo and colors to implement VISA. Oh well.

That seems reasonable. I have a wrapper class and pass back a pass/fail numeric and a status string, but now thinking back it might have been more appropriate to just pass back a standard labview error cluster. In my case, the python wrapper can be run from either LabVIEW or directly in python. The thing i struggle with is passing back real-time status that normally is provided in the terminal via python print statements when python scripts run stand-alone. I'm testing an approach that just sends these via a UDP session but I haven't found a way to override the Python print command so that it prints to both the terminal (python scripts) and to the UDP session (LabVIEW VIs).

What type of instrumentation and data acquisition systems does your lab work with ? Mostly VISA type serial/gpib/LXI instruments or mostly data acquisition cards / PXI chassis type stuff?

This isn't enticing you to upgrade from LV 2009?😀

I would investigate cosmos. I haven't migrated a complete project to it yet but I'm implementing data collection, storage and telemetry GUIs to it for a new project working with python and FPGA programmers. A lot of the python programmers use python and it as a replacement for LabVIEW/TestStand. I haven't used their Script-Runner (TestStand-ish stuff) but the current version is highly capable for data collection, saving, presentation, limit checking. They are working on cosmos 5 which will run in a docker container and have web based gui's

Ok. I misunderstood. But maybe there's something in there that can help. I remember having to do a lot of work arounds with callback VIs to get printing a panel without a prompt for filename to work. Attached is a 2014 version. Win10PrintPDF2014.llb

If you are using Win10 you can try the VI(s) in the attached LLB. We typically create a "print" VI that shows all the controls, decorations logos etc we want to print, then run the VI in this llb. I threw the llb together real quick...hope everything works. Win10PrintPDF.llb

💩

This is a long shot here, but do they all need to run in the UI thread but their preferred execution system is set to "same as caller" and then something gets screwed up when they are called by dynamic dispatch in the runtime? What happens if you set their preferred execution system to "user interface" and retry.

agreed. As part of my trials and tribulations with MAX I had to repair NI VISA. With NIPM18.5? no option to do that so they recommend uninstalling and reinstalling...fair enough. Tried that and NIPM wanted to uninstall LabVIEW..wtf. Upgrading to the latest version of NIPM (19.6) provided a better experience allowing you to repair installs now.

MAX That is all.

Is the latest version 1.10.9.115? Is there another higher version somewhere because that one seems to still have the issue.

Has anyone used IPFS as a tool for storing and distributing test data (multiple gigabytes)? My use case would be to run tests that store data on local windows machines and then distribute that to other users who may have linux, windows etc and also to a centralized archiving location. The users and test machines are in a relatively strict network environment and most users machines are locked down. Some of the linux users may have elevated privileges to install things like ipfs but I'm worried about a typical windows user who may want to get the files easily without having to go through a bunch of command line steps to install ipfs on there machine after requesting elevated privileges.

Thanks for the quick response. its a rather annoying problem. I think this may have been the problem but wont know until I test again on Monday. You are correct that its a PM320E. And so far their driver has been a pain. The suspect command is the error query the parent class implements by default "SYST:ERR?" but PM320E requires ":SYST:ERR?". A nuance (nuisance) that I failed to notice. PS. I think I may have borked the instrument up by upgrading the firmware too. Oh well thats what you get for trying to get something done before a holiday weekend.

I have an issue where reading the VISA Instr Property "Intf Type" of a USB Instrument hangs for about 40 secs: followed by an asynchronous VISA Write hang for 2+ minutes! The timeout on the VISA instr session is set to 1000ms. Here are the other details of the session: and here's a snip of the VI: Any idea why these long timeouts are occurring? or why the 1000ms timeout is being violated for both the Instr property call (no idea what goes on under the hood here) or the VISA write.

If that doesn't work you may have to separate the TestStandAPI calls out. Are you using your TestStand Actor as a GUI or user interface? If so you may have to create another Actor to separate out the TestStand API calls that are causing the log jam into a new Actor....That new actor should not have any property/invoke nodes which would force its VI into the UI thread.

I would imagine the string 127.0.0.1 (or u32 Net Address 2130706433)

I worked on some Ethercat issue a few years back and remember that at the time the cRIO doesn't support Beckhoff array datatypes and we had to make individual IO variables for each item in the array on the Beckhoff side. Were you able to import the XML file OK into the LabVIEW project?

never mind. found a work around to my problem. I was getting runtime errors whenever I saved my VI with the activex control saying the control doesn't support persistence. I fixed by saving a null variant to a connection property before exiting the vi and the problem went away

Did you have any luck with solving this issue? I'd like to do the same thing.

Curious how your company worked or works out the OS licensing. I tried to go down this rabbit hole with MS a couple of years ago and ended up giving up because it was so difficult to figure out for a small business.

Yeah I could see that being helpful at some point. What happens when you have more than one primitive/Subvi on the diagram in the node? Does it just place another entry at the bottom of the unbundle?

If you don't need to do FPGA image processing, I would explore the other options for Camera Link cards that are not FPGA based and see if they will work with Pharlap With regards to the FPGA example, this may be a long shot If you haven't compiled FPGA code and I'm not sure it will work at all. I don't have time right now to fully explain but to summarize: Open the example 1477 getting started project Save a copy of the project and all VIs to a new location (so you don't overwrite the working windows target version from NI) Close the off the shelf example project Open the copy project Create a new RT target in the project (right click on project in project tree, select new targets and devices, select RT desktop Move the FPGA Target from the Windows Target to the RT Desktop target Move the Host VI from the windows target to the RT target Compile the FPGA target VI Open the Host VI (now in the realtime target) and reconfigure the Open FGPA reference to point to the new compiled FPGA VI.

I guess I would need to know about your requirements, but I think that would be a road less traveled. Do you need base, medium, full or extended full? do you need power over camera link? etc. Why do you need real-time? In the future I would recommend talking with Robert Eastland and purchasing all your vision related hardware /software from Graftek. He has been extremely helpful with me in the past and knows his stuff. I have no affiliation with the company. Did you try my suggestion to compile the example FPGA code and move the host example to the real-time target to see if its even a possibility?

Unfortunately, the card probably does not work directly in LabVIEW Realtime. NI's specifications and documentation are often vague with hidden gotchas. I had a similar problem with an NI-serial card years ago when Real-time and FPGA first debuted. I wanted to use the serial card directly in LabVIEW real-time with VISA, but I ended up having to code a serial FPGA program on the card because VISA did not recognize it as a serial port early on. Is there anyway you can try to compile the FPGA example and download it to the card? C:\Program Files (x86)\National Instruments\LabVIEW 2018\examples\Vision-RIO\PCIe-1477\PCIe-1477 Getting Started\PCIe-1477 Getting Started.lvproj After you compile and download the FPGA code to the 1477, I think you would have to move "PCIe-1477 Getting Started\Getting Started (Host).vi" from windows target to the Real-time target, open it up and see if it can be run.