bbean

Does anyone know the status of GPM and/or Gcentral? I went to gpackag.io and website isn't working. last commit here https://gitlab.com/mgi/gpm/gpm was a few years ago

you could try this property saver. its pretty old. See the examples in the palette that gets installed konstantin_shifershteyn_lib_property_saver-1.5.0.4.vip

Hi @drjdpowell, Before I reinvent the wheel, do you have any examples of python modules sending messages to one of your LabVIEW TCP Event Messenger Servers (or a simple UDP Receiver / Sender pair)? I'm interested in extending an existing LabVIEW Messenger Actor to guys on the python side as an API. I'm not sure the best way for them to send message, but a simple one would be to simply send a string with the format (Message Label>>Msg Param1, Msg Param2....)

I didn't see the word "LabVIEW" mentioned in any of those press release. Just seems like Emerson is on a buying spree. Typically this happens at the end of a business cycle when companies (CEOs) run out of ideas for how to improve their business from within. It will be interesting to see how Emerson executes and brings all these acquisitions together under one umbrella and whether LabVIEW has any role.

I want to say I've seen this when one of the modules has gone bad. Have you tried pulling them all out and then installing them one by one to see if one of them causes the problem?

you can already do this in a limited fashion in python. This is a simple example from a single prompt but you can see where its going: https://poe.com/s/BEWvBcTIEkrVXzTezpza The manual was probably online when the model was trained so it already has knowledge of it in this example. But once the size limitations of the text entry increase, you will be able to just upload a manual. And here's a simple refactoring to make an abstract class https://poe.com/s/MJp4t75WVrA5MR5SiS8B I believe the way they work is they are predicting each character on the fly

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.