Front panel gage display in cRIO

[VPEA]

I updated my cRIO 9045 to the latest firmware and LV2024, and now my gage is not displaying properly.  Is this a known issue?

[Bob_Schor]

Are you running a Real-Time OS on the cRIO?  When you run your program, is the cRIO connected to a PC running Windows and LabVIEW, and communicating with the (Real-Time) code running on the cRIO?  If so, I strongly recommend a proper "division of labor" with the Host (PC) running the "Front Panel" controls and file I/O, and the cRIO handling the Real-Time data processing.  Communication between Host and Target takes place over Ethernet (I use Network Streams, others have use TCP or UDP).

Making a Gauge display should be simple on the Host (you can certainly use a "Gauge" indicator, or "draw a picture" ...)

Bob Schor

[VPEA]

The LV code is running standalone on the cRIO.  I have a touch screen connected by HDMI which displays "live" data at a 250ms and a 1000ms update rate. In this case, the gage is updated at 250ms. The screen also allows the user to interact with the settings and operation of the software.  The display worked without flaws until I updated the cRIO firmware and the LV version.  Not sure which update caused the issue since I did both at the same time.

[Bob_Schor]

Can you go back to your previous version, restoring both the cRIO firmware and LabVIEW version?  If I were to guess (I just flipped a coin, it came up "Heads"), I'd suspect the cRIO firmware.  It would be interesting to see "new LabVIEW code on old cRIO firmware", and if that fails, try "updating cRIO and restoring the old LabVIEW".  If that still fails, make sure the old firmware with the old LabVIEW still works.

Bob Schor

P.S. -- I do realize the above suggestion might not be feasible, and would definitely be a P.I.T.A., but if, as it seems, changing both firmware and LabVIEW "breaks" the system, is it "reproducible"?

[VPEA]

Yes, that was a PITA, but beneficial.  Downgrading the firmware did not help.  Downgrading LV forced me to also downgrade XNET.  I could not test just the LV downgrade, but after both LV and XNET were downgraded, the issue went away.

Is there a way to upgrade just XNET on the cRIO without upgrading LV?

[VPEA]

Wanted to provide an update for everyone who might encounter this same issue.

I updated everything to 2025Q2 (LabView, all the drivers on the host computer, XNET, NI-MAX, VISA, etc., including the cRIO firmware, the programming environment, base system, etc.).  Then I deployed an updated version of my code and all works and displays as it should.