HV MainFrame 1458
Lecroy 1458 HV Main frame
Both of the crates (1454 and 1458) provide an RS-232 interface, allowing the use of a standard terminal for control and display. This interface provides the same capabilities as the front panel display in a text command format or full screen format (VT100 compatible). The front panel and RS-232 interfaces are always available for reviewing information in the crate, but changes can be locked out remotely or via a front panel key switch.
Finally, VISyN crates can be controlled (optional) over local area networks (LAN) via ARCNET or Ethernet (TCPIP). Ethernet is the most widely used LAN, available for all types of host systems. It allows for control over laboratory intranets as well as common internets. ARCNET is a proven industrial standard. It is a high speed (2.5 Mbaud) token-passing network protocol. The standard implementation of ARCNET is readily available and inexpensive for many types of host systems, including VME. Long distances (4 miles) can be covered; the token-passing system is deterministic; in heavy traffic; throughput does not decrease.
The Model 1458 Crate addresses high channel count applications. This crate supplies sixteen (16) slots for HV cards, but no keypad or LCD display. All control is via RS-232 or a local area network. The 1458 supports 192 channels of the 1461 HV card in 14 inches of vertical rack space.
Model 1461 3 kV Independent HV Supply
The Model 1461 HV card supplies 12 independent channels, in a single slot, suitable for photomultiplier tubes. The high voltage output is programmable from 0 to 3 kV. The output current supports a 1.2 Mohm load to 3 kV. Other features include voltage measurement, current measurement, programmable current trip, hardware voltage limit (once per card), and separate programmable ramp up and ramp down rates.
Running on DAQ1
login to daq1
socat TCP4-LISTEN:5555,crnl,fork /dev/ttyS1,raw,echo=0,crnl,b9600
open another terminal window
Running on DAQ2
Using daq2, copy and paste the entire block of code below into a single terminal. (The "echo" command is there just to cause the evaluation of the second to last line w/o needing to hit enter.)
enter the commands below as root in two different xterm windows
in the first xterm window type
source ~daq/CODA/2.6.2/setup cd /root/slowc/socat/socat-18.104.22.168 ./socat TCP4-LISTEN:5555,crnl,fork /dev/ttyS0,raw,echo=0,crnl,b9600
in the second xterm window
Could not listen on port: 5555
Unplugging the rs-232 cable and plugging it back in worked once.
At the second instance a full power cycle of the crate was needed
The GUI and the command line scripts are in the same package.
You require the GUI to be working first. The CLI scripts talk to the server associated with the GUI.
I put a tarball of a 2010 version of the code here:
There is a lot of garbage in that tarball (sorry). You'll want to do something like this:
% tar xvjf slowc.tar.bz2 % cd slowc % mkdir TEST % ./hvs TEST
If you're lucky the GUI will start and you can follow the (limited) instructions here to add your crate ('HVFrame'):
The GUI needs to talk to the crate via a TCP ("telnet") connection. This is trivial if you have a portserver. If you have the crate connected to the computer via a serial port, then you will need to run a program called 'socat' to provide the TCP interface that the GUI needs. The syntax will be something like this:
% socat TCP4:localhost:5555 /dev/ttyS1,raw,echo=0,crnl
The GUI would then talk to the HVFrame at localhost:5555 (The socat line is off the top of my head -- let me know if it doesn't work.)
socat is put in the the subdirectory
make sure that the user can talk to the serial port. the user root can do this automatically you can edit /etc/group and add the user "daq"
type groups on the command line to see if you are a member now
socat TCP-LISTEN:5555,crnl,fork /dev/ttyS1,raw,echo=0,crnl,b9600
usr/local/bin/socat TCP4-LISTEN:5555,crnl,fork /dev/ttyS1,raw,echo=0,crnl,b9600
uucp owns the /dev/ttyS1 device
Notes On Operation
- If no interlock system exists, the interlock bnc connector must be capped. Otherwise, the mainframe will throw a PANICOFF error.
- To clear a PANICOFF error, you must put the machine into local mode and press the HV Off button.