Neil Pate

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?

Drat, still not having any luck with this. I am going to see if this works in a VM.

Hmmm. I wonder which part of "offline" is not clear?

Thanks! I did actually click there but thought it was just for patches.

Can anybody point me in the direction of the offline installers for 2019 (+toolkits/drivers for FPGA and RT). I can only find the 3.5 MB web installer for pretty much anything.

Thanks!

The difference in the Value output type can be caused by the mechanical switching mechanism that is configured on the boolean.

I don't have LabVIEW on the PC I am on now and I can never remember their names properly, but only the top row of the mechanical switching mechanism will give you green boolean value.

Can you show us what the control on the sub VI is please. Also the Context Help window might provide some insight into why this wire is broken.

There is no need for the timed loop as the DAQ itself has a timing source. Just use a regular loop and ask the DAQ for a certain number of samples. This will accurately fix the loop rate.

Also, to get up and running just try using a regular queue. Although you need to be a bit more careful on RT there is no good reason they will not work unless you really need to get every last ounce of performance from the system. I have never been a fan of shared variables, too much "magic" going on behind the scenes for my liking.

A Radio-button has a natural interlock mechanism. You can customise the booleans to be regular buttons and also change their positions to get a 2D grid type feel if that is what you want.

7 hours ago, ShaunR said:

When I wrote Passa Mak I went through all this. It replaces Captions and Tip Strips and anything else that has a text property on-the-fly but  the inevitable support required to allow people to use languages like Japanese or Chinese was just rediculous-so I didn't.

The real problem was filenames, though. How did you resolve that?

I did not try and translate any filenames. Only strings, numerics and booleans.  

11 hours ago, ShaunR said:

You can get it to display Japanese under certain conditions (ini setting and Force Uncode Text on the control) but it is permanently "stuck" so you end up with spaces between chars for ascii. 

I have blocked out those painful memories...I did eventually get something working which is robust, but if I recall it was pretty ropey until it worked properly (lots of weirdness...).

1 hour ago, ShaunR said:

If you want to display Japanese, you cannot on an English version of Windows - you just get question marks.

Not true at all. I have an application I developed that includes on the fly translation to pretty much any predefined language using UTF8 string lookup files. It works fine on my English language Windows (developed on Win 7, works fine on Win 10).

Obviously you need to have the correct language packs installed in order to get the fonts.

Picture is a snippet from one of the translation files.

1 hour ago, ShaunR said:

What we can't do, currently, is display it on non, language specific OSs.

What do you mean by this?

39 minutes ago, ShaunR said:

I've just spent a month writing two xcontrols

Wow, that is keen!

On 4/9/2019 at 1:22 AM, flarn2006 said:

Also wtf, those six characters in the screenshot filename just came from an RNG

🤣 sounds like a cash converter service...

I had a real struggle with some USB3.0 cameras and a Windows 10 PC. They were Basler cameras, and even Windows device manager sometimes did not pick them up. They would regularly just "not appear" in MAX. Never managed to solve the problem to my satisfaction and pretty much decided to not use USB hardware.

Now that I think about it, I also cache the This VI ref in another VI which I use as sort of an actor debugger to allow me to open the FPs and BDs of any running actors including clones (not AF actors, my own home rolled framework). I poll all the refs multiple times per second to get status about the clone name and running status, and have never seen any weird crashes which I have attributed to that.