Neil Pate

Not seen the banner at all since you did the switch, so it seems to be working. Thank you

Sorry, I know way too little about the subtleties of PPLs! The only other thing I can think of is making sure the class is being loaded from the right place on disk. From your screenshot you have a bit of the path in the first dialogue can you try figure out the whole path and then pass it to the Get Default Class VI (or something like that, I am not at my PC).

The error probably goes away in your last scenario as dropping the class constant onto the block diagram causes the LabVIEW compiler to automatically include that class in the build. This kind of thing happens all the time with factory pattern type stuff in LabVIEW, where everything works perfectly in the IDE because all the classes are in memory. If that is the problem you can solve it in a number of ways, one of the easiest I have found is to make a dummy VI that you can then include in the build or place somewhere on your top level VI, in this VI just drop down all the class constants of the classes you are using. The kinda breaks the lazy loading paradigm, but you win some you lose some. Just as a side note, I avoid PPLs like the plague as I just cannot see a good use case for them for "normal" applications. The sheer number of problems that arise with PPLs have caused me to put them in the same category as Shared Variables; nice in principle but never to actually be relied upon...

Thanks Michael. I have not seen it today 😁

So out of curiosity, how does everyone else handle their name generation? Multiple cameras with multiple image processing steps each needing temporary storage. I usually try and programitically generate the name but now that I think about this thread there must be a better way that I don't know about.

Anyone else still getting the green wiki banner at the top? I must have dismissed this about 100 times if not more but it keeps coming back. This is on mobile Chrome but I am pretty sure I see it on desktop Chrome too.

Wow that sounds pretty rubbish! I have never really gotten to the point where I have said yup I totally understand this API.

The one thing that always confused me was writing the actual image to the terminal. If it was purely reference based there would be no need to sequence it as I have done it in my demo. The indicator gets updated when the same actual data value hits it, which is a bit unreference like (maybe...). As Rolf says, a strange duck. This does help me know what happens if for example I broadcast an Image reference on a user event. No data copy of the whole image occurs, and if I do stuff to ref coming out the receiving event it might effect my original image, it is not a copy.

I have used Vision on and off for several years and never really grokked the subtleties of IMAQimage references and what they actually represent. Now using strings instead this all just clicks into place for me.

this is the external DVR I was talking about

Hi Tuan, I would be a bit surprised if you could write to disk at 3.2 GB/s for any reasonable length of time even with a fast SSD. You say longer than 10s, how much longer? If you can buffer in memory all your data you could stream to disk as needed at a slower rate. Something I came across recently which I was surprised even existed, is a feature where an FPGA can use a DMA FIFO transfer to write directly to a TDMS file using a kind-of DVR (external DVR perhaps). Not sure if your hardware supports that but it might help with performance.

They are just the dialogues indicating what is happening, no user interaction is required. The first dialogue is Package Manager and the next one is all the RTE stuff.

I have a legacy application I am updating to use LV2019. It has an installer for the application which installs the run-time engine and the application itself (and a bunch of other stuff). This is done using InnoSetup and not NI's installer creator. Previously, I was able to run the RTE install in totally silent mode where no popups or anything came up on the screen, I would like to do the same thing but cannot use the same parameters as 2019 uses the new NIPM format. I can get the installer to run through from start to finish with no user interaction using: install.exe --passive --accept-eulas --prevent-reboot However during install it pops up its own dialogue. Does anyone know how I can suppress this dialogue?

Indeed. In my circumstance though, I don't really care too much for the output, I have some downstream code that waits a bit and checks for correct generation of a PDF file I am creating.

@Brainiac did you solve this in the end? The code below shows how I do it, this works completely fine for me on Windows 7..10. The Generation Batch File is the complete path on disk, I don't use the Working Directory input.

Now that you mention it, I recall a work around I had to put in place some time ago on a touch screen only application. Sometimes my custom dialogs got hidden behind the main panel, the way we solved it in the end (ugly but worked), was just to periodically force all the dialogs to be on top. Each dialogue type actor was responsible for getting itself on top. Not pretty...

James, not exactly solving your problem, but... What I usually do is only make the dialogs modal during exe building (i.e. set their FP property in the build only). This prevents the issue of things being hidden behind other things and locking the developer out of LabVIEW.

Looks like you might have a space between the \ and the c in your string

The DMA FIFO is silly fast if configured correctly. I have used it in a VST to losslessly stream (continuously for tens of hours) something on the order of several GB/s to disk. That was using PXI, and not myRIO though. Don't forget, the host (RT) is actually the place where data gets buffered, and this is where you can make a nice big buffer. You don't really need a big buffer on the FPGA, you just need to make sure you read from the host buffer fast enough. As Tim_S said, do the trick where you read zero samples, this will return no data but will give you the number of samples actually available.

Thank you, I will give this a try.

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?

You can programmatically colour decorations. The tricky bit is getting a reference to them, as you cannot just look them up by name. What you can do though is figure out their UID and then operate on them by using this number. Whatever you do, don't be tempted to access them via their index position in the Decorations array, the order frequently changes and will cause very subtle coloring bugs in your code!

Thanks Tim, the problem is I cannot even install the stuff in the first place! NI Package Manager is not my favourite piece of software at the moment...

Some good stuff there, $15 gets you everything. https://www.humblebundle.com/books/data-analysis-machine-learning-books?partner=gamefromscratch

I really am not a fan of the new NI Package Manager. Having so much drama with it across multiple computers. Cannot install the Vision Development Module 2019, the installer just closes soon after starting, no error messages or anything. Staring Package Manager directly gives this error: Anybody else having issues?