[3668398.689779] usb 1-2.1: new high-speed USB device number 111 using xhci_hcd
[3668398.768543] usb 1-2.1: New USB device found, idVendor=3923, idProduct=709b, bcdDevice= 1.01
[3668398.768560] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3668398.768567] usb 1-2.1: Product: GPIB-USB-HS
[3668398.768573] usb 1-2.1: Manufacturer: National Instruments
[3668398.768579] usb 1-2.1: SerialNumber: 01211B2F
# gpib_config
failed to open device file '/dev/gpib0'
main: No such file or directory
Geez. What's going on, where is my kernel module?
Bun's Lab
Get the source: mkdir ~/src && cd ~/src svn checkout svn://svn.code.sf.net/p/linux-gpib/code/trunk linux-gpib-code Kernel module, you of course need your kernel's header files: cd ~/src/linux-gpib-code/linux-gpib-kernel make -j8 sudo make install User land…
Had to recompile the kernel modules. There's been some kernel update or another since, and since this is plain source code, apt doesn't know to do that for me.
E1406A_Command_Module_Users_Manual.pdf
2.8 MB
283 pages of documentation.
The E1406A is the C sized version of the E1306A. Couldn't find the manual for the E1306A.
No time to read it now, I wanna get somewhere fast
The E1406A is the C sized version of the E1306A. Couldn't find the manual for the E1306A.
No time to read it now, I wanna get somewhere fast
😨1
Bun's Lab
There's life on RS232!
This only gives me Unrecognized command no matter what
ST is a command that is recognized, and so is ST VT220. Resizing my konsole window appropriately and doing
and then running
Gives me a text user interface with working navigation using the function keys.
% echo $TERM
xterm-256color
% export TERM=vt220
% picocom -b 9600 -d 8 -p n -f n -y n /dev/ttyUSB0
and then running
ST VT220
Gives me a text user interface with working navigation using the function keys.
Now it completely died :(
There's a buzzer on the control module board and not even that does a sound anymore
There's a buzzer on the control module board and not even that does a sound anymore
Letting it rest a bit stabilizes it. I know it's risky to even try with a sketchy PSU but I have an urge to poke this thing. Will come up with a temporary solution tomorrow.
This media is not supported in your browser
VIEW IN TELEGRAM
The terminal emulation gave me issues. Only function keys F1 through F4 would work in the text interface. So I dug out a real terminal and set it to VT220 mode.
VXI stands for VME eXtension for Instrumentation. My command module and instruments only use the P1 connector which is also present in VME. So it should work
Compare this to the VME bus (sans the 64 bit extensions on row z and a)
https://electronics.stackexchange.com/q/450179
https://electronics.stackexchange.com/q/450179