Using IPbus: Difference between revisions

Revision as of 15:17, 21 June 2020

Main Page -> Control & Readout Software Documentation and Howto's -> Using IPbus

Use case

IPbus is a control protocol that uses UDP/IP to send values into the registries on the readout unit (RU). The software on the host computer uses the Hardware Access Library (uHAL) to send the commands to the RU.

Configuration files

There is a main connection file pRU-connections.xml, this file contains the address and port of the RU, for information on the content of the connection file please see the pRU Ethernet Configuration document.

Following there is a Module registers file (module-address.xml), this file contains a table with all the registries present in the RU.

Finally, there are files for each register

global_regs.xml
trigger_manager.xml
offload.xml
alpide_control.xml
alpide_data.xml

As of the writing of this page, these files can be found on the production_test repository in the ipbus branch under the BSP folder.

WARNING: To prevent undefined behavior the registers' files MUST match the firmware version!

@@ Line 2: / Line 2: @@
 == Use case ==
-IPbus is a control protocol that uses UDP/IP to send values into the registries on the readout unit (RU). Hardware Access Library (uHAL) is used on the host computer to send the commands.
+IPbus is a control protocol that uses UDP/IP to send values into the registries on the readout unit (RU). The software on the host computer uses the Hardware Access Library (uHAL) to send the commands to the RU.
@@ Line 17: / Line 17: @@
 * alpide_data.xml
-PTB-specific Module R
+As of the writing of this page, these files can be found on the production_test repository in the ipbus branch under the BSP folder.
-As of the writing of this page, these files can be found on the production_test repository in the ipbus fork under the BSP folder.
+WARNING: To prevent undefined behavior the registers' files MUST match the firmware version!