12-11-2017 09:13 AM
12-11-2017 09:27 AM
Hi Hernant,
you can connect your cRIO to a monitor using some wires, it's physically possible.
Would it be useful, when your cRIO doesn't provide a monitor output? No…
(Using some high-speed analog outputs you could fake a VGA signal. Quite some effort, but used for some emulator hardware for old game controllers.)
12-11-2017 09:33 AM
Why it's not useful to have moniter output.
Do you have any connection diagram to connect to moniter?
Hemant
12-11-2017 09:52 AM - edited 12-11-2017 09:54 AM
A Compact RIO is an I/O controller that includes some on-board processing capabilities to facilitate I/O and allow some control loops to run independently from the main LabVIEW code (running on a PC) that has the User Interface. It is this "Main" routine that can acquire data via the cRIO and produce the displays that you need -- the cRIO is best thought of as an I/O controller, though one that can handle some processing and Control Loop chores without involving the calling PC. To put Display processors on this specialized I/O controller would vastly complicate its architecture, and undoubtedly cause a significant speed penalty.
Bob Schor
12-11-2017 10:24 AM
The cRIO-903X series have Display Port capability and you can enable the embedded display. This does take resources away from your application and may introduce jitter and resource exhaustion.
12-12-2017 05:34 AM
As others have said - some of the CompactRIO chassis have display options (e.g. DisplayPort etc.) so you can connect them to a monitor although I don't think this is used very often.
More commonly, you would write a separate PC application to act as your user interface which communicates with the CompactRIO to send/receive data/commands from the user. You could also use something like Web Services / WebSockets to provide a web-based interface to the CompactRIO.