LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO triggering event structure no UI

I am using a cRIO-9047 with an embedded UI.

I am able to use interactive mode (view probes / front panels etc) but only with the embedded UI disabled. If I try and enter interactive mode with the UI enabled I get an error at the end of deployment and the cRIO restarts.

With the UI disabled I don’t get the event structure responding to button presses on my interactive display - which is as expected for a non embedded UI cRIO.

Is it possible to use scripting to cause events to occur in an interactive RT environment?

0 Kudos
Message 1 of 4
(205 Views)

I don’t want to change 50 event cases by adding dynamic events but just insert events into the event structure queue - if possible!

0 Kudos
Message 2 of 4
(204 Views)

@Al1234 wrote:

I am using a cRIO-9047 with an embedded UI.

I am able to use interactive mode (view probes / front panels etc) but only with the embedded UI disabled. If I try and enter interactive mode with the UI enabled I get an error at the end of deployment and the cRIO restarts.

With the UI disabled I don’t get the event structure responding to button presses on my interactive display - which is as expected for a non embedded UI cRIO.

Is it possible to use scripting to cause events to occur in an interactive RT environment?


 

IIRC you can't use front panel events with RT. No difference for embedded UI enabled or not. There is an example on host - rt target communication on the examples leveraging shared variable nodes. 

These days I prefer ni gRPC device server, if no timed loop is necessary.

Actor Framework
0 Kudos
Message 3 of 4
(127 Views)

Front panel events work fine when using the embedded UI. 
When in interactive mode they also work OK with the code running on the cRIO and using the laptop screen to control the cRIO (the embedded UI screen has the LabVIEW front panel with the text ‘remote control’ bottom right)

I have found what prevents interactive mode as described above is if FPGA code is accessed from the RT. This then causes fail during upload to the cRIO. 
not sure we hat to try next - any ideas?


 

0 Kudos
Message 4 of 4
(109 Views)