Difference: NetworkAddresses (1 vs. 5)

Revision 5
25 Jan 2010 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

TRBNet Addresses

Here are some suggestions for TrbNet Addresses in the final detector setup. They were choosen based on the following premises:
Line: 10 to 10
 
  • Since a board may be unplugged at one position and later installed on another, entries in the database can be marked as active or inactive. Active entries are used by the DHCP deamon, inactive entries are for documentation & analysis only
  • There is no need to consult the database to get the position of a board since it is already encoded in the address itself (-> saves computation time & makes online-tracking easier). In the table this is shown under "naming scheme" where a string like "1ISF" shows the meaning of each nibble of the address.

Changed:
<
<
>
>
The up-to-date table can be found in the TrbNet Documentation.
 

Broadcasts

  • The generic BROADCAST_BITMASK selects the broadcasts a board is able to receive
Line: 49 to 49
 

The Subevent ID of a board is the trbnet address of the board where all bits marking replacement boards are set to 0.
Added:
>
>
The up-to-date table can be found in the TrbNet Documentation.

 

Database

The main database for addresses will give the information that is needed to assign addresses and subeventids to all boards. This information is:
Revision 4
24 Nov 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

TRBNet Addresses

Here are some suggestions for TrbNet Addresses in the final detector setup. They were choosen based on the following premises:
Line: 17 to 17
 
MDC AddOn 12 1000 - 17FF 1ISF where I: inner(1), outer(0) MDC, S: Sector, F: FPGA on board I+2,I+4,I+6 and/or S+8
MDC OEPB 372 2000 - 2FFF 2LSM where L: MDC-layer, S: Sector, M: Motherboard L+4, L+8, L+12 and/or S+8
RICH ADCM 30 3000 - 31FF 30SB where S: Sector, B: Board Replacement boards: S+8 and/or B+8
Changed:
<
<
Shower AddOn 6 3200 - 32FF 32NS where S: Sector, N=0 N <> 0
>
>
Shower AddOn 6 3200 - 33FF 32NS where S: Sector, N=FPGA 0x33xx
 
TRB Start, Veto 2 4000 - 40FF 40NP where N=0, P = Board position N <> 0
TRB FW 3 4100 - 41FF 41NP where N=0, P = Board position N <> 0
TRB RPC 24 4400 - 47FF 44SB where S: Sector, B: Board 44,45,46,47 or S+8, B+8
TRB TOF 12 4800 - 4BFF 48SB where S: Sector, B: Board 48,49,4A,4B or S+8, B+8
Ethernet Bridges ? 5000 - 5FFF 5nxy where n is detector: 0 inner mdc, 1 outer mdc, 2 rich, 3 shower , 4 -F others
Changed:
<
<
Hubs ~10 8000 - 8FFF Without fixed numbering scheme
>
>
Hubs ~10 8000 - 8FFF 0x830n for RICH hubs, rest not yet defined
 
Test Setups   F000 - FEFF  
Broadcasts   FF00 - FFFF  
Line: 49 to 49
 

The Subevent ID of a board is the trbnet address of the board where all bits marking replacement boards are set to 0.
Added:
>
>
System Subevent IDs Description
MDC 0x1IS0 where I is 0 for inner and 1 for outer MDC and S is the sector, counting from 0 to 5
RICH 0x830I where I is any hex digit, depending on the final decision on the number of Hubs used
Shower 0x32S0 where S is the sector, counting from 0 to 5
Start / Veto / other TRBs 0x40NN N is any hex digit
Wall 0x410N N depending on number of board / any hex digit
RPC 0x44SB where S is sector and B is board number
TOF 0x48SB where S is sector and B is board number
 

Database

The main database for addresses will give the information that is needed to assign addresses and subeventids to all boards. This information is:
Revision 3
23 Jun 2009 - Main.MarekPalka
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

TRBNet Addresses

Here are some suggestions for TrbNet Addresses in the final detector setup. They were choosen based on the following premises:
Line: 9 to 9
 
  • Upon replacement, the new address still marks the position, but otherwise unused bits are set
  • Since a board may be unplugged at one position and later installed on another, entries in the database can be marked as active or inactive. Active entries are used by the DHCP deamon, inactive entries are for documentation & analysis only
  • There is no need to consult the database to get the position of a board since it is already encoded in the address itself (-> saves computation time & makes online-tracking easier). In the table this is shown under "naming scheme" where a string like "1ISF" shows the meaning of each nibble of the address.
Deleted:
<
<
  • Addresses are independent from subevent-IDs which are assigned independently
 

Line: 23 to 22
 
TRB FW 3 4100 - 41FF 41NP where N=0, P = Board position N <> 0
TRB RPC 24 4400 - 47FF 44SB where S: Sector, B: Board 44,45,46,47 or S+8, B+8
TRB TOF 12 4800 - 4BFF 48SB where S: Sector, B: Board 48,49,4A,4B or S+8, B+8
Changed:
<
<
Ethernet Bridges ? 5000 - 5FFF Without fixed numbering scheme
>
>
Ethernet Bridges ? 5000 - 5FFF 5nxy where n is detector: 0 inner mdc, 1 outer mdc, 2 rich, 3 shower , 4 -F others
 
Hubs ~10 8000 - 8FFF Without fixed numbering scheme
Test Setups   F000 - FEFF  
Broadcasts   FF00 - FFFF  
Line: 44 to 43
 
6 FFBF  
7 FF7F Ethernet Bridges
Changed:
<
<
-- JanMichel - 12 May 2009
>
>

Subevent ID

The subevent ids are assigned based on the trbnet addresses. Since only boards that sent data via Ethernet produce subevent headers (which are TRBs using its TDCs or Ethernet Bridges), the range of possible subeventids is limited to the range between 0x4000 und 0x5FFF.

The Subevent ID of a board is the trbnet address of the board where all bits marking replacement boards are set to 0.

Database

The main database for addresses will give the information that is needed to assign addresses and subeventids to all boards. This information is:
  • Unique Id + endpoint id (=number of fpga on board) 64 + 8 bit
  • Place on detector (= base part of trbnet address)
  • trbnet address 16 bit
  • Verbose description of location
  • Time of installation
  • Time of deinstallation
  • board type (some kind of enum list)
  • Verbose description of board
This table must always be up-to-date, thus an easy interface and some pressure to do updates is needed here. For example, a feature of the network startup process can be that it throws an error if it detects an unlisted board or if the place of a board inside the network has changed.

TODO

  • Agree on database format
  • Write tool that checks presence of boards and assigns addresses
  • Make address maps for all detectors

-- JanMichel - 13 June 2009
 
Revision 2
18 May 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

TRBNet Addresses

Here are some suggestions for TrbNet Addresses in the final detector setup. They were choosen based on the following premises:
Line: 8 to 8
 
  • Addresses represent the position and purpose of the board on the detector
  • Upon replacement, the new address still marks the position, but otherwise unused bits are set
  • Since a board may be unplugged at one position and later installed on another, entries in the database can be marked as active or inactive. Active entries are used by the DHCP deamon, inactive entries are for documentation & analysis only
Changed:
<
<
  • There is no need to consult the database to get the position of a board since it is already encoded in the address itself (-> saves computation time & makes online-tracking easier)
>
>
  • There is no need to consult the database to get the position of a board since it is already encoded in the address itself (-> saves computation time & makes online-tracking easier). In the table this is shown under "naming scheme" where a string like "1ISF" shows the meaning of each nibble of the address.
 
  • Addresses are independent from subevent-IDs which are assigned independently

Line: 29 to 29
 
Broadcasts   FF00 - FFFF  
Added:
>
>

Broadcasts

  • The generic BROADCAST_BITMASK selects the broadcasts a board is able to receive
  • Several broadcast addresses may be combined by unsetting more than one bit, so that the board answers on two or more specific resets.

Unset Bit Corresponding Address Addresses Types
- FFFF All boards
0 FFFE Hubs
1 FFFD MED OEPB
2 FFFB RICH ADCM
3 FFF7 Shower AddOn
4 FFEF TOF TRB
5 FFDF RPC TRB
6 FFBF  
7 FF7F Ethernet Bridges
  -- JanMichel - 12 May 2009
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)