From: Dirk <mai...@gm...> - 2021-10-11 18:36:18
|
Hello, several weeks ago i obtained a RaspberryPI GPIB Shield. I followed the instructions at http://elektronomikon.org/install.html but did minor changes to get version 4.3.4 working. Installation went fine without any problems. If i try to read something from my R&S URV5 power meter nothing happend. I get the same result with my SMG signal generator. Testing the system with "ibtest" (-> line status) shows unkown status of bus lines. At this point i have no idea what is wrong in my setup. It would be great if someone can help me. BR Dirk Following some additional information: root@raspberrypi:/home/pi# cat /etc/debian_version 10.10 root@raspberrypi:/home/pi# root@raspberrypi:/home/pi# uname -a Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 armv7l GNU/Linux root@raspberrypi:/home/pi# root@raspberrypi:/home/pi# dmesg [...] [ 55.161921] gpib_common: loading out-of-tree module taints kernel. [ 55.164358] Linux-GPIB 4.3.4 Driver [ 55.182620] gpib: registered gpib_bitbang interface root@raspberrypi:/home/pi# root@raspberrypi:/home/pi# gpib_config -v linux-gpib version = 4.3.4 root@raspberrypi:/home/pi# root@raspberrypi:/home/pi# ibterm -d10 Attempting to open /dev/gpib0 pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 ibterm>*IDN? ibterm> ibterm: Done. root@raspberrypi:/home/pi# root@raspberrypi:/home/pi# ibtest Do you wish to open a (d)evice or an interface (b)oard? (you probably want to open a device): b enter name of interface board (or device) you wish to open: violet trying to open board named 'violet' You can: w(a)it for an event [...] send group e(x)ecute trigger (device only) : l DAV unknown NDAC unknown NRFD unknown IFC unknown REN unknown SRQ unknown ATN unknown EOI unknown gpib status is: ibsta = 0x1160 < SRQI CMPL REM CIC > iberr= 0 ibcntl = 0 You can: w(a)it for an event [...] send group e(x)ecute trigger (device only) : root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf [...] /* This section configures the configurable driver characteristics * for an interface board, such as board address, and interrupt level. * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, etc. */ interface { minor = 0 /* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */ board_type = "gpib_bitbang" /* type of interface board being used */ name = "violet" /* optional name, allows you to get a board descriptor using ibfind() */ pad = 0 /* primary address of interface */ sad = 0 /* secondary address of interface */ timeout = T3s /* timeout for commands */ eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is carriage return */ set-reos = yes /* Terminate read if EOS */ set-bin = no /* Compare EOS 8-bit */ set-xeos = no /* Assert EOI whenever EOS byte is sent */ set-eot = yes /* Assert EOI with last byte on writes */ /* settings for boards that lack plug-n-play capability */ base = 0 /* Base io ADDRESS */ irq = 0 /* Interrupt request level */ dma = 0 /* DMA channel (zero disables) */ /* pci_bus and pci_slot can be used to distinguish two pci boards supported by the same driver */ /* pci_bus = 0 */ /* pci_slot = 7 */ master = yes /* interface board is system controller */ } /* Now the device sections define the device characteristics for each device. * These are only used if you want to open the device using ibfind() (instead * of ibdev() ) */ device { minor = 0 name = "urv" pad = 10 sad = 0 } device { minor = 0 /* minor number for interface board this device is connected to */ name = "smg" /* device mnemonic */ pad = 28 /* The Primary Address */ sad = 0 /* Secondary Address */ eos = 0xa /* EOS Byte */ set-reos = yes /* Terminate read if EOS */ set-bin = no /* Compare EOS 8-bit */ } root@raspberrypi:/home/pi# |
From: marcello c. <ca...@fi...> - 2021-10-11 20:54:35
|
Maybe I am wrong, but at a first sight it looks like the meter address is not 10. If you are sure the address is correct, try this: sudo su echo 1 > /sys/module/gpib_bitbang/parameters/debug tail -f /var/log/kern.log Then, open another terminal, try again with ibterm, cut the output that comes from tail and send me. Make sure also that "eos = 0x0d" is the correct termination for the instrument. You might try "eos = 0x0a". Good luck Marcello On 10/11/21 8:36 PM, Dirk wrote: > Hello, > > several weeks ago i obtained a RaspberryPI GPIB Shield. > > I followed the instructions at http://elektronomikon.org/install.html > but did minor changes to get version 4.3.4 working. > > Installation went fine without any problems. > > If i try to read something from my R&S URV5 power meter nothing happend. > I get the same result with my SMG signal generator. > > Testing the system with "ibtest" (-> line status) shows unkown status of > bus lines. > > At this point i have no idea what is wrong in my setup. > > It would be great if someone can help me. > > BR > Dirk > > > > Following some additional information: > > root@raspberrypi:/home/pi# cat /etc/debian_version > 10.10 > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# uname -a > Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 > armv7l GNU/Linux > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# dmesg > [...] > [ 55.161921] gpib_common: loading out-of-tree module taints kernel. > [ 55.164358] Linux-GPIB 4.3.4 Driver > [ 55.182620] gpib: registered gpib_bitbang interface > root@raspberrypi:/home/pi# > > > root@raspberrypi:/home/pi# gpib_config -v > linux-gpib version = 4.3.4 > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# ibterm -d10 > Attempting to open /dev/gpib0 > pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 > ibterm>*IDN? > ibterm> > ibterm: Done. > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# ibtest > Do you wish to open a (d)evice or an interface (b)oard? > (you probably want to open a device): b > enter name of interface board (or device) you wish to open: violet > trying to open board named 'violet' > You can: > w(a)it for an event > [...] > send group e(x)ecute trigger (device only) > : l > DAV unknown > NDAC unknown > NRFD unknown > IFC unknown > REN unknown > SRQ unknown > ATN unknown > EOI unknown > gpib status is: > ibsta = 0x1160 < SRQI CMPL REM CIC > > iberr= 0 > > ibcntl = 0 > You can: > w(a)it for an event > [...] > send group e(x)ecute trigger (device only) > : > > > root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf > [...] > /* This section configures the configurable driver characteristics > * for an interface board, such as board address, and interrupt level. > * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, etc. > */ > > interface { > minor = 0 /* board index, minor = 0 uses /dev/gpib0, > minor = 1 uses /dev/gpib1, etc. */ > board_type = "gpib_bitbang" /* type of interface board > being used */ > name = "violet" /* optional name, allows you to get a board > descriptor using ibfind() */ > pad = 0 /* primary address of interface */ > sad = 0 /* secondary address of interface */ > timeout = T3s /* timeout for commands */ > > eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is carriage > return */ > set-reos = yes /* Terminate read if EOS */ > set-bin = no /* Compare EOS 8-bit */ > set-xeos = no /* Assert EOI whenever EOS byte is sent */ > set-eot = yes /* Assert EOI with last byte on writes */ > > /* settings for boards that lack plug-n-play capability */ > base = 0 /* Base io ADDRESS */ > irq = 0 /* Interrupt request level */ > dma = 0 /* DMA channel (zero disables) */ > > /* pci_bus and pci_slot can be used to distinguish two pci boards > supported by the same driver */ > /* pci_bus = 0 */ > /* pci_slot = 7 */ > > master = yes /* interface board is system controller */ > } > > /* Now the device sections define the device characteristics for each > device. > * These are only used if you want to open the device using ibfind() > (instead > * of ibdev() ) > */ > > device { > minor = 0 > name = "urv" > pad = 10 > sad = 0 > } > > > device { > minor = 0 /* minor number for interface board this device > is connected to */ > name = "smg" /* device mnemonic */ > pad = 28 /* The Primary Address */ > sad = 0 /* Secondary Address */ > > eos = 0xa /* EOS Byte */ > set-reos = yes /* Terminate read if EOS */ > set-bin = no /* Compare EOS 8-bit */ > } > > root@raspberrypi:/home/pi# > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general -- Marcello Carla' (ca...@fi...) |
From: Dirk <mai...@gm...> - 2021-10-11 21:33:44
|
Hi Marcello, thanks for fast reply! Device adresses are correct (they are shown on every startup). (I also tested it with "pad = 9" and "pad = 11".) Setting "eos = 0x0d" or "eos = 0x0a" equals in same result: no communication. Attached you can find my tail output: root@raspberrypi:/home/pi# tail -f /var/log/kern.log Oct 11 22:22:46 raspberrypi kernel: [ 1428.417137] gpib_bitbang:bb_request_system_control - 1 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417175] gpib_bitbang:bb_update_status - 0x20 mask 0x0 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417211] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417267] gpib_bitbang:bb_interface_clear - 1 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417398] gpib_bitbang:bb_interface_clear - 0 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417419] gpib_bitbang:bb_update_status - 0x1020 mask 0x0 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417451] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417480] gpib_bitbang:bb_remote_enable - 1 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417511] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:22:46 raspberrypi kernel: [ 1428.417544] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:01 raspberrypi kernel: [ 1443.446836] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:01 raspberrypi kernel: [ 1443.446885] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:01 raspberrypi kernel: [ 1443.446904] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:01 raspberrypi kernel: [ 1443.446936] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409562] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409603] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409625] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409660] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409679] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409710] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409734] gpib_bitbang:bb_take_control - 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409754] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409789] gpib_bitbang:bb_line_status - status lines: 6a00 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409808] gpib_bitbang:bb_command - 243f8cc3 243f8cc3 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409877] gpib_bitbang:bb_command - CMD(3): Oct 11 22:23:09 raspberrypi kernel: [ 1451.409890] gpib_bitbang:bb_command - 0x40=TLK0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409904] gpib_bitbang:bb_command - 0x3f=LSN31 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409917] gpib_bitbang:bb_command - 0x2a=LSN10 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409933] gpib_bitbang:bb_write - board 57838b64 lock 1 length: 3 Oct 11 22:23:09 raspberrypi kernel: [ 1451.409946] gpib_bitbang:bb_write - <3 > Oct 11 22:23:09 raspberrypi kernel: [ 1451.409960] gpib_bitbang:bb_write - 0 0x40->@ Oct 11 22:23:09 raspberrypi kernel: [ 1451.409973] gpib_bitbang:bb_write - 1 0x3f->? Oct 11 22:23:09 raspberrypi kernel: [ 1451.409986] gpib_bitbang:bb_write - 2 0x2a->* Oct 11 22:23:09 raspberrypi kernel: [ 1451.410042] gpib_bitbang:bb_NRFD_interrupt - 0 DAV: 1 NRFD:1 SRQ: 0 val: 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410057] gpib_bitbang:bb_write - NRFD: 1 NDAC: 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410091] gpib_bitbang:bb_write - sending 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410136] gpib_bitbang:bb_write - accepted 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410167] gpib_bitbang:bb_write - sending 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410211] gpib_bitbang:bb_write - accepted 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410242] gpib_bitbang:bb_write - sending 2 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410287] gpib_bitbang:bb_write - accepted 2 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410313] gpib_bitbang:bb_write - sent 3 bytes. Oct 11 22:23:09 raspberrypi kernel: [ 1451.410313] Oct 11 22:23:09 raspberrypi kernel: [ 1451.410350] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410383] gpib_bitbang:bb_line_status - status lines: 2800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410395] gpib_bitbang:bb_go_to_standby - Oct 11 22:23:09 raspberrypi kernel: [ 1451.410424] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410444] gpib_bitbang:bb_write - board 57838b64 lock 1 length: 5 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410458] gpib_bitbang:bb_write - <5 w.EOI> Oct 11 22:23:09 raspberrypi kernel: [ 1451.410471] gpib_bitbang:bb_write - 0 0x2a->* Oct 11 22:23:09 raspberrypi kernel: [ 1451.410484] gpib_bitbang:bb_write - 1 0x49->I Oct 11 22:23:09 raspberrypi kernel: [ 1451.410496] gpib_bitbang:bb_write - 2 0x44->D Oct 11 22:23:09 raspberrypi kernel: [ 1451.410509] gpib_bitbang:bb_write - 3 0x4e->N Oct 11 22:23:09 raspberrypi kernel: [ 1451.410522] gpib_bitbang:bb_write - 4 0x3f->? Oct 11 22:23:09 raspberrypi kernel: [ 1451.410593] gpib_bitbang:bb_write - NRFD: 1 NDAC: 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410611] gpib_bitbang:bb_write - sending 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410655] gpib_bitbang:bb_write - accepted 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410687] gpib_bitbang:bb_write - sending 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410730] gpib_bitbang:bb_write - accepted 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410765] gpib_bitbang:bb_write - sending 2 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410809] gpib_bitbang:bb_write - accepted 2 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410840] gpib_bitbang:bb_write - sending 3 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410883] gpib_bitbang:bb_write - accepted 3 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410914] gpib_bitbang:bb_write - sending 4 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410958] gpib_bitbang:bb_write - accepted 4 Oct 11 22:23:09 raspberrypi kernel: [ 1451.410983] gpib_bitbang:bb_write - sent 5 bytes. Oct 11 22:23:09 raspberrypi kernel: [ 1451.410983] Oct 11 22:23:09 raspberrypi kernel: [ 1451.411010] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411043] gpib_bitbang:bb_line_status - status lines: a800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411060] gpib_bitbang:bb_update_status - 0x1060 mask 0x1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411091] gpib_bitbang:bb_line_status - status lines: a800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411148] gpib_bitbang:bb_disable_eos - Oct 11 22:23:09 raspberrypi kernel: [ 1451.411172] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411205] gpib_bitbang:bb_line_status - status lines: a800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411223] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411254] gpib_bitbang:bb_line_status - status lines: a800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411270] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411303] gpib_bitbang:bb_line_status - status lines: a800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411326] gpib_bitbang:bb_take_control - 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411343] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411376] gpib_bitbang:bb_line_status - status lines: e800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411392] gpib_bitbang:bb_command - 243f8cc3 243f8cc3 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411459] gpib_bitbang:bb_command - CMD(3): Oct 11 22:23:09 raspberrypi kernel: [ 1451.411471] gpib_bitbang:bb_command - 0x3f=LSN31 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411484] gpib_bitbang:bb_command - 0x20=LSN0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411497] gpib_bitbang:bb_command - 0x4a=TLK10 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411511] gpib_bitbang:bb_write - board 57838b64 lock 1 length: 3 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411524] gpib_bitbang:bb_write - <3 > Oct 11 22:23:09 raspberrypi kernel: [ 1451.411538] gpib_bitbang:bb_write - 0 0x3f->? Oct 11 22:23:09 raspberrypi kernel: [ 1451.411551] gpib_bitbang:bb_write - 1 0x20-> Oct 11 22:23:09 raspberrypi kernel: [ 1451.411564] gpib_bitbang:bb_write - 2 0x4a->J Oct 11 22:23:09 raspberrypi kernel: [ 1451.411611] gpib_bitbang:bb_NRFD_interrupt - 0 DAV: 1 NRFD:1 SRQ: 0 val: 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411632] gpib_bitbang:bb_write - NRFD: 1 NDAC: 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411655] gpib_bitbang:bb_write - sending 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411698] gpib_bitbang:bb_write - accepted 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411728] gpib_bitbang:bb_write - sending 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411771] gpib_bitbang:bb_write - accepted 1 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411803] gpib_bitbang:bb_write - sending 2 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411846] gpib_bitbang:bb_write - accepted 2 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411872] gpib_bitbang:bb_write - sent 3 bytes. Oct 11 22:23:09 raspberrypi kernel: [ 1451.411872] Oct 11 22:23:09 raspberrypi kernel: [ 1451.411900] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411932] gpib_bitbang:bb_line_status - status lines: 2800 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411944] gpib_bitbang:bb_go_to_standby - Oct 11 22:23:09 raspberrypi kernel: [ 1451.411971] gpib_bitbang:bb_update_status - 0x1060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.411992] gpib_bitbang:bb_read - board: 57838b64 lock 1 length: 2048 Oct 11 22:23:09 raspberrypi kernel: [ 1451.412072] gpib_bitbang:bb_read - ..........DAV: 1 NRFD:0 SRQ: 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.728873] gpib_bitbang:bb_read - timeout - DAV: 1 NRFD:1 SRQ: 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.728890] gpib_bitbang:bb_read - got 0 bytes. Oct 11 22:23:09 raspberrypi kernel: [ 1451.728907] gpib_bitbang:bb_read - return: -110 eoi: 0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.728907] Oct 11 22:23:09 raspberrypi kernel: [ 1451.728950] gpib_bitbang:bb_update_status - 0x5060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.728983] gpib_bitbang:bb_line_status - status lines: 2a00 Oct 11 22:23:09 raspberrypi kernel: [ 1451.729002] gpib_bitbang:bb_update_status - 0x5060 mask 0x0 Oct 11 22:23:09 raspberrypi kernel: [ 1451.729035] gpib_bitbang:bb_line_status - status lines: 2a00 BR Dirk Am 11.10.2021 um 22:39 schrieb marcello carla': > Maybe I am wrong, but at a first sight it looks like > the meter address is not 10. If you are sure the address > is correct, try this: > > sudo su > echo 1 > /sys/module/gpib_bitbang/parameters/debug > tail -f /var/log/kern.log > > Then, open another terminal, try again with ibterm, > cut the output that comes from tail and send me. > > Make sure also that "eos = 0x0d" is the correct > termination for the instrument. You might try "eos = 0x0a". > > Good luck > > Marcello > > > > On 10/11/21 8:36 PM, Dirk wrote: >> Hello, >> >> several weeks ago i obtained a RaspberryPI GPIB Shield. >> >> I followed the instructions at http://elektronomikon.org/install.html >> but did minor changes to get version 4.3.4 working. >> >> Installation went fine without any problems. >> >> If i try to read something from my R&S URV5 power meter nothing happend. >> I get the same result with my SMG signal generator. >> >> Testing the system with "ibtest" (-> line status) shows unkown status of >> bus lines. >> >> At this point i have no idea what is wrong in my setup. >> >> It would be great if someone can help me. >> >> BR >> Dirk >> >> >> >> Following some additional information: >> >> root@raspberrypi:/home/pi# cat /etc/debian_version >> 10.10 >> root@raspberrypi:/home/pi# >> >> root@raspberrypi:/home/pi# uname -a >> Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 >> armv7l GNU/Linux >> root@raspberrypi:/home/pi# >> >> root@raspberrypi:/home/pi# dmesg >> [...] >> [ 55.161921] gpib_common: loading out-of-tree module taints kernel. >> [ 55.164358] Linux-GPIB 4.3.4 Driver >> [ 55.182620] gpib: registered gpib_bitbang interface >> root@raspberrypi:/home/pi# >> >> >> root@raspberrypi:/home/pi# gpib_config -v >> linux-gpib version = 4.3.4 >> root@raspberrypi:/home/pi# >> >> root@raspberrypi:/home/pi# ibterm -d10 >> Attempting to open /dev/gpib0 >> pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 >> ibterm>*IDN? >> ibterm> >> ibterm: Done. >> root@raspberrypi:/home/pi# >> >> root@raspberrypi:/home/pi# ibtest >> Do you wish to open a (d)evice or an interface (b)oard? >> (you probably want to open a device): b >> enter name of interface board (or device) you wish to open: violet >> trying to open board named 'violet' >> You can: >> w(a)it for an event >> [...] >> send group e(x)ecute trigger (device only) >> : l >> DAV unknown >> NDAC unknown >> NRFD unknown >> IFC unknown >> REN unknown >> SRQ unknown >> ATN unknown >> EOI unknown >> gpib status is: >> ibsta = 0x1160 < SRQI CMPL REM CIC > >> iberr= 0 >> >> ibcntl = 0 >> You can: >> w(a)it for an event >> [...] >> send group e(x)ecute trigger (device only) >> : >> >> >> root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf >> [...] >> /* This section configures the configurable driver characteristics >> * for an interface board, such as board address, and interrupt level. >> * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, >> etc. >> */ >> >> interface { >> minor = 0 /* board index, minor = 0 uses /dev/gpib0, >> minor = 1 uses /dev/gpib1, etc. */ >> board_type = "gpib_bitbang" /* type of interface board >> being used */ >> name = "violet" /* optional name, allows you to get a board >> descriptor using ibfind() */ >> pad = 0 /* primary address of interface */ >> sad = 0 /* secondary address of interface */ >> timeout = T3s /* timeout for commands */ >> >> eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is carriage >> return */ >> set-reos = yes /* Terminate read if EOS */ >> set-bin = no /* Compare EOS 8-bit */ >> set-xeos = no /* Assert EOI whenever EOS byte is sent */ >> set-eot = yes /* Assert EOI with last byte on writes */ >> >> /* settings for boards that lack plug-n-play capability */ >> base = 0 /* Base io ADDRESS */ >> irq = 0 /* Interrupt request level */ >> dma = 0 /* DMA channel (zero disables) */ >> >> /* pci_bus and pci_slot can be used to distinguish two pci boards >> supported by the same driver */ >> /* pci_bus = 0 */ >> /* pci_slot = 7 */ >> >> master = yes /* interface board is system controller */ >> } >> >> /* Now the device sections define the device characteristics for each >> device. >> * These are only used if you want to open the device using ibfind() >> (instead >> * of ibdev() ) >> */ >> >> device { >> minor = 0 >> name = "urv" >> pad = 10 >> sad = 0 >> } >> >> >> device { >> minor = 0 /* minor number for interface board this device >> is connected to */ >> name = "smg" /* device mnemonic */ >> pad = 28 /* The Primary Address */ >> sad = 0 /* Secondary Address */ >> >> eos = 0xa /* EOS Byte */ >> set-reos = yes /* Terminate read if EOS */ >> set-bin = no /* Compare EOS 8-bit */ >> } >> >> root@raspberrypi:/home/pi# >> >> >> _______________________________________________ >> Linux-gpib-general mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > |
From: Frank M. H. <fm...@gm...> - 2021-10-12 02:25:15
|
There really needs to be some kind of warning in the docs about the bitbang driver. Implementing ieee 488.2 with software driven dio lines has no chance of meeting the standard's timing requirements. Which is a relatively minor complaint, considering the bitbang driver makes no serious attempt to implement the behavior required by the protocol's state machines. On Mon, Oct 11, 2021, 16:55 marcello carla' <ca...@fi...> wrote: > Maybe I am wrong, but at a first sight it looks like > the meter address is not 10. If you are sure the address > is correct, try this: > > sudo su > echo 1 > /sys/module/gpib_bitbang/parameters/debug > tail -f /var/log/kern.log > > Then, open another terminal, try again with ibterm, > cut the output that comes from tail and send me. > > Make sure also that "eos = 0x0d" is the correct > termination for the instrument. You might try "eos = 0x0a". > > Good luck > > Marcello > > > > On 10/11/21 8:36 PM, Dirk wrote: > > Hello, > > > > several weeks ago i obtained a RaspberryPI GPIB Shield. > > > > I followed the instructions at http://elektronomikon.org/install.html > > but did minor changes to get version 4.3.4 working. > > > > Installation went fine without any problems. > > > > If i try to read something from my R&S URV5 power meter nothing happend. > > I get the same result with my SMG signal generator. > > > > Testing the system with "ibtest" (-> line status) shows unkown status of > > bus lines. > > > > At this point i have no idea what is wrong in my setup. > > > > It would be great if someone can help me. > > > > BR > > Dirk > > > > > > > > Following some additional information: > > > > root@raspberrypi:/home/pi# cat /etc/debian_version > > 10.10 > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# uname -a > > Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 > > armv7l GNU/Linux > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# dmesg > > [...] > > [ 55.161921] gpib_common: loading out-of-tree module taints kernel. > > [ 55.164358] Linux-GPIB 4.3.4 Driver > > [ 55.182620] gpib: registered gpib_bitbang interface > > root@raspberrypi:/home/pi# > > > > > > root@raspberrypi:/home/pi# gpib_config -v > > linux-gpib version = 4.3.4 > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# ibterm -d10 > > Attempting to open /dev/gpib0 > > pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 > > ibterm>*IDN? > > ibterm> > > ibterm: Done. > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# ibtest > > Do you wish to open a (d)evice or an interface (b)oard? > > (you probably want to open a device): b > > enter name of interface board (or device) you wish to open: violet > > trying to open board named 'violet' > > You can: > > w(a)it for an event > > [...] > > send group e(x)ecute trigger (device only) > > : l > > DAV unknown > > NDAC unknown > > NRFD unknown > > IFC unknown > > REN unknown > > SRQ unknown > > ATN unknown > > EOI unknown > > gpib status is: > > ibsta = 0x1160 < SRQI CMPL REM CIC > > > iberr= 0 > > > > ibcntl = 0 > > You can: > > w(a)it for an event > > [...] > > send group e(x)ecute trigger (device only) > > : > > > > > > root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf > > [...] > > /* This section configures the configurable driver characteristics > > * for an interface board, such as board address, and interrupt level. > > * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, > etc. > > */ > > > > interface { > > minor = 0 /* board index, minor = 0 uses /dev/gpib0, > > minor = 1 uses /dev/gpib1, etc. */ > > board_type = "gpib_bitbang" /* type of interface board > > being used */ > > name = "violet" /* optional name, allows you to get a board > > descriptor using ibfind() */ > > pad = 0 /* primary address of interface */ > > sad = 0 /* secondary address of interface */ > > timeout = T3s /* timeout for commands */ > > > > eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is carriage > > return */ > > set-reos = yes /* Terminate read if EOS */ > > set-bin = no /* Compare EOS 8-bit */ > > set-xeos = no /* Assert EOI whenever EOS byte is sent */ > > set-eot = yes /* Assert EOI with last byte on writes */ > > > > /* settings for boards that lack plug-n-play capability */ > > base = 0 /* Base io ADDRESS */ > > irq = 0 /* Interrupt request level */ > > dma = 0 /* DMA channel (zero disables) */ > > > > /* pci_bus and pci_slot can be used to distinguish two pci boards > > supported by the same driver */ > > /* pci_bus = 0 */ > > /* pci_slot = 7 */ > > > > master = yes /* interface board is system controller */ > > } > > > > /* Now the device sections define the device characteristics for each > > device. > > * These are only used if you want to open the device using ibfind() > > (instead > > * of ibdev() ) > > */ > > > > device { > > minor = 0 > > name = "urv" > > pad = 10 > > sad = 0 > > } > > > > > > device { > > minor = 0 /* minor number for interface board this device > > is connected to */ > > name = "smg" /* device mnemonic */ > > pad = 28 /* The Primary Address */ > > sad = 0 /* Secondary Address */ > > > > eos = 0xa /* EOS Byte */ > > set-reos = yes /* Terminate read if EOS */ > > set-bin = no /* Compare EOS 8-bit */ > > } > > > > root@raspberrypi:/home/pi# > > > > > > _______________________________________________ > > Linux-gpib-general mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > -- > Marcello Carla' > (ca...@fi...) > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > |
From: Thomas K. <ele...@gm...> - 2021-10-12 11:42:51
|
Hello, On Mon, 11 Oct 2021 22:24:54 -0400 Frank Mori Hess <fm...@gm...> wrote: > There really needs to be some kind of warning in the docs about the > bitbang driver. Implementing ieee 488.2 with software driven dio > lines has no chance of meeting the standard's timing requirements. indeed - i'll update the documentation and try to gather some numbers on the (worst case) timings to see where the limits are. > Which is a relatively minor complaint, considering the bitbang driver > makes no serious attempt to implement the behavior required by the > protocol's state machines. Also true :-/ Thanks for tuning in, Thomas > On Mon, Oct 11, 2021, 16:55 marcello carla' <ca...@fi...> wrote: > > > Maybe I am wrong, but at a first sight it looks like > > the meter address is not 10. If you are sure the address > > is correct, try this: > > > > sudo su > > echo 1 > /sys/module/gpib_bitbang/parameters/debug > > tail -f /var/log/kern.log > > > > Then, open another terminal, try again with ibterm, > > cut the output that comes from tail and send me. > > > > Make sure also that "eos = 0x0d" is the correct > > termination for the instrument. You might try "eos = 0x0a". > > > > Good luck > > > > Marcello > > > > > > > > On 10/11/21 8:36 PM, Dirk wrote: > > > Hello, > > > > > > several weeks ago i obtained a RaspberryPI GPIB Shield. > > > > > > I followed the instructions at > > > http://elektronomikon.org/install.html but did minor changes to > > > get version 4.3.4 working. > > > > > > Installation went fine without any problems. > > > > > > If i try to read something from my R&S URV5 power meter nothing > > > happend. I get the same result with my SMG signal generator. > > > > > > Testing the system with "ibtest" (-> line status) shows unkown > > > status of bus lines. > > > > > > At this point i have no idea what is wrong in my setup. > > > > > > It would be great if someone can help me. > > > > > > BR > > > Dirk > > > > > > > > > > > > Following some additional information: > > > > > > root@raspberrypi:/home/pi# cat /etc/debian_version > > > 10.10 > > > root@raspberrypi:/home/pi# > > > > > > root@raspberrypi:/home/pi# uname -a > > > Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST > > > 2021 armv7l GNU/Linux > > > root@raspberrypi:/home/pi# > > > > > > root@raspberrypi:/home/pi# dmesg > > > [...] > > > [ 55.161921] gpib_common: loading out-of-tree module taints > > > kernel. [ 55.164358] Linux-GPIB 4.3.4 Driver > > > [ 55.182620] gpib: registered gpib_bitbang interface > > > root@raspberrypi:/home/pi# > > > > > > > > > root@raspberrypi:/home/pi# gpib_config -v > > > linux-gpib version = 4.3.4 > > > root@raspberrypi:/home/pi# > > > > > > root@raspberrypi:/home/pi# ibterm -d10 > > > Attempting to open /dev/gpib0 > > > pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 > > > ibterm>*IDN? > > > ibterm> > > > ibterm: Done. > > > root@raspberrypi:/home/pi# > > > > > > root@raspberrypi:/home/pi# ibtest > > > Do you wish to open a (d)evice or an interface (b)oard? > > > (you probably want to open a device): b > > > enter name of interface board (or device) you wish to open: violet > > > trying to open board named 'violet' > > > You can: > > > w(a)it for an event > > > [...] > > > send group e(x)ecute trigger (device only) > > > : l > > > DAV unknown > > > NDAC unknown > > > NRFD unknown > > > IFC unknown > > > REN unknown > > > SRQ unknown > > > ATN unknown > > > EOI unknown > > > gpib status is: > > > ibsta = 0x1160 < SRQI CMPL REM CIC > > > > iberr= 0 > > > > > > ibcntl = 0 > > > You can: > > > w(a)it for an event > > > [...] > > > send group e(x)ecute trigger (device only) > > > : > > > > > > > > > root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf > > > [...] > > > /* This section configures the configurable driver characteristics > > > * for an interface board, such as board address, and interrupt > > > level. > > > * minor = 0 configures /dev/gpib0, minor = 1 configures > > > /dev/gpib1, > > etc. > > > */ > > > > > > interface { > > > minor = 0 /* board index, minor = 0 uses > > > /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */ > > > board_type = "gpib_bitbang" /* type of interface > > > board being used */ > > > name = "violet" /* optional name, allows you to get a > > > board descriptor using ibfind() */ > > > pad = 0 /* primary address of interface */ > > > sad = 0 /* secondary address of interface */ > > > timeout = T3s /* timeout for commands */ > > > > > > eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is > > > carriage return */ > > > set-reos = yes /* Terminate read if EOS */ > > > set-bin = no /* Compare EOS 8-bit */ > > > set-xeos = no /* Assert EOI whenever EOS byte is sent > > > */ set-eot = yes /* Assert EOI with last byte on writes */ > > > > > > /* settings for boards that lack plug-n-play capability */ > > > base = 0 /* Base io ADDRESS */ > > > irq = 0 /* Interrupt request level */ > > > dma = 0 /* DMA channel (zero disables) */ > > > > > > /* pci_bus and pci_slot can be used to distinguish two pci boards > > > supported by the same driver */ > > > /* pci_bus = 0 */ > > > /* pci_slot = 7 */ > > > > > > master = yes /* interface board is system controller > > > */ } > > > > > > /* Now the device sections define the device characteristics for > > > each device. > > > * These are only used if you want to open the device using > > > ibfind() (instead > > > * of ibdev() ) > > > */ > > > > > > device { > > > minor = 0 > > > name = "urv" > > > pad = 10 > > > sad = 0 > > > } > > > > > > > > > device { > > > minor = 0 /* minor number for interface board this > > > device is connected to */ > > > name = "smg" /* device mnemonic */ > > > pad = 28 /* The Primary Address */ > > > sad = 0 /* Secondary Address */ > > > > > > eos = 0xa /* EOS Byte */ > > > set-reos = yes /* Terminate read if EOS */ > > > set-bin = no /* Compare EOS 8-bit */ > > > } > > > > > > root@raspberrypi:/home/pi# > > > > > > > > > _______________________________________________ > > > Linux-gpib-general mailing list > > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > > > -- > > Marcello Carla' > > (ca...@fi...) > > > > > > _______________________________________________ > > Linux-gpib-general mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > |
From: marcello c. <ca...@fi...> - 2021-10-12 10:06:43
|
Frank's remark is very serious. There is some timing in the gpib standard a software driver cannot cope with. It may be that the URV5 is one such case. But many devices, especially vintage devices, do work quite well. Before giving up it is worth to make a few tests: 1) Browsing the URV5 user manual, I did not find the *IDN? among the recognized command. If this is the case, no surprise there is no response. Many devices that do not follow SCPI ignore the *IDN?. May Dirk try some other command? 2) Sure 100% that the gpib shell is working properly? Might it be tested with some other devices? Otherwise, it is also possible to connect the gpib bus directly to the raspberry gpios, without the shell (with limited fanout; no more than 4 or 5 devices). The pin to pin correspondence table (from the source code) is: /********************************************** * Signal pairing and pin wiring between the * * Raspberry-Pi connector and the GPIB bus * * * * signal pin wiring * * GPIB Pi-gpio GPIB -> RPi * **********************************************/ typedef enum { D01_pin_nr = 20, /* 1 -> 38 */ D02_pin_nr = 26, /* 2 -> 37 */ D03_pin_nr = 16, /* 3 -> 36 */ D04_pin_nr = 19, /* 4 -> 35 */ D05_pin_nr = 13, /* 13 -> 33 */ D06_pin_nr = 12, /* 14 -> 32 */ D07_pin_nr = 6, /* 15 -> 31 */ D08_pin_nr = 5, /* 16 -> 29 */ EOI_pin_nr = 9, /* 5 -> 21 */ DAV_pin_nr = 10, /* 6 -> 19 */ NRFD_pin_nr = 24, /* 7 -> 18 */ NDAC_pin_nr = 23, /* 8 -> 16 */ IFC_pin_nr = 22, /* 9 -> 15 */ SRQ_pin_nr = 11, /* 10 -> 23 */ _ATN_pin_nr = 25, /* 11 -> 22 */ REN_pin_nr = 27, /* 17 -> 13 */ /* * GROUND PINS * 12,18,19,20,21,22,23,24 => 14,20,25,30,34,39 */ Marcello On 10/12/21 4:24 AM, Frank Mori Hess wrote: > There really needs to be some kind of warning in the docs about the > bitbang driver. Implementing ieee 488.2 with software driven dio lines > has no chance of meeting the standard's timing requirements. Which is a > relatively minor complaint, considering the bitbang driver makes no > serious attempt to implement the behavior required by the protocol's > state machines. > > On Mon, Oct 11, 2021, 16:55 marcello carla' <ca...@fi... > <mailto:ca...@fi...>> wrote: > > Maybe I am wrong, but at a first sight it looks like > the meter address is not 10. If you are sure the address > is correct, try this: > > sudo su > echo 1 > /sys/module/gpib_bitbang/parameters/debug > tail -f /var/log/kern.log > > Then, open another terminal, try again with ibterm, > cut the output that comes from tail and send me. > > Make sure also that "eos = 0x0d" is the correct > termination for the instrument. You might try "eos = 0x0a". > > Good luck > > Marcello > > > > On 10/11/21 8:36 PM, Dirk wrote: > > Hello, > > > > several weeks ago i obtained a RaspberryPI GPIB Shield. > > > > I followed the instructions at http://elektronomikon.org/install.html > > but did minor changes to get version 4.3.4 working. > > > > Installation went fine without any problems. > > > > If i try to read something from my R&S URV5 power meter nothing > happend. > > I get the same result with my SMG signal generator. > > > > Testing the system with "ibtest" (-> line status) shows unkown > status of > > bus lines. > > > > At this point i have no idea what is wrong in my setup. > > > > It would be great if someone can help me. > > > > BR > > Dirk > > > > > > > > Following some additional information: > > > > root@raspberrypi:/home/pi# cat /etc/debian_version > > 10.10 > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# uname -a > > Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 > > armv7l GNU/Linux > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# dmesg > > [...] > > [ 55.161921] gpib_common: loading out-of-tree module taints kernel. > > [ 55.164358] Linux-GPIB 4.3.4 Driver > > [ 55.182620] gpib: registered gpib_bitbang interface > > root@raspberrypi:/home/pi# > > > > > > root@raspberrypi:/home/pi# gpib_config -v > > linux-gpib version = 4.3.4 > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# ibterm -d10 > > Attempting to open /dev/gpib0 > > pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 > > ibterm>*IDN? > > ibterm> > > ibterm: Done. > > root@raspberrypi:/home/pi# > > > > root@raspberrypi:/home/pi# ibtest > > Do you wish to open a (d)evice or an interface (b)oard? > > (you probably want to open a device): b > > enter name of interface board (or device) you wish to open: violet > > trying to open board named 'violet' > > You can: > > w(a)it for an event > > [...] > > send group e(x)ecute trigger (device only) > > : l > > DAV unknown > > NDAC unknown > > NRFD unknown > > IFC unknown > > REN unknown > > SRQ unknown > > ATN unknown > > EOI unknown > > gpib status is: > > ibsta = 0x1160 < SRQI CMPL REM CIC > > > iberr= 0 > > > > ibcntl = 0 > > You can: > > w(a)it for an event > > [...] > > send group e(x)ecute trigger (device only) > > : > > > > > > root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf > > [...] > > /* This section configures the configurable driver characteristics > > * for an interface board, such as board address, and interrupt > level. > > * minor = 0 configures /dev/gpib0, minor = 1 configures > /dev/gpib1, etc. > > */ > > > > interface { > > minor = 0 /* board index, minor = 0 uses /dev/gpib0, > > minor = 1 uses /dev/gpib1, etc. */ > > board_type = "gpib_bitbang" /* type of interface board > > being used */ > > name = "violet" /* optional name, allows you to get a board > > descriptor using ibfind() */ > > pad = 0 /* primary address of interface */ > > sad = 0 /* secondary address of interface */ > > timeout = T3s /* timeout for commands */ > > > > eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is > carriage > > return */ > > set-reos = yes /* Terminate read if EOS */ > > set-bin = no /* Compare EOS 8-bit */ > > set-xeos = no /* Assert EOI whenever EOS byte is sent */ > > set-eot = yes /* Assert EOI with last byte on writes */ > > > > /* settings for boards that lack plug-n-play capability */ > > base = 0 /* Base io ADDRESS */ > > irq = 0 /* Interrupt request level */ > > dma = 0 /* DMA channel (zero disables) */ > > > > /* pci_bus and pci_slot can be used to distinguish two pci boards > > supported by the same driver */ > > /* pci_bus = 0 */ > > /* pci_slot = 7 */ > > > > master = yes /* interface board is system controller */ > > } > > > > /* Now the device sections define the device characteristics for each > > device. > > * These are only used if you want to open the device using ibfind() > > (instead > > * of ibdev() ) > > */ > > > > device { > > minor = 0 > > name = "urv" > > pad = 10 > > sad = 0 > > } > > > > > > device { > > minor = 0 /* minor number for interface board this > device > > is connected to */ > > name = "smg" /* device mnemonic */ > > pad = 28 /* The Primary Address */ > > sad = 0 /* Secondary Address */ > > > > eos = 0xa /* EOS Byte */ > > set-reos = yes /* Terminate read if EOS */ > > set-bin = no /* Compare EOS 8-bit */ > > } > > > > root@raspberrypi:/home/pi# > > > > > > _______________________________________________ > > Linux-gpib-general mailing list > > Lin...@li... > <mailto:Lin...@li...> > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > -- > Marcello Carla' > (ca...@fi... <mailto:ca...@fi...>) > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > <mailto:Lin...@li...> > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > -- Marcello Carla' (ca...@fi...) |
From: Dirk <mai...@gm...> - 2021-10-14 18:40:18
|
Hello, Am 12.10.2021 um 12:06 schrieb marcello carla': > [...] > > 1) Browsing the URV5 user manual, I did not find the *IDN? among > the recognized command. If this is the case, no surprise there is > no response. Many devices that do not follow SCPI ignore the *IDN?. > May Dirk try some other command? Indeed that was a fault by me. The URV5 don´t know "*IDN?". I didn´t checked it before because i thought that every GPIB device support this command. So i tried some other commands out of the manual but with the same result. Next week i try to borrow an HP/Agilent device from work and test it. > > 2) Sure 100% that the gpib shell is working properly? Might it be > tested with some other devices? Otherwise, it is also possible to > connect the gpib bus directly to the raspberry gpios, without the > shell (with limited fanout; no more than 4 or 5 devices). The pin > to pin correspondence table (from the source code) is: > [...] Not 100% at all but nearly 99% ;-) I will try to rewire it on sunday! Thanks all of you for your help. BR Dirk > > > On 10/12/21 4:24 AM, Frank Mori Hess wrote: >> There really needs to be some kind of warning in the docs about the >> bitbang driver. Implementing ieee 488.2 with software driven dio >> lines has no chance of meeting the standard's timing requirements. >> Which is a relatively minor complaint, considering the bitbang driver >> makes no serious attempt to implement the behavior required by the >> protocol's state machines. >> >> On Mon, Oct 11, 2021, 16:55 marcello carla' <ca...@fi... >> <mailto:ca...@fi...>> wrote: >> >> Maybe I am wrong, but at a first sight it looks like >> the meter address is not 10. If you are sure the address >> is correct, try this: >> >> sudo su >> echo 1 > /sys/module/gpib_bitbang/parameters/debug >> tail -f /var/log/kern.log >> >> Then, open another terminal, try again with ibterm, >> cut the output that comes from tail and send me. >> >> Make sure also that "eos = 0x0d" is the correct >> termination for the instrument. You might try "eos = 0x0a". >> >> Good luck >> >> Marcello >> >> >> >> On 10/11/21 8:36 PM, Dirk wrote: >> > Hello, >> > >> > several weeks ago i obtained a RaspberryPI GPIB Shield. >> > >> > I followed the instructions at >> http://elektronomikon.org/install.html >> > but did minor changes to get version 4.3.4 working. >> > >> > Installation went fine without any problems. >> > >> > If i try to read something from my R&S URV5 power meter nothing >> happend. >> > I get the same result with my SMG signal generator. >> > >> > Testing the system with "ibtest" (-> line status) shows unkown >> status of >> > bus lines. >> > >> > At this point i have no idea what is wrong in my setup. >> > >> > It would be great if someone can help me. >> > >> > BR >> > Dirk >> > >> > >> > >> > Following some additional information: >> > >> > root@raspberrypi:/home/pi# cat /etc/debian_version >> > 10.10 >> > root@raspberrypi:/home/pi# >> > >> > root@raspberrypi:/home/pi# uname -a >> > Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST >> 2021 >> > armv7l GNU/Linux >> > root@raspberrypi:/home/pi# >> > >> > root@raspberrypi:/home/pi# dmesg >> > [...] >> > [ 55.161921] gpib_common: loading out-of-tree module taints >> kernel. >> > [ 55.164358] Linux-GPIB 4.3.4 Driver >> > [ 55.182620] gpib: registered gpib_bitbang interface >> > root@raspberrypi:/home/pi# >> > >> > >> > root@raspberrypi:/home/pi# gpib_config -v >> > linux-gpib version = 4.3.4 >> > root@raspberrypi:/home/pi# >> > >> > root@raspberrypi:/home/pi# ibterm -d10 >> > Attempting to open /dev/gpib0 >> > pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 >> > ibterm>*IDN? >> > ibterm> >> > ibterm: Done. >> > root@raspberrypi:/home/pi# >> > >> > root@raspberrypi:/home/pi# ibtest >> > Do you wish to open a (d)evice or an interface (b)oard? >> > (you probably want to open a device): b >> > enter name of interface board (or device) you wish to open: violet >> > trying to open board named 'violet' >> > You can: >> > w(a)it for an event >> > [...] >> > send group e(x)ecute trigger (device only) >> > : l >> > DAV unknown >> > NDAC unknown >> > NRFD unknown >> > IFC unknown >> > REN unknown >> > SRQ unknown >> > ATN unknown >> > EOI unknown >> > gpib status is: >> > ibsta = 0x1160 < SRQI CMPL REM CIC > >> > iberr= 0 >> > >> > ibcntl = 0 >> > You can: >> > w(a)it for an event >> > [...] >> > send group e(x)ecute trigger (device only) >> > : >> > >> > >> > root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf >> > [...] >> > /* This section configures the configurable driver characteristics >> > * for an interface board, such as board address, and interrupt >> level. >> > * minor = 0 configures /dev/gpib0, minor = 1 configures >> /dev/gpib1, etc. >> > */ >> > >> > interface { >> > minor = 0 /* board index, minor = 0 uses >> /dev/gpib0, >> > minor = 1 uses /dev/gpib1, etc. */ >> > board_type = "gpib_bitbang" /* type of interface >> board >> > being used */ >> > name = "violet" /* optional name, allows you to get a >> board >> > descriptor using ibfind() */ >> > pad = 0 /* primary address of interface */ >> > sad = 0 /* secondary address of interface */ >> > timeout = T3s /* timeout for commands */ >> > >> > eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is >> carriage >> > return */ >> > set-reos = yes /* Terminate read if EOS */ >> > set-bin = no /* Compare EOS 8-bit */ >> > set-xeos = no /* Assert EOI whenever EOS byte is >> sent */ >> > set-eot = yes /* Assert EOI with last byte on writes */ >> > >> > /* settings for boards that lack plug-n-play capability */ >> > base = 0 /* Base io ADDRESS */ >> > irq = 0 /* Interrupt request level */ >> > dma = 0 /* DMA channel (zero disables) */ >> > >> > /* pci_bus and pci_slot can be used to distinguish two pci boards >> > supported by the same driver */ >> > /* pci_bus = 0 */ >> > /* pci_slot = 7 */ >> > >> > master = yes /* interface board is system >> controller */ >> > } >> > >> > /* Now the device sections define the device characteristics >> for each >> > device. >> > * These are only used if you want to open the device using >> ibfind() >> > (instead >> > * of ibdev() ) >> > */ >> > >> > device { >> > minor = 0 >> > name = "urv" >> > pad = 10 >> > sad = 0 >> > } >> > >> > >> > device { >> > minor = 0 /* minor number for interface board this >> device >> > is connected to */ >> > name = "smg" /* device mnemonic */ >> > pad = 28 /* The Primary Address */ >> > sad = 0 /* Secondary Address */ >> > >> > eos = 0xa /* EOS Byte */ >> > set-reos = yes /* Terminate read if EOS */ >> > set-bin = no /* Compare EOS 8-bit */ >> > } >> > >> > root@raspberrypi:/home/pi# >> > >> > >> > _______________________________________________ >> > Linux-gpib-general mailing list >> > Lin...@li... >> <mailto:Lin...@li...> >> > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general >> >> -- Marcello Carla' >> (ca...@fi... <mailto:ca...@fi...>) >> >> >> _______________________________________________ >> Linux-gpib-general mailing list >> Lin...@li... >> <mailto:Lin...@li...> >> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general >> >> >> >> _______________________________________________ >> Linux-gpib-general mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general >> > |
From: Thomas K. <ele...@gm...> - 2021-10-12 11:32:01
|
Hi Dirk, i'm sorry to hear the problem persists. To rule out any hardware issues, could you please send me pictures of the shield from top and bottom directly (off-list)? Greetings, Thomas On Mon, 11 Oct 2021 20:36:08 +0200 Dirk <mai...@gm...> wrote: > Hello, > > several weeks ago i obtained a RaspberryPI GPIB Shield. > > I followed the instructions at http://elektronomikon.org/install.html > but did minor changes to get version 4.3.4 working. > > Installation went fine without any problems. > > If i try to read something from my R&S URV5 power meter nothing > happend. I get the same result with my SMG signal generator. > > Testing the system with "ibtest" (-> line status) shows unkown status > of bus lines. > > At this point i have no idea what is wrong in my setup. > > It would be great if someone can help me. > > BR > Dirk > > > > Following some additional information: > > root@raspberrypi:/home/pi# cat /etc/debian_version > 10.10 > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# uname -a > Linux raspberrypi 5.10.60-v7+ #1449 SMP Wed Aug 25 15:00:01 BST 2021 > armv7l GNU/Linux > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# dmesg > [...] > [ 55.161921] gpib_common: loading out-of-tree module taints kernel. > [ 55.164358] Linux-GPIB 4.3.4 Driver > [ 55.182620] gpib: registered gpib_bitbang interface > root@raspberrypi:/home/pi# > > > root@raspberrypi:/home/pi# gpib_config -v > linux-gpib version = 4.3.4 > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# ibterm -d10 > Attempting to open /dev/gpib0 > pad = 10, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000 > ibterm>*IDN? > ibterm> > ibterm: Done. > root@raspberrypi:/home/pi# > > root@raspberrypi:/home/pi# ibtest > Do you wish to open a (d)evice or an interface (b)oard? > (you probably want to open a device): b > enter name of interface board (or device) you wish to open: violet > trying to open board named 'violet' > You can: > w(a)it for an event > [...] > send group e(x)ecute trigger (device only) > : l > DAV unknown > NDAC unknown > NRFD unknown > IFC unknown > REN unknown > SRQ unknown > ATN unknown > EOI unknown > gpib status is: > ibsta = 0x1160 < SRQI CMPL REM CIC > > iberr= 0 > > ibcntl = 0 > You can: > w(a)it for an event > [...] > send group e(x)ecute trigger (device only) > : > > > root@raspberrypi:/home/pi# cat /usr/local/etc/gpib.conf > [...] > /* This section configures the configurable driver characteristics > * for an interface board, such as board address, and interrupt > level. > * minor = 0 configures /dev/gpib0, minor = 1 configures /dev/gpib1, > etc. */ > > interface { > minor = 0 /* board index, minor = 0 uses /dev/gpib0, > minor = 1 uses /dev/gpib1, etc. */ > board_type = "gpib_bitbang" /* type of interface board > being used */ > name = "violet" /* optional name, allows you to get a board > descriptor using ibfind() */ > pad = 0 /* primary address of interface */ > sad = 0 /* secondary address of interface */ > timeout = T3s /* timeout for commands */ > > eos = 0x0d /* EOS Byte, 0xa is newline and 0xd is > carriage return */ > set-reos = yes /* Terminate read if EOS */ > set-bin = no /* Compare EOS 8-bit */ > set-xeos = no /* Assert EOI whenever EOS byte is sent */ > set-eot = yes /* Assert EOI with last byte on writes */ > > /* settings for boards that lack plug-n-play capability */ > base = 0 /* Base io ADDRESS */ > irq = 0 /* Interrupt request level */ > dma = 0 /* DMA channel (zero disables) */ > > /* pci_bus and pci_slot can be used to distinguish two pci boards > supported by the same driver */ > /* pci_bus = 0 */ > /* pci_slot = 7 */ > > master = yes /* interface board is system controller */ > } > > /* Now the device sections define the device characteristics for each > device. > * These are only used if you want to open the device using ibfind() > (instead > * of ibdev() ) > */ > > device { > minor = 0 > name = "urv" > pad = 10 > sad = 0 > } > > > device { > minor = 0 /* minor number for interface board this > device is connected to */ > name = "smg" /* device mnemonic */ > pad = 28 /* The Primary Address */ > sad = 0 /* Secondary Address */ > > eos = 0xa /* EOS Byte */ > set-reos = yes /* Terminate read if EOS */ > set-bin = no /* Compare EOS 8-bit */ > } > > root@raspberrypi:/home/pi# > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general |