Most TRB3 designs contain the feature to forward signals from any input to the CTS to be used for triggering. That is, any input to a TDC design or the data from ADC-AddOn crossing a configurable threshold can be selected to be forwarded to the CTS. The signal is sent on-board the TRB3 or using RJ-45 cables between boards. For convenient use, a coincidence between two groups of signals can be generated as well.
Using this features gives various options to trigger on input signals - without the need to install a dedicated signal cable to the CTS.
Do you have any devices that needs to be remote controlled using a RS232 or serial link? And there is no computer nearby to provide this interface?
Both TRB3 and TRB3sc include a UART module that can be controlled via TrbNet. The output uses LVTTL signals, but an external board can be used to convert to a real RS232.
Did you know that both TRB3 and TRB3sc feature a pin-header providing 2.5V, 3.3V and 5-6V to power your peripherals? The suggested connector is Molex 0901420010 to force the correct positioning and prevent short circuits or over-voltage issues but any other female connectors for pin-headers will do as well.
Please be aware that the pin-out of the two power connectors is different as the TRB3 provides an additional 1.8V not available on TRB3sc.
The new JTAG-programmer: Used instead of the normal white programmer, features four different outputs matching the connectors on most of our boards. The board can be changed to a USB-to-serial, USB-to-SPI or similar converter by reprogramming of the FTDI USB-chip.
Note that there are some software issues on some Linux systems which need to be investigated. On Windows and some Linux machines it works flawless and faster than the original programmer.
The auto-completion function of the zsh now supports the "trbcmd" and "trbflash" commands. The details are in
zsh-auto-completion
