Difference between revisions of "Supported Hardware"

From MidasWiki
Jump to navigation Jump to search
Line 1: Line 1:
Over the last 20 years, the hardware used for physics experiment did evolved from CAMAC or FastBus to VME and more recently to Network devices gathering data from custom FPGAs acquisition boards. Obviously not all models for a given category are present, but similarity between their operations may provide you a good starting point for a particular driver development.
+
{{Pagelinks}}
 +
 
 +
Over the last 20 years, the hardware used for physics experiment evolved from CAMAC or FastBus to VME and more recently to Network devices gathering data from custom FPGAs acquisition boards. Obviously not all models for a given category are present, but similarity between their operations may provide you a good starting point for a particular driver development.
 
Find out what type of hardware is currently supported in [https://bitbucket.org/tmidas/midas/src/93fa5ed4a40df94d4241e4a1910e44d1c5c8b866/drivers/?at=develop the Midas Git Repository /Drivers]
 
Find out what type of hardware is currently supported in [https://bitbucket.org/tmidas/midas/src/93fa5ed4a40df94d4241e4a1910e44d1c5c8b866/drivers/?at=develop the Midas Git Repository /Drivers]
  
 
=== CAMAC ===   
 
=== CAMAC ===   
Even though CAMAC is not much used any more, when simple test need to be done and old equipment are still available and functional, it can provide a quick solution to an otherwise heavy or cumbersome DAQ system.
+
Even though CAMAC is no longer used very much, when a simple test need to be done and old equipment is still available and functional, it can provide a quick solution to an otherwise heavy or cumbersome DAQ system.
Recent USB/CAMAC interfaces can be attractive as they provide '''fast CAMAC cycle''' (data collection through preloaded CAMAC list) and will shelf permanently the old ISA or PCI interfaces that newer hardware can't support any more anyway.
+
Recent USB/CAMAC interfaces can be attractive as they provide '''fast CAMAC cycle''' (data collection through preloaded CAMAC list) and will shelve permanently the old ISA or PCI interfaces that newer hardware does not support.
  
 
=== FastBus ===
 
=== FastBus ===
This hardware was accessed through VME. Modules are obsolete.
+
This hardware was accessed through VME. Modules are now obsolete.
  
 
=== VME ===
 
=== VME ===
VME is still widely used and various type of VME interfaces can be found such as: VME processors, USB device, Optical link to PCIe card, Network based interfaces.
+
VME is still widely used and various type of VME interfaces can be found. The more common interfaces are supported by Midas, such as: VME processors, USB device, Optical link to PCIe card, Network based interfaces, SIS3100 PCIe interfaces, or VME processors for more demanding VME requirements.
SIS3100 PCIe interfaces, or VME processors for more demanding VME requirements are the more common interfaces supported by Midas.
 
  
Worth to be mentioned that commercial VME modules manufacturer are using the VME crate housing for power distribution and provide access to their device using propitiatory lin such as optical to improve the data transfer rate. This configuration requires a dedicated PCIe interface sitting in a PC. The VME access remains available in any case.
+
It's worth mentioning that manufacturers of commercial VME modules are using the VME crate housing for power distribution and provide access to their device using propitiatory links (such as optical) to improve the data transfer rate. This configuration requires a dedicated PCIe interface sitting in a PC. The VME access remains available in any case.
  
 
=== Serial communication ===
 
=== Serial communication ===
Line 19: Line 20:
  
 
=== Software layers ===
 
=== Software layers ===
Midas includes for the so called "slow control hardware" a multi-layer concept based on the Object-Oriented programming. It is composed of 3 layers (3 directories)
+
Midas includes support for the so called "slow control hardware" a multi-layer concept based on the Object-Oriented programming. It is composed of 3 layers (3 directories)
 
* ''Class/'' describes the main functionality of the device
 
* ''Class/'' describes the main functionality of the device
 
** High Voltage devices provides similar functionality across the different brand, ex:class/hv.c will implement the user/Midas(ODB) interface and call the appropriate function for that device through the device layer.
 
** High Voltage devices provides similar functionality across the different brand, ex:class/hv.c will implement the user/Midas(ODB) interface and call the appropriate function for that device through the device layer.
Line 27: Line 28:
 
** Serial, parallel, GPIB, Ethernet or proprietary communication to the device. The ex:bus/rs232.h will package the request into the appropriate form to be delivered to the device.
 
** Serial, parallel, GPIB, Ethernet or proprietary communication to the device. The ex:bus/rs232.h will package the request into the appropriate form to be delivered to the device.
  
''Note:'' not all the device drivers implement the triple layer (Class, Device, Bus) as some include the hardware calls directly from the device layer.
+
''Note:'' not all the device drivers implement the triple layer (Class, Device, Bus) as some include the hardware calls directly from the device layer.
 +
 
 +
See [[Slow Control System]] for more details.
 +
 
 +
[[Category:Appendices]]

Revision as of 16:44, 14 July 2015


Over the last 20 years, the hardware used for physics experiment evolved from CAMAC or FastBus to VME and more recently to Network devices gathering data from custom FPGAs acquisition boards. Obviously not all models for a given category are present, but similarity between their operations may provide you a good starting point for a particular driver development. Find out what type of hardware is currently supported in the Midas Git Repository /Drivers

CAMAC

Even though CAMAC is no longer used very much, when a simple test need to be done and old equipment is still available and functional, it can provide a quick solution to an otherwise heavy or cumbersome DAQ system. Recent USB/CAMAC interfaces can be attractive as they provide fast CAMAC cycle (data collection through preloaded CAMAC list) and will shelve permanently the old ISA or PCI interfaces that newer hardware does not support.

FastBus

This hardware was accessed through VME. Modules are now obsolete.

VME

VME is still widely used and various type of VME interfaces can be found. The more common interfaces are supported by Midas, such as: VME processors, USB device, Optical link to PCIe card, Network based interfaces, SIS3100 PCIe interfaces, or VME processors for more demanding VME requirements.

It's worth mentioning that manufacturers of commercial VME modules are using the VME crate housing for power distribution and provide access to their device using propitiatory links (such as optical) to improve the data transfer rate. This configuration requires a dedicated PCIe interface sitting in a PC. The VME access remains available in any case.

Serial communication

RS232, USB communication are sometime necessary. Network interface devices to these type of serial interfaces are getting popular by providing a common programming layer independent of the hardware communication. Similarly, software layer such as ser2net will bridge serial devices connected to a PC to a remote network application for communication.

Software layers

Midas includes support for the so called "slow control hardware" a multi-layer concept based on the Object-Oriented programming. It is composed of 3 layers (3 directories)

  • Class/ describes the main functionality of the device
    • High Voltage devices provides similar functionality across the different brand, ex:class/hv.c will implement the user/Midas(ODB) interface and call the appropriate function for that device through the device layer.
  • Device/ describes the functionality implementation for that particular device.
    • Depending on the device hardware, the requested function may involve a specific access sequence. The ex:device/lrs4420.c will format that transaction and call the appropriate communication function implemented into by this device
  • Bus/ describes the access specific to the device.
    • Serial, parallel, GPIB, Ethernet or proprietary communication to the device. The ex:bus/rs232.h will package the request into the appropriate form to be delivered to the device.

Note: not all the device drivers implement the triple layer (Class, Device, Bus) as some include the hardware calls directly from the device layer.

See Slow Control System for more details.