Raspberry Pi2/3 logging platform for Voltnuts

[BFX]

Not enough place (RPi 2 B+,7" LCD, Agilent 82357B, Bluetooth kbrd and mouse )
It's not working for now with Agilent 82357B, but it's only few minutes from start. (tuning is in progress)
Funny moment's with this keyboard (it is shit) (how to put the #? ou yes ctrl + alt + u and 23 )

That message seems more like one or both of these:

1: gpib_config has not been run, after the adapter initialization.
2: User has no access to /dev/gpib0  - Do a : sudo chmod 666 /dev/gpib*

What does a lsusb say ?

What does a uname -a say ?

/Bingo

thx for hints
there is no gpib in dev

[plesa]

Not enough place (RPi 2 B+,7" LCD, Agilent 82357B, Bluetooth kbrd and mouse )
It's not working for now with Agilent 82357B, but it's only few minutes from start. (tuning is in progress)
Funny moment's with this keyboard (it is shit) (how to put the #? ou yes ctrl + alt + u and 23 )

That message seems more like one or both of these:

1: gpib_config has not been run, after the adapter initialization.
2: User has no access to /dev/gpib0  - Do a : sudo chmod 666 /dev/gpib*

What does a lsusb say ?

What does a uname -a say ?

/Bingo

thx for hints
there is no gpib in dev

You do not have firmware in device loaded. With loaded FW PID will be not 518 but 718. But anyway, this interface is not currently working. You needs to use USBTMC, VXI
 or another proven adapters like NI GPIB USB HS, NI GPIB USB B, E5810 A/B.

[bingo600]

thx for hints
there is no gpib in dev

As Plesa says , you need to load the firmware twice.

And have you loaded the kernel module module ?

You should see this

If "lsmod |grep agilent" shows these two lines:
pi@pi3:~ $ lsmod |grep agilent
agilent_82357a         18039  0
gpib_common            31540  1 agilent_82357a

If not , what does : sudo modprobe agilent_82357a           say ?

Does the lsmod show the module loaded after this ??

/Bingo

[BFX]

Thank you guys 
@plesa : are you sure that this doesn't work at all? I have original one.

After loading firmware twice I got gpib0-15 in dev.
And on the adapter Access and Ready lights to green, but also Fail led is on (red). See pictures.

Code: [Select]

pi@raspberrypi:~ $ lsmod |grep agilent
agilent_82357a         18039  0
gpib_common            31540  1 agilent_82357a

result of lsmod

[TiN]

What lsusb and modprobe results?

[BFX]

pi@raspberrypi:~ $ lsmod |grep agilent
agilent_82357a         18039  0
gpib_common            31540  1 agilent_82357a

Code: [Select]

pi@raspberrypi:~ $ modprobe agilent_82357a
pi@raspberrypi:~ $ lsmod
Module                  Size  Used by
agilent_82357a         18039  0
gpib_common            31540  1 agilent_82357a
bnep                   10340  2
8192cu                560049  0
cfg80211              427855  1 8192cu
btusb                  27628  0
btrtl                   3667  1 btusb
btintel                 6167  1 btusb
btbcm                   5929  1 btusb
bluetooth             326105  24 bnep,btbcm,btrtl,btusb,btintel
rfkill                 16037  4 cfg80211,bluetooth
evdev                  11396  2
joydev                  9024  0
snd_bcm2835            20447  1
snd_pcm                75762  1 snd_bcm2835
snd_timer              19288  1 snd_pcm
snd                    51908  5 snd_bcm2835,snd_timer,snd_pcm
bcm2835_gpiomem         3040  0
i2c_bcm2708             4834  0
bcm2835_wdt             3225  0
rpi_ft5406              3986  0
rpi_backlight           2064  0
uio_pdrv_genirq         3164  0
uio                     8000  1 uio_pdrv_genirq
i2c_dev                 5859  0
fuse                   84037  3
ipv6                  347594  56
pi@raspberrypi:~ $



[TiN]

I meant separately

Did you run gpib_config? Show us your /etc/gpib.conf, make us not guess

[plesa]

pi@raspberrypi:~ $ lsmod |grep agilent
agilent_82357a         18039  0
gpib_common            31540  1 agilent_82357a

Once again, this adapter is not working with Linux-GPIB and recent kernels 4.4 -4.9.Does not matter if it is clone or genuine ( I have Keysight genuine version and clone)
When solution will be ready Bingo600 or me will inform in this thread.
Maybe you can be successful with Arduino adapter.

[BFX]

I meant separately

Did you run gpib_config? Show us your /etc/gpib.conf, make us not guess

No but there is no section for agilent_82357a
Have you an example?

[TiN]

I heard these guys at xDevs have a guide. But listed procedure there works only on Pi with kernels 3.8.xx

[bingo600]

I heard these guys at xDevs have a guide. But listed procedure there works only on Pi with kernels 3.8.xx

@TiN
  Promoting


Re Error:
If the read light are on , you either missed some of the firmware stuff , or you haven't run gpib_config after loading the fw.
Or maybe have an invalid (unadapted) /etc/gpib.conf file.
See
https://www.eevblog.com/forum/reviews/using-a-raspberry-pi-with-linux-gpib-and-a-beiming-or-agilent-usb-gpib-adapter/msg964579/#msg964579


My guess - gpib_config or gpib.conf  related.

Do you have the /dev/gpib* devices now ??
Make sure to chmod 666 them , or as a test run as root


/Bingo

[BFX]

Ok I update gpib.conf and run and red light is gone 

Code: [Select]

pi@raspberrypi:~ $ sudo nano /etc/gpib.conf
pi@raspberrypi:~ $ sudo gpib_config
pi@raspberrypi:~ $

Now only ready is green 

I tried to run some test but  failed

Code: [Select]

Traceback (most recent call last):
  File "/pub/python/Test_GPIB.py", line 5, in <module>
    instr.write("*IDN?")
  File "/usr/local/lib/python2.7/dist-packages/Gpib.py", line 49, in write
    gpib.write(self.id, str)
GpibError: write() failed: An attempt to write command bytes to the bus has timed out.

Should be that my 34401A is not configured properly?
Address is OK. And after test 34401 is frozen only some underscores are in place of digits.

[TiN]

Everything is OK with your 34401, it's just you end up in same state as everyone else here are
Meter is "frozen" because it's in remote mode. Press local button to warm it back to normal.

[BFX]

Everything is OK with your 34401, it's just you end up in same state as everyone else here are
Meter is "frozen" because it's in remote mode. Press local button to warm it back to normal.

Thank you for words of encouragement
Do you know roughly where is the problem? Is it only for 34401 or it's common problem of 82357a?

[TiN]

Common problem with 82357A/Bs + linux-gpib + kernels 4.x.x series.
Something in linux kernel headers or kernel itself got change from 3.8->4.x which caused these agilent pods (real ones and fakes) to timeout on any gpib operation.

[BFX]

Common problem with 82357A/Bs + linux-gpib + kernels 4.x.x series.
Something in linux kernel headers or kernel itself got change from 3.8->4.x which caused these agilent pods (real ones and fakes) to timeout on any gpib operation.

Thx for explanation. It means at 3.8 it's working fine, sure?
I'm not familiar with linux too much, but maybe compare the changes 3.8->4.x would do the business
Well I think It's time to try 3.8 for my solution, till here some experts solve this problem 

[bingo600]

Common problem with 82357A/Bs + linux-gpib + kernels 4.x.x series.
Something in linux kernel headers or kernel itself got change from 3.8->4.x which caused these agilent pods (real ones and fakes) to timeout on any gpib operation.

Thx for explanation. It means at 3.8 it's working fine, sure?
I'm not familiar with linux too much, but maybe compare the changes 3.8->4.x would do the business
Well I think It's time to try 3.8 for my solution, till here some experts solve this problem 

Note that kernel 3.8 (Wheezy) won't work on a RasPI v3 , you need a v1 or v2

We're  working with the linux-gpib maintainer to find the problem on the 4.x.x kernels (Jessie)

/Bingo

[CalMachine]

I received my RPi earlier this week!  I was able do successfully install the V2 of the rpi lognut image and booted up.  RPi and Linux is brand new to me, so it's a bit overwhelming .  I figured having experience with Arduino and PICs that RPi would come somewhat easily.... well I was wrong. 

I've yet to test any GPIB instrument connections.  I've got a genuine HP 82357B and NI GPIB-USB-HS to use... although it seems like the HP 82357B is having issues with the current iteration the RPi kernel?

[plesa]

I received my RPi earlier this week!  I was able do successfully install the V2 of the rpi lognut image and booted up.  RPi and Linux is brand new to me, so it's a bit overwhelming .  I figured having experience with Arduino and PICs that RPi would come somewhat easily.... well I was wrong. 

I've yet to test any GPIB instrument connections.  I've got a genuine HP 82357B and NI GPIB-USB-HS to use... although it seems like the HP 82357B is having issues with the current iteration the RPi kernel?

It is easy. 82357B is not working and image is set for NI GPIB HS. On image is /pub directory shared over samba (you can connect as network drive from another machine and edit webpage and scripts).
There is running webserver, so just check in you browser ( webserver use the /pub/www directory ). There are few basic scripts for test and also for logging (3458A,K2001,3441xA, 34401A and for enviromet BME_log.py).
All these scripts  log are plotted on website.

[TheSteve]

Kernel 4.x still works with the 82357x but only if you're using an original raspberry pi.
With kernel "Linux gpib 4.4.0-1-rpi #1 Debian 4.4.6-1+rpi14 (2016-05-05) armv6l GNU/Linux" and an original model B pi I've never lost communication with my 3458A using an original 82357B.
I set this up using TiN's howto on xdevs. The image that does graphing and has a web server would be a lot more fun though.

[CalMachine]

I'm trying to run the 3458A Log script in python.  There were a few nonsensical syntax errors that I needed to fix, but after that, it's just stating

ImportError:  No module named 'Gpib'.

I've checked my lsub and it shows my NI usb-gpib.

[VintageNut]

I'm trying to run the 3458A Log script in python.  There were a few nonsensical syntax errors that I needed to fix, but after that, it's just stating

ImportError:  No module named 'Gpib'.

I've checked my lsub and it shows my NI usb-gpib.

You can type in python commands from the command prompt one at a time when you are trying something for the first time. That allows you to see which statement is throwing the error.

Does your Gpib module have a .py extension?

[plesa]

I'm trying to run the 3458A Log script in python.  There were a few nonsensical syntax errors that I needed to fix, but after that, it's just stating

ImportError:  No module named 'Gpib'.

I've checked my lsub and it shows my NI usb-gpib.

Run sudo gpib_config and after that execute scripts.

[CalMachine]

I'm trying to run the 3458A Log script in python.  There were a few nonsensical syntax errors that I needed to fix, but after that, it's just stating

ImportError:  No module named 'Gpib'.

I've checked my lsub and it shows my NI usb-gpib.

Run sudo gpib_config and after that execute scripts.

Was finally able to execute the scripts in the IDLE and I don't think that is what I was looking for.  Moving on.. lol.  So, I just accessed the webserver and am looking at the real time data log tests.  This data I'm looking at can't be mine right?  I haven't initiated any logs yet.

I'm trying to run the 3458A Log script in python.  There were a few nonsensical syntax errors that I needed to fix, but after that, it's just stating

ImportError:  No module named 'Gpib'.

I've checked my lsub and it shows my NI usb-gpib.

You can type in python commands from the command prompt one at a time when you are trying something for the first time. That allows you to see which statement is throwing the error.

Does your Gpib module have a .py extension?

I am not sure.  I was just trying to run the provided script in the Python IDLE.




*Edit   Alright sorry for the hassle.  I Think I've figured it out and kind of wrapped my head around how to go about interfacing RPi remotely.  I've been able to connect with putty and control it with my laptop and started logging!  Atleast I think I did.  Can't do much in the command prompt after I executed the script... but my 3458A went into remote mode.

[TheSteve]

*Edit   Alright sorry for the hassle.  I Think I've figured it out and kind of wrapped my head around how to go about interfacing RPi remotely.  I've been able to connect with putty and control it with my laptop and started logging!  Atleast I think I did.  Can't do much in the command prompt after I executed the script... but my 3458A went into remote mode.

When you run something from a shell(command prompt) it will typically "hold on to" the window. You can add an & after the command to have it run in the background. Right now if you loose your ssh/telnet connection to the pi the program/logging will also stop, if you add the & it will keep going.