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 )
82357B is not working, but we hope it will be fixed soon.
Maybe you can try to use different adapter like http://egirland.blogspot.cz/2014/03/arduino-uno-as-usb-to-gpib-controller.html
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.
I followed TiN's guide located here:
https://xdevs.com/guide/agilent_gpib_rpi/
At the time I hadn't read this thread and knew nothing about any incompatibilities.
On my first try I started with raspbian jessie lite from here:
https://www.raspberrypi.org/downloads/raspbian/
I downloaded the newest version, it booted up but I couldn't login remotely as it appears to have sshd disabled by default - I run all of my raspberry pi's headless - no keyboard, monitor or mouse.
So I used an older build I already had downloaded for a different pi project. It was from May of 2016. You can find the older versions here:
https://downloads.raspberrypi.org/raspbian_lite/images/
It booted right away and I was able to login remotely via ssh. I then pretty much followed TiN's howto substituting the proper kernel name etc as I went.
If I got any errors a long the way it was nothing major.
It has been working great ever since. I have had over 12 solid days of logging using some of TiN's sample python scripts that I modified a little. It hasn't crashed or had a single issue.
I am using an original generation pi, model B with 512 megs ram and an authentic 82357B.
Give it a try, I am sure it will work for you, if not we'll figure it out.
As a last ditch if needed I can make the exact image I used available for download. If your pi has a keyboard/monitor I would start by trying the newest version though.
As a last ditch if needed I can make the exact image I used available for download.
As a last ditch if needed I can make the exact image I used available for download.Please do that.
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.
I used - 2016-05-27-raspbian-jessie-lite
pi@gpib:~ $ gpib_config -v
linux-gpib version = 4.0.3 [r1652]
[..]
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.
Fair enough - there are some caveats to using it. Using "screen" probably is the best option for people - I've been using it for 20 years now.
Fair enough - there are some caveats to using it. Using "screen" probably is the best option for people - I've been using it for 20 years now.
A small mod to the BME_Log.py script so that it runs with only one sensor present.
Fair enough - there are some caveats to using it. Using "screen" probably is the best option for people - I've been using it for 20 years now.
screen is old and had bugs.
try tmux. I'm a many year screen person, too, but tmux is what everyone at work seems to be using, with good success, and more features.
Thanks, I will put it to Github and to next image.
Thanks, I will put it to Github and to next image.
Maybe you should merge the open pull request, so that it doesn't run out of sync for too long, there were some changes from other people as well:
https://github.com/PlesaEEVBlog/RPi_LogNut/pulls
Thanks, I will put it to Github and to next image.
Maybe you should merge the open pull request, so that it doesn't run out of sync for too long, there were some changes from other people as well:
https://github.com/PlesaEEVBlog/RPi_LogNut/pulls
It is in my plans, please be patient
Try to enter /pub/python/ directory with actual .py file and run python ./3458A_Log.py.
Try to enter /pub/python/ directory with actual .py file and run python ./3458A_Log.py.ooo!!! Thank you so much! I was missing the 'python' part in the command. I think I've got it working now.
Try to enter /pub/python/ directory with actual .py file and run python ./3458A_Log.py.
You know it is only one click in Github, if you agree with the commits?Yes, but I would like to review it and test it, so it takes more time.
BTW what di you changes in script, is it something for all us us? I'm put there there notification when internal temperature is increased something like "Clean filter".
Also found in different thread here this application made by member here for 3457A, which can be probably modified to 3458A.
It use the Arduino GPIB.