Cordm at 13:38, 5 February 2026

2026-02-05T13:38:53Z

← Older revision		Revision as of 13:38, 5 February 2026
Line 9:		Line 9:
	\|presenters=Gary Boorman		\|presenters=Gary Boorman
	\|abstract=How does the typical cRIO module work? What happens when a cRIO module is plugged into a chassis? What happens when a property or invoke node is placed on your FPGA block diagram? How does the cRIO controller know about the module’s capabilities? Does the cRIO controller really have a backplane? And why are cRIO modules hot-swappable?		\|abstract=How does the typical cRIO module work? What happens when a cRIO module is plugged into a chassis? What happens when a property or invoke node is placed on your FPGA block diagram? How does the cRIO controller know about the module’s capabilities? Does the cRIO controller really have a backplane? And why are cRIO modules hot-swappable?


	Using information learned from building my own cRIO modules, and from writing the drivers in LabVIEW and XML, to creating an API, this talk will look at some of the magic that happens when a cRIO module is inserted into a chassis, and how the LabVIEW FPGA code interacts with cRIO modules.		Using information learned from building my own cRIO modules, and from writing the drivers in LabVIEW and XML, to creating an API, this talk will look at some of the magic that happens when a cRIO module is inserted into a chassis, and how the LabVIEW FPGA code interacts with cRIO modules.

Cordm: Created page with "{{infobox |category=presentation |icon=GDevConButton.png |presentation-conference=GDevCon-6{{!}}GDevCon#6 |presentation-presenter=Gary Boorman }} {{presentation |presenters=Gary Boorman |abstract=How does the typical cRIO module work? What happens when a cRIO module is plugged into a chassis? What happens when a property or invoke node is placed on your FPGA block diagram? How does the cRIO controller know about the module’s capabilities? Does the cRIO controller re..."

2026-02-05T13:38:10Z

Created page with "{{infobox |category=presentation |icon=GDevConButton.png |presentation-conference=GDevCon-6{{!}}GDevCon#6 |presentation-presenter=Gary Boorman }} {{presentation |presenters=Gary Boorman |abstract=How does the typical cRIO module work? What happens when a cRIO module is plugged into a chassis? What happens when a property or invoke node is placed on your FPGA block diagram? How does the cRIO controller know about the module’s capabilities? Does the cRIO controller re..."

New page

{{infobox
|category=presentation
|icon=GDevConButton.png
|presentation-conference=GDevCon-6{{!}}GDevCon#6
|presentation-presenter=Gary Boorman
}}

{{presentation
|presenters=Gary Boorman
|abstract=How does the typical cRIO module work? What happens when a cRIO module is plugged into a chassis? What happens when a property or invoke node is placed on your FPGA block diagram? How does the cRIO controller know about the module’s capabilities? Does the cRIO controller really have a backplane? And why are cRIO modules hot-swappable?

Using information learned from building my own cRIO modules, and from writing the drivers in LabVIEW and XML, to creating an API, this talk will look at some of the magic that happens when a cRIO module is inserted into a chassis, and how the LabVIEW FPGA code interacts with cRIO modules.
|youtube-id=XGLsP_IwO-o
}}

[[Category:GDevCon-6]]

GDevCon-6/The Anatomy of a cRIO Module - Revision history

Cordm at 13:38, 5 February 2026