Difference: TrbNetMonitoring (1 vs. 8)

Revision 8
01 Feb 2010 - Main.BorislavMilanovic
Line: 1 to 1
 
META TOPICPARENT name="DaqNetwork"
-- BorislavMilanovic - 27 Jul 2009
Line: 99 to 99
 

Discussion

Changed:
<
<
Here is the discussion page where you can post any questions, problems and requirements You may find necessary, until I finish writing my diploma-thesis. The forum will be deleted in some months.

Current topic - monitoring signals comming from the detectors (!)
>
>
Current topic - EPICS integration
 

Revision 7
31 Dec 2009 - Main.JanMichel
Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="NewTriggerBus"
>
>
META TOPICPARENT name="DaqNetwork"
  -- BorislavMilanovic - 27 Jul 2009

TRBnet Monitoring System

Revision 6
06 Oct 2009 - Main.BorislavMilanovic
Line: 1 to 1
 
META TOPICPARENT name="NewTriggerBus"
-- BorislavMilanovic - 27 Jul 2009
Line: 63 to 63
 

Possibilities

Added:
>
>
All FIFOs are predesigned to suit every experiment in near future. Each one can be used in a ringbuffer mode. Usually, when a FIFO is full, it discards all the new data packets trying to be written. In ringbuffer mode, it discards the oldest packet, when near full. Therefore only newest and freshest values are kept inside. When the ringbuffer mode is being used, it can be turned off. However, if a FIFO is built to not support the ringbuffer mode, it can not be turned on again (but the FIFO will spare some resources). Following FIFO sizes were specified:
 
Fifo list Type
8 x 16 LUT
8 x 32 LUT
16 x 16 LUT
16 x 32 LUT
Deleted:
<
<
16 x 1024 BRAM
16 x 2048 BRAM
16 x 4096 BRAM
 
32 x 16 LUT
32 x 32 LUT
Deleted:
<
<
32 x 512 BRAM
32 x 1024 BRAM
32 x 2048 BRAM
 
64 x 16 LUT
64 x 32 LUT
Changed:
<
<
64 x 512 BRAM
64 x 1024 BRAM
>
>
16 x 1024 1 BRAM
16 x 2048 2 BRAM
16 x 4096 4 BRAM
32 x 512 1 BRAM
32 x 1024 2 BRAM
32 x 2048 4 BRAM
64 x 512 2 BRAM
64 x 1024 4 BRAM
 

Every FIFO has following configurations:

Config
.. .. 3 2 1 0
Changed:
<
<
.. .. halt input checking ringbuffer reset
>
>
.. .. halt input checking ringbuffer mode reset

Software Part

Soon, an EPICS implementation will follow. However until then, the user can control the entire monitoring procedure over a command-line interface. A client is connected via Ethernet (TCP/IP) with a server. The server is synthesized in one FPGA anywhere on the TRBnet. The client (outside the TRBnet) can read out FIFOs, Registers, ROMs and write to the config cells. The server awaits instructions and uses 'trbcmd' classes to gain access to the TRBnet over the ETRAX interface. The server is a daemon. Once started on one ETRAX chip with Linux, it listens for incomming TCP/IP instructions. The client can then first acquire all ROM information and configure itself, and afterwards this configuration (addresses, FIFOs, etc...) can be used for precise user control. The client should soon support an EPICS interface for a fine GUI control and signal visualization.

The entire architecture

Due to 'trbcmd', the user can specify one single FIFO address the should be read out, and since all FPGAs on a particular sub-detector are built alike, the user receives this monitoring signal (from the FIFO) for every sub-detector node at once.
 

Discussion

Changed:
<
<
Here is the discussion page, a.k.a. a forum, where You can post any questions, problems and requirements You may find necessary, until I finish writing my diploma-thesis. The forum will be deleted in some months.
>
>
Here is the discussion page where you can post any questions, problems and requirements You may find necessary, until I finish writing my diploma-thesis. The forum will be deleted in some months.
 

Current topic - monitoring signals comming from the detectors (!)
Line: 100 to 110
 

META FILEATTACHMENT attr="" comment="The current monitoring setup" date="1249058006" name="MonitoringOverview.png" path="MonitoringOverview.png" size="144223" user="BorislavMilanovic" version="1.1"
META FILEATTACHMENT attr="" comment="FIFO Data packet" date="1249067125" name="DataPacket.png" path="DataPacket.png" size="91542" user="BorislavMilanovic" version="1.3"
Added:
>
>
META FILEATTACHMENT attr="" comment="The monitoring architecture (HW and SW)" date="1254802946" name="bigARCH.png" path="bigARCH.png" size="63657" user="BorislavMilanovic" version="1.2"
Revision 5
20 Aug 2009 - Main.BorislavMilanovic
Line: 1 to 1
 
META TOPICPARENT name="NewTriggerBus"
-- BorislavMilanovic - 27 Jul 2009
Line: 63 to 63
 

Possibilities

Changed:
<
<
I will insert here a table summarizing all current FIFOs, configurations and areas of use.
>
>
Fifo list Type
8 x 16 LUT
8 x 32 LUT
16 x 16 LUT
16 x 32 LUT
16 x 1024 BRAM
16 x 2048 BRAM
16 x 4096 BRAM
32 x 16 LUT
32 x 32 LUT
32 x 512 BRAM
32 x 1024 BRAM
32 x 2048 BRAM
64 x 16 LUT
64 x 32 LUT
64 x 512 BRAM
64 x 1024 BRAM

Every FIFO has following configurations:

Config
.. .. 3 2 1 0
.. .. halt input checking ringbuffer reset
 

Discussion

Revision 4
01 Aug 2009 - Main.BorislavMilanovic
Line: 1 to 1
 
META TOPICPARENT name="NewTriggerBus"
-- BorislavMilanovic - 27 Jul 2009
Line: 13 to 13
  It is by far not the final version, as the monitoring system is intended to be extensible to fit all the future TRBnet experiments (HADES, FAIR, CBM).
Changed:
<
<
There are also lots of configuration possibilities open, so please tell me - what do You want/need?
>
>
There are also lots of configuration possibilities open, so please let me know - what do You want/need?

 

Requirements

Line: 64 to 67
 

Discussion

Changed:
<
<
I will open a fresh discussion page, a.k.a. a forum, where You can post any questions, problems and requirements You may find necessary, until i finish writing my diploma-thesis. The forum will be deleted in some months.
>
>
Here is the discussion page, a.k.a. a forum, where You can post any questions, problems and requirements You may find necessary, until I finish writing my diploma-thesis. The forum will be deleted in some months.
 

Current topic - monitoring signals comming from the detectors (!)

Added:
>
>

  -- BorislavMilanovic - 31 Jul 2009

META FILEATTACHMENT attr="" comment="The current monitoring setup" date="1249058006" name="MonitoringOverview.png" path="MonitoringOverview.png" size="144223" user="BorislavMilanovic" version="1.1"
Revision 3
31 Jul 2009 - Main.BorislavMilanovic
Line: 1 to 1
 
META TOPICPARENT name="NewTriggerBus"
-- BorislavMilanovic - 27 Jul 2009
Line: 45 to 45
 

More information will follow soon.
Added:
>
>

Data packing

Data packet

This figure illustrates the contents of a FIFO cell. It is possible to tagg any signal comming from the detector with a timestamp and the event-number. There are 3 different timer domains:

  • Global time - is the same on all TRBs
  • Local time - provides higher accuracy (no sync)
  • Time since last trigger

Together with some FIFO-generics like timer-resolution and time-width it is possible to adjust the timestamp exactly to the FIFO type beeing used. Different signals need different timer resolutions, as they do not provide raw detector data with same frequencies.
 

Possibilities

I will insert here a table summarizing all current FIFOs, configurations and areas of use.
Line: 57 to 70
 

Added:
>
>
-- BorislavMilanovic - 31 Jul 2009
 

META FILEATTACHMENT attr="" comment="The current monitoring setup" date="1249058006" name="MonitoringOverview.png" path="MonitoringOverview.png" size="144223" user="BorislavMilanovic" version="1.1"
Added:
>
>
META FILEATTACHMENT attr="" comment="FIFO Data packet" date="1249067125" name="DataPacket.png" path="DataPacket.png" size="91542" user="BorislavMilanovic" version="1.3"
Revision 2
31 Jul 2009 - Main.BorislavMilanovic
Line: 1 to 1
 
META TOPICPARENT name="NewTriggerBus"
-- BorislavMilanovic - 27 Jul 2009
Line: 25 to 25
 
  • Flexibility
  • Real-time access and configuration
Changed:
<
<

HW Architecture

>
>

HW Architecture

The current monitoring setup
 

The whole monitoring system has been redesigned lately to meet all the future requirements. TrbNetRegIO is used to provide access to the monitoring facility, hence read and write signals can be used directly on the 4-th channel of the TRBnet, not interfering with other more critical low level signals.
Line: 35 to 38
 
  • Registers (Address 3000 - 3FFF)
  • FIFOs (Address 2000 - 20FF)
Changed:
<
<
Every cell may be configured extensively by the user. Width, depth, frequency and ringbuffer-mode are just a few possibilities. More information will follow soon.

The register cells are simple, use almost no ressources and allow a direct peek into the FPGA hardware (like temperature, voltage, etc.).
>
>
Every cell may be configured extensively by the user. Width, depth, frequency and ringbuffer-mode are just a few possibilities. An online configuration can also be performed, even during beamtime, using the config-cells. The register cells are simple, use almost no ressources and allow a direct peek into the FPGA-driven hardware (like temperature, voltages, etc.).
 
Changed:
<
<
The FIFOs can be used to track time-sensitive events. There are big FIFOs which use one or more Block-RAMs and the small LUT-FIFOs, using logic cells only. They both insert new data only at a given frequency. If the frequency is high enough, even logic analyser output can be monitored.

All information about the FIFO-types is stored in a ROM on each FPGA. On the first start, the monitoring system simply reads out the entire ROM and knows exactly which addresses, sizes and types of cells it is dealing with.
>
>
The FIFOs can be used to track time-sensitive events. There are big FIFOs which use one or more Block-RAMs and the small LUT-FIFOs, using logic cells only. They both insert new data only at a given frequency. If the frequency is high enough, even logic analyser output can be monitored. Current tests have confirmed that data can be written to the FIFO every clock-cycle, i.e. every 10ns. All information about the FIFO-types is stored in a ROM on each FPGA. On the first start, the monitoring system simply reads out the entire ROMs and knows exactly which addresses, sizes and types of cells it has to deal with.
 

More information will follow soon.

Possibilities

Changed:
<
<
I will insert here a table summarizing all current FIFOs, configurations and area of use.
>
>
I will insert here a table summarizing all current FIFOs, configurations and areas of use.
 

Discussion

I will open a fresh discussion page, a.k.a. a forum, where You can post any questions, problems and requirements You may find necessary, until i finish writing my diploma-thesis. The forum will be deleted in some months.
Added:
>
>
Current topic - monitoring signals comming from the detectors (!)
 
Added:
>
>

META FILEATTACHMENT attr="" comment="The current monitoring setup" date="1249058006" name="MonitoringOverview.png" path="MonitoringOverview.png" size="144223" user="BorislavMilanovic" version="1.1"
 
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)