Re: Problems with Electronomikon gpib_bitbang

"marcello.carla" <[email protected]> Tue, 21 Feb 2023 15:26:50 +0100
Newsgroups gmane.linux.hardware.gpib.general
Message-ID <[email protected]>
Dear Chris,

the debug can be activated with:

sudo modprobe gpib_bitbang debug=1

or, if the module is already running:

sudo su
echo 1 > /sys/module/gpib_bitbang/parameters/debug
Ctrl-D

Use 2 or 3 instead of 1 for a higher debug level;
0 to disable.

Let me know and good luck

Marcello




On 2/21/23 12:42 PM, quips_roofing.0t--- via Linux-gpib-general wrote:
> Hi all,
> I’m having trouble getting any results using a electronomikon GPIB hat on a Pi. I have tried two different interface boards, two different Pis (a Pi3 and Pi4), different devices and different cables. I figure the problem is therefore with my driver setup or commands.
>
> I’m running the r2048 branch, locally compiled.
>
> My /usr/local/etc/gpib.conf  config file is -
>
> <code>
>
> interface {
> 	minor = 0			/* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */
> 	board_type = "gpib_bitbang"	/* name of the driver */
> 	name = "raspi_gpio_interface"	/* optional name, allows you to get a board descriptor using ibfind() */
> 	pad = 0				/* primary address of interface             */
> 	sad = 0				/* secondary address of interface           */
> 	eos = 0x0a	/* 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 */
> 	timeout = T30s
> /* 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)      */
>
> 	master = yes	/* interface board is system controller */
> }
>
>
> device {
> 	minor = 0
>       name = "SolartronDMM"
>       pad = 7
>       eos = 0x0a
>       set-reos = yes
>       set-bin = no
> 	timeout = T30s
> }
>
> </code>
>
> Syslog shows driver loading -
> <code>
> Feb 21 21:40:22 GPIB01 kernel: [   64.307958] gpib_common: loading out-of-tree module taints kernel.
> Feb 21 21:40:22 GPIB01 kernel: [   64.310725] Linux-GPIB 4.3.5 Driver
> Feb 21 21:40:22 GPIB01 kernel: [   64.336055] gpib: registered gpib_bitbang interface
> Feb 21 21:40:22 GPIB01 kernel: [   64.336083] gpib_bitbang:bb_init_module - module loaded with pin map "elektronomikon" and SN7516x driver support
> Feb 21 21:40:36 GPIB01 kernel: [   78.563879] gpib_bitbang:bb_attach - Using pin map "elektronomikon"  with SN7516x driver support
> Feb 21 21:40:36 GPIB01 kernel: [   78.564627] gpib_bitbang:bb_attach - attached board: 0
> </code>
>
> Using the glib utility -
> <code>
>
> sudo modprobe gpib_bitbang sn7516x_used=1
>
> pi@GPIB01:~ $ sudo ibterm -d 7 -e 10 -r 1 -N -i -x
>
> Attempting to open /dev/gpib0
> pad = 7, sad = 0, timeout = 10, send_eoi = 0, eos_mode = 0x040a
> ibterm>*IDN?
> ibterm error: Unable to write to device at pad 7
>
> - ENOL 2: No listeners
> ibterm>
> InternalReceiveSetup: command failed
> ibterm error: Failed during read from device at pad 7
>
> - ENOL 2: No listeners
>
> </code>
>
> Device is currently a solartron 7150 multimeter but have used other miscellaneous HP equipment as well. Device confirms its address is 7 on startup.
>
> I’ve also attempted a basic
>
> interm -d 7
>
> Both LEDs on the board are illuminated but neither change during commanding.
>
> Any advice as to how to debug? Am I using the correct EOS mode?
>
> Thanks,
> Chris
>
> _______________________________________________
> Linux-gpib-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general



_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general