EEVblog Electronics Community Forum

Hi Plesa,
For my vote its is all HP-Ag-Ks GPIB equipment with either  Prologix or HP 82357B. The later has some problems with clones abounding everywhere.
NI also in the running.
Thanks

If it's python, I can help to write support for Keithley 2001, 2002, 2400, 2510, 182, HP 3458, Wavetek 4920/4920M.

Plesa,
thanks for sharing...

For the moment I have Rigol DM3068 and RPi2..  It would be over Ethernet.
I would like to help with that.

P.S. Where did you guys get BME280 from?

Great idea overall!! If this is written in Python, would it not also run (or could it be written in siuch a way) that it runs on a PC?

Right now I am using the Prologix and RF Scientific logging software on my 3458A and other Agilent gear.
But I am very much interested in other options, especially RP.

Plesa,

I have attached a couple of shell scripts I used to setup my RPi on wheezy. If you find any of it useful you can add it to your project. The rpi_gpib_installer.sh works well but it only lets you select either the Agilent or NI interfaces. It might not be difficult to change for a universal install.

Thanks for all inputs. Extra Kudos for  TiN and ManateeMafia
Based on voting majority needs support 3458A, so lets start with this instrument.
It is going to use latest Raspbian with Pixel, this is answer to TiN question related to kernel ( 4.4.26) and Python 2.7.9

GPIB interface:
NI GPIB-USB-HS - TiN, Plesa
Agilent 82357B ( official)  - we needs volunteer for testing
Agilent 82357B ( clone)  - I have dead clone only
Prologix GPIB-USB v6.0  - we needs volunteer for testing
Agilent E5810A  - Plesa

LAN:
support for LAN is made by
https://github.com/python-ivi/python-vxi11
http://alexforencich.com/wiki/en/python-vxi11/start
Alex Forencich ( member here)  - author of python-vxi11 and also USBTMC

Instruments (Support means script for dataloging)
In first phase only 3458A,K2001,K2002
Future phases  3441xA/34401A/3446xA

Enviroment:
2x BME280 connected to I2C - Python dataloging with Adafruit code to log file (csv) and ploting data on webpage on RPI (similar look like Fluke 1620A display  - 2nd page of datasheet)
http://download.flukecal.com/pub/literature/3397500_6200_ENG_B_W.PDF
2 sensors as minimum
BME280 sensors I used are these
https://www.sparkfun.com/products/13676
Others posted above do not allow to set I2C address, there are similar on Ebay for $5/pcs.

Data upload:
Function to upload CSV-data to remote FTP. I will prefer to make data available on RPI FTP instead of active upload.
Who needs this except TiN?

SSH access is default.
Apache2/NGINX - any preference except TiN?

Now we needs to discuss how to process data. I checked options like KST ( stability ) and ended like TiN with D3.js. There is possibility to plot graphs by D3 on server side to reduce processing time on webpage, but I needs to investigate further. Dataplot of 10MB takes 20-30s.
Currently I can imagine one page for data from 3458A ( timestamp, temperature, humidity,pressure) second page for environment log and third page as universal for generic instruments ( timestamp, value).
Any suggestions how to visualize data?

I don't know how D3 works, but I think it will be useful to have a file format that explains how to plot data and few "macro" to add things like stddev, convergence, ppm deviation between two measurements etc. If there is something like this, you can plot chart with one script.

Inviato dal mio Nexus 6P utilizzando Tapatalk

Keysight 34461A over either LAN or USB, please.

Hmmh, I'm generally in favor of strict separation of hard- and software, otherwise there will be unnecessary duplication of effort and fragmentation of community and knowledge.

If you suggest Raspberry Pi, I suppose you're ok with using Linux.  When the task is to access the GPIB using Linux, then the obvious choice would be to use the linux-gpib library (http://linux-gpib.sourceforge.net/), no?  Well, that's what I'm using at least (with an old PCI GPIB interface -- I also have a USB GPIB interface, but that doesn't seem to work well with multiple devices or older HPIB gear).

I would like to see more support for GPIB devices and perhaps on the high level ("presentation layer" if you will), like the web interface you suggest.

If I remember K2001 and K2002 have 3458A GPIB compatibility mode ... so supporting 3458A means also K2001 and K2002.
Anyone used this compatibility mode up to now on Keithely? How it works?

Anyway I think we must think at this as at least 3 software layer for just capturing the data:

• TOP LAYER: gather data and store on CSV or some file based database
• MIDDLE LAYER: implements instrument interface
• LOW LEVEL LAYER: write GPIB commands to the physical interface (for supporting specific hardware - Prologix, 82357B, GPIB ENET, etc)

in this way we can implement how many LOW layer or instrument we wants without changing (too much) the other TOP layers.

Than I imagine a simple web interface made by two main modules:

• interface for set "logging" tasks (this module speaks with TOP LAYER and configure the instrument for doing measurements), this interface show also the real time measured data
• interface and module to elaborate the stored data gathered by TOP LAYER and to present them in the most appropriate way (charts, tables, etc) 

I have Raspi1 , and Raspi3
I would prefer Apache (sorry TIN)


Agilent 82357B ( clone)  - I have one , working excellent , and a Beiming
Agilent E5810A  - I have one , but not used it yet

Edit:
Have ordered : 2x BME280

/Bingo

I'm definitely interested in this project!

I'm interested in LAN support for any of:
34461A - Agilent
34410A - Agilent
DMM7510 - Keithley
2450 SMU - Keithley
DM3068 - Rigol

Quote from: bingo600 on November 16, 2016, 08:38:32 pm

Agilent E5810A  - I have one , but not used it yet

Care for a mini teardown? I was thinking about GPIB-LAN bridges recently, because I only have one USB-GPIB adapter (also a 82357B clone) and it's not as convenient as having access to all the instruments from the network. So I've came up with the idea to implement a linux-gpib to VXI bridge to emulate E5810B (could do that with a RPi and this clone USB adapter perhaps), but I need to do more research on that.

While researching this I was looking at existing GPIB-LAN gateways, Keysight, ICS and also I've analyzed E5810B firmware a bit and it seems very clever as it uses TI's AM335X and the PRUSS cores to do the GPIB. I never saw the insides of this gateway so I don't know if PRUSS is bitbanging some GPIB interface chip (NAT9914 and the likes) or probably GPIB transceivers directly, which would be quite cool and fast. The kernel modules, especially the one responsible for talking to the PRUSS and GPIB is tagged with the GPL linker symbol, but I didn't find sources anywhere 

I suppose I already posted internal picture of E5810A, but it use the Power PC AMCC PPC405.Firmware seems to be made by ICS Electronic http://www.icselect.com.
And there is also one Xilinx Spartan, 83846 PHY and some Cypress for USB. If you wants picture of A version I can post within 2-3 weeks, when I will be back home:)
The main board looks more like some platform, because on front are 3x 64 pin connectors to connect display and few leds on front panel.

If I remember K2001 and K2002 have 3458A GPIB compatibility mode ... so supporting 3458A means also K2001 and K2002.
Anyone used this compatibility mode up to now on Keithely? How it works?

K2001 do not have compatibility mode. It is only on K2001

I'm interested in LAN support for any of:
34461A - Agilent
34410A - Agilent
DMM7510 - Keithley
2450 SMU - Keithley
DM3068 - Rigol

Both 34461A and 3441xA will be working. For Keithley/Rigol I do not have access to them, but based on how Python scripts are, you can add their support (logging) easily.
Some old meters like 3457A I have in garage, so their support can be added later.

I don't know how D3 works, but I think it will be useful to have a file format that explains how to plot data and few "macro" to add things like stddev, convergence, ppm deviation between two measurements etc. If there is something like this, you can plot chart with one script.

Statistic available in D3 is min,max,mean,median,deviation, ppm is calculated against defined reference value. But If you needs something more complex you can access log by Samba of FTP and work with data in Excel/Libre Office or other statistical program.

In meantime I needs to define data separator ( comma, tab or semicolon) my preference is tab. So log files will be tsv and not csv. Any complains?

Current status:
Image for RPi 2/3 is ready ( ext4 replaced by F2FS)
Support implemented and tested for: LAN instruments ( tested with 34411A), USB ( by USBTMC, tested with 34411A), GPIB (NI USB-GPIB-HS,E5810A)
-big thanks to Alex Forecich ( member here)
http://www.alexforencich.com/wiki/en/python-vxi11/start
http://www.alexforencich.com/wiki/en/python-usbtmc/start
Modified Adafruid library to support two BME280 sensors

Now lets to discuss the D3 and plot part.
A) I propose to have separate graph for Environment data ( both BME280 in one graph) .
B) Measurement data in second graph with environment data from one sensor ( add plot for ppm).

On chart are possible following functions:
Zoom in/Zoom out
Display values on mouse over

Any ideas?

BTW Thanks to VK5RC - He donated one 82357B clone for testing.
Prologix has been ordered.

I can upload current version of image (8GB SD card is minimum) or wait for Prologix. Anyone interested in current version?

Quote from: plesa on November 19, 2016, 08:05:41 pm

I suppose I already posted internal picture of E5810A, but it use the Power PC AMCC PPC405.Firmware seems to be made by ICS Electronic http://www.icselect.com.
And there is also one Xilinx Spartan, 83846 PHY and some Cypress for USB. If you wants picture of A version I can post within 2-3 weeks, when I will be back home:)
The main board looks more like some platform, because on front are 3x 64 pin connectors to connect display and few leds on front panel.

Agilent might have rebranded some ICS stuff. Someone here did a teardown of ICS 8065, based on NAT7210 interface chip, driven by LH75411 ARM7TDMI.

Thanks for the description, seems too like departure from NI interface chips (EOL I suppose), so probably the Spartan does the GPIB protocol details and just passes data back and forth with the PowerPC. Still not as clever and simple as driving the GPIB transceivers straight from the PRU cores

Anyway, that's just curiosity, I don't want to dive deep into the GPIB details to be able to implement this in PRU. I'm leaning towards just a piece of software to translate VXI11 to linux-gpib calls so anyone with any supported GPIB adapter (NI, Agilent, Beiming, clones etc) and board of choice (RPi, BeagleBone etc) could set up a GPIB to LAN gateway.

TI AM335X GPIB would be useful for those that don't have any GPIB adapters or slow ones (e.g. not NI HS variant), but requires much more and low level work.

I also suppose that it is re-brand or some of their OEM product.
NI seems to have also obsolescence problems and that why they made NI GPIB-USB-HS+, it can be interesting what is inside.
It can be useful, but the amount of work seems to be big, maybe for someone like NighPanda who made Beiming adapter:)

BTW I'm surprised how many people are using one adapter per instrument, after that is GPIB quite "expensive" interface.And GPIB cables are so cheap on eBay:)

I've bought 10x 50cm HP GPIB cables for $30 to connect everything toghether.
I already have the 53181 conhecer to the 3457, and the 3457 conhecer to the K2000.
Next will be the K2000 conhecer to the 3456, then the 3456 conhecer to the PC with GPIB to USB HP clone.

plesa

Quote

I can upload current version of image (8GB SD card is minimum) or wait for Prologix. Anyone interested in current version?

My SD card in one of Pi1's died recently, so I'm surely can try new image now  .

One more suggestion - to have main linux partition located in the end of the image. So it could be easily expanded to larger SD cards. It's PITA to do so if there is other smaller partition in the end or swap in 8GB image, and you use it on 32GB card for example  Yea, my linux-magic not that great.

Image is being uploaded to xDevs FTP File is called RPi_LogNut.7z
I tried to minimize the image size, but there seems to be problem with F2FS ( but I have much better experience with F2FS than with Ext4 FS).
Current image size after compression is 2.2GB. For image creation was used Win32DiskImager.
On image is enabled Samba, so you can access/map  /pub directory on your main computer.
Following has been tested:
   Connection to LAN instrument ( example /pub/python/Test_LAN.py)
   Connection to USB  instrument ( example /pub/python/Test_USB.py)
   Connection to GPIB instrument over NI adapter ( example /pub/python/Test_GPIB.py)
   Samba /pub ( read/write)
  BME280 logging (   /pub/python/BME280/BME_Logging_tsv.py)

Following needs to be set:
  webserver
  D3 scripts for logging (I would like to make it universal - description of plot loaded from log file header)
  Test support for 82357B clone adapter
  Test Prologix GPIB-USB Controller 6.0


Here are notes if someone want to update you own image:
1. Download Raspbian image  (RASPBIAN JESSIE WITH PIXEL)  it will take a while 1.4GB
https://www.raspberrypi.org/downloads/raspbian/

2. For image installation follow
https://www.raspberrypi.org/documentation/installation/installing-images/README.md

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install screen mc f2fs-tools i2c-tools samba samba-common-bin bc python-dev rpi-update tk-dev build-essential texinfo texi2html libcwidget-dev libncurses5-dev libx11-dev binutils-dev bison flex libusb-1.0-0 libusb-dev libmpfr-dev libexpat1-dev tofrodos subversion autoconf automake libtool

sudo rpi-update
sudo wget https://raw.githubusercontent.com/notro/rpi-source/master/rpi-source -O /usr/bin/rpi-source && sudo chmod +x /usr/bin/rpi-source && /usr/bin/rpi-source -q --tag-update
sudo rpi-source
sudo reboot

cd /opt
sudo svn checkout http://svn.code.sf.net/p/linux-gpib/code/trunk/linux-gpib/ linux-gpib
cd linux-gpib
sudo ./bootstrap
sudo ./configure
sudo make
sudo make install

sudo svn checkout https://github.com/python-ivi/python-vxi11/trunk python-vxi11
cd python-vxi11
sudo python setup.py install

sudo svn checkout https://github.com/python-ivi/python-usbtmc/trunk python-usbtmc
cd python-usbtmc   
sudo python setup.py install
sudo pip install pyusb

# Following part is test USB connection
import usbtmc
instr =  usbtmc.Instrument("USB::0x0957::0x0a07::INSTR")
print(instr.ask("*IDN?"))
# Agilent Technologies,34411A,MY480060XX,2.41-2.40-0.09-46-09
Vice info https://github.com/python-ivi/python-usbtmc


# I2C
enable i2C in raspi-config
sudo raspi-config
-7 Advanced Options - A7 I2C Enable/Disable automatic loading of I2C kernel module - YES
reboot
# Now detect the BME280 by
sudo i2cdetect -y 1
pi@raspberrypi:~ $ sudo i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- 76 77

# Address 77 and 76 - BME280

Install adafruit library
cd opt   
sudo git clone https://github.com/adafruit/Adafruit_Python_GPIO.git
cd Adafruit_Python_GPIO
sudo python setup.py install

Modication second module ( I2C address to 76 instead 77 )
https://cdn.sparkfun.com/datasheets/Sensors/Weather/SparkFun_BME280_Breakout_v10.pdf

# Samba configuration
sudo smbpasswd -a pi
enter Samba password (raspberry)

create /pub directory
mkdir pub
chown -R  pi /pub
sudo nano /etc/samba/smb.conf

# add following to smb.conf
[pub]
   comment= RPi pub
   path=/pub
   browseable=Yes
   writeable=Yes
   only guest=no
   create mask=0777
   directory mask=0777
   public=no

@bingo600

I have the Adafruit version of the BME280 breakout and I plan on putting mine inside of a Hammond 1551MFLBK enclosure. One of the holes of the pcb will be used to secure it to one of the internal standoffs.

The enclosure is much larger but I like the fact I can use a zip tie to temporarily mount it where it is needed. I will have to drill some small holes near the sensor.

I have found the board to be highly sensitive to air drafts and have been keeping mine wrapped in anti-static foam for a while now.

@ManateeMafia & Plesa
Thanx for the info.

I'll see if i can get a Raspi 1 or 3 going this weekend , while waiting for the BME's from China

/Bingo

I'm actually using ext4 too , and have no problems on my RasPi's.
I even have one with Kodi , that gets it's power cut when we leave the summerhouse.
That one have been working for 1.5 years wo. probs

/Bingo

Addon to the Vnut Platform

Here's Mark Simms annotated HP3458A calram readout , built on a RasPiv3 with a "fresh Jessie" , and linux-gpib 4.03
Rename the file extension to tar.gz , wasn't allowed as an upload extension

I haven't tested this one on my 58' yet , but it's build as the one i uploaded previously , that was used by TiN

/Bingo

I'd expect this ready to go image concept presented in thread to be more targeted for beginners and non-software folks who just want plug it in, write image and run the "log the data, now" app.

I don't agree 100%
A common platform would be nice for ie. your DMM noiselogger measurements.

Btw, one problem I have with RPi and NI USB-GPIB-HS is random crashed when running long time (hours). I used wheezy and jessie images from raspi site, different kernels, latest and one before that linux-gpib, RPI 1 and RPI 3 boards and various SanDisk SD cards. After crash gpib_config can't talk to dongle anymore, even thou it shows ok in lsusb. Reboot doesn't help , only dongle powercycle does.

Have you tried with a powered USB hub ?
I think it could be power related.

Same NI dongle however works happily logging simultaneous data from 3x2001, 2x2002, 3458 over more than 70 hours now, running same python snake app on DE1SoC board with Trusty LTS 14.04 linux.

Does that one deliver more/better power ?

/Bingo

I don't agree 100%
A common platform would be nice for ie. your DMM noiselogger measurements.

More meant - can do both, DIY stuff for advanceds, but also have easy functions for beginner work
E.g. when linux-gpib was a new thing few years ago - fiddling with dozen of packages, kernel headers, firmware uploads enough to scare even brave *nix beginner 

Have you tried with a powered USB hub ?
I think it could be power related.
...
Does that one deliver more/better power ?

Yes, even tried powering +5V to dongle directly to pod from 3A PSU, same thing.
RPI board just forwards same +5V from input. Dongle takes ~400mA peak.

This issue is bit offtopic here, but I brought it up so we make sure images are ok for long term runs.

Maybe worth to make two level app? First level for function logic, etc datalogger or noise tester or custom modes such as delta measurement using current source and voltmeter for resistance measurement, similar to Kei 6220+2182.

Second layer would be for hardware support, eg SCPI commands to talk actual instruments.

It will take a bit more work, but will be easier to add support for specific instruments later.

I always have 3458, 2002s connected on GPIB, and add other instruments as needed.

What a great thread.

OK, I am ready to get my first Raspberry Pi.
But which one should I get to get best results ?
Thanks.

RPi2 or RPi3. RPi3 is faster and has integrated WiFI/BT. Price is almost the same. Image is working on both, we are not using x64 mode available on RPi3.
Do not forget to buy also enclosure. As SD card is 8GB minimum, I'm using several Samsung SD ( Pro/EVO+)  cards without problems.
RPi official power adapter is OK, but during logging I used output of E3631A PSU ( 5V for RPi, and 15V for LTZ).

I do not have Prologix yet, so it is not working, but will be added soon. Currently is working on NI USB-HS and E5810 GPIB interface.
82357B will be added soon as well.

I have been working on the BME280 server/client code. It has been tested and I have a GUI for those that want to use a PiTFT hat. There is room on the display for a second sensor readout. The RPi is installed in a black Uniker case with 2.2 display. My photo doesn't do it justice as my camera phone adds a blue tint.

I am not sure if this is too much to add up front to the project but it may be worth considering for a future version. It has push buttons and a user interface might be added for launching python scripts without a remote login.

This 2.2" display is pretty small at 320x240. The smallest text size is 10 point and the largest is 24.

I have the Kuman 3.5" display with case. It looks like it would be a better choice but I haven't assembled it yet to see how durable it is. There doesn't seem to be any protection for the screen like the Uniker.

@plesa

You'd need these for Agilent USB adapters & clones.

Code: [Select]

sudo apt-get install fxload

#Get the USB adapter firmware
wget http://linux-gpib.sourceforge.net/firmware/gpib_firmware-2008-08-10.tar.gz
tar xvzf gpib_firmware-2008-08-10.tar.gz

/Bingo

Ps: I don't have any EMI antennas 

Yep, I know. I also tried to repair fake 82357B adapter from ebay, but it lost vendor ID, anyone know how to restore it?
EMI antennas are not required ferite beads and some wire will be enough
https://interferencetechnology.com/the-hf-current-probe-theory-and-application/

From
https://www.eevblog.com/forum/reviews/using-a-raspberry-pi-with-linux-gpib-and-a-beiming-or-agilent-usb-gpib-adapter/msg329067/#msg329067


cd ~/linux-gpib
sudo apt-get install fxload

#Get the USB adapter firmware
wget http://linux-gpib.sourceforge.net/firmware/gpib_firmware-2008-08-10.tar.gz
tar xvzf gpib_firmware-2008-08-10.tar.gz

cd gpib_firmware-2008-08-10/agilent_82357a/

#Find the adapter
lsusb
#It will show something like this : Bus 001 Device 007: ID 0957:0518 Agilent Technologies, Inc.

#load firmware 1'st time
sudo fxload -t fx2 -D /dev/bus/usb/001/007 -I ./measat_releaseX1.8.hex

#Find the adapter (Device will usually increment by 1 , after a fw load)
lsusb
#It will show something like this : Bus 001 Device 008: ID 0957:0518 Agilent Technologies, Inc.

#load firmware 2'nd time
sudo fxload -t fx2 -D /dev/bus/usb/001/008 -I ./measat_releaseX1.8.hex

#Find the adapter
lsusb
#It will show something like this : Bus 001 Device 009: ID ID 0957:0718 Agilent Technologies, Inc. , note the change to ID 0957:0718

The green led's should be lit , and we're ready to go.

Didn't see such stuff with my K2001's/3458 mixes.
Btw, I also had Agilent pod version of linux setup guide, using clone I have here.

Just my two cents: you can also use a DS18B20 as a second temperature monitor thing. It's more small and I suppose more cheap too.
It don't even share pins with the BME sensor, so you can just slap over the BME without doing any rewiring.
I'm actually using one it for TC characterisation of resistors for my LTZ1000 project.

If you needs DS18B20 sensors support you can inspire here
https://www.modmypi.com/blog/ds18b20-one-wire-digital-temperature-sensor-and-the-raspberry-pi

BME280 is unique for it's humidity measurement.
Lot of things are sensitive to humidity and not only to temperature. Price of BME280 is almost same like DS18B20, only absolute accuracy is better with DS18B20 ( 1C vs 0.5C).

Nice project. I have a HM8012 benchtop multimeter with RS232, a RK8511 DC electronic load with RS232 and a Siglent SPD3303D power supply with an USB port, do you plan to support this? Would be cool to control and read it all from Python on a Raspberry Pi for measurements and experiments, like power on/off stress tests. I can help to implement drivers for it.

Looks like the xdevs site is down. Maybe you could create a github repository with a script (and additional programs and config files etc. if needed), which you can just start to turn a fresh Raspian image into this special distribution? Only one wget from a root shell would be required and then starting the script. Bonus: add some Dialog menus (can be implemented in bash) what instrument drivers you want to install and how you want it to configure, just like the raspi-config. Then you don't need to host gigabytes of data, too. Everyone could fork the github repository and send you pull requests for new things they have implemented.

"Yes, post type of instrument and type of interface (GPIB,Prologix,USB,LAN, RS232)"

Instrument: several 3458A's

Interface: Agilent 82357B GPIB to USB

@OP, for crap sake please please make it easy to use for us end users who are not linux nuts. "Bash, fork, pull requests" and such gibberish will turn many like me away. Thank you.

I am waiting for the Agileng clone adapter implementation, i only have that one.   

So you are exactly the user for this.
Image ready to go including plots available on website is ready on xDevs site.
...
RPi you should buy is:
https://www.raspberrypi.org/products/raspberry-pi-2-model-b/
or
https://www.raspberrypi.org/products/raspberry-pi-3-model-b/
RPi3 is faster and has WiFi and Bluetooth.
Do not forget case
https://www.raspberrypi.org/products/raspberry-pi-case/

Does RPi-2 or -3 make a difference for needed image?
Where can I find the image? I scanned xdevs site several times, but was not able to find it.

Does the raspberry need additional (DDRx)-RAM cards or is RAM already on board?
It's quite confusing for me without linux or raspberry experience...

As far as I understood xdev site, Agilent's GPIB to USB interface adapter loads firmware via bootloader on each startup.
Is that firmware loaded into adapters RAM or why is it not loaded permanently?

I've tried to put the image on a 8GB Sandisk Ultra but it has a few sector less than needed (20MB actually):
Not enough space on disk: Size: 15564800 sectors  Available: 15523840 sectors  Sector size: 512

It's just great that a "8GB" card is 7.4 in reality...

Reading back what I wrote, I'm sorry if this came through as a complaint, it wasn't aimed at you.
I can only be grateful for the idea and effort put into it. So thank you!

I wrote a sample for my HM8012 and tested it with

, and created a github pull request, so that it can be integrated in the main github repository (and later in the SD card image). With the github repository, we could implement an update function, even over the web interface, to get the latest examples and framework code, without the need to update the whole SD card image and without overwriting your own code.

Maybe would be a good idea to add TiN's guide to the repository as well in a doc directory, so that it is all in one place and under version control, and all scripts and docs needed to create a new image from a fresh Raspbian image.

I think a Python measurement framework would be nice. Maybe we can use some parts of the project at http://sigrok.org that @lwatts666 mentioned?

An idea: a generic base class "Instrument". All instruments in common is the capability to measure something. An instrument has a fixed number of inputs (and maybe outputs?). Concrete instrument classes for a HP34401A, or a HM8012, are derived from the abstract base class and implement all the instrument specific initialization and communication. It might be possible to configure an input, e.g. select volt or ohm, and select a range or auto-range. For each input you can get an input reader, which reads this input and knows about more about the input, like the unit, e.g. V or A, or the instrument channel.Then a logger class. You can add inputs to it and it automatically reads all inputs and writes them with a timestamp to a file, in a selected interval.

Sounds difficult if you are not an object oriented programmer, but it makes it really easy to write your own custom measurement script for an advanced end user. Goal should be that you can write a script for an instrument, without knowing the GPIB commands or other details of the instrument, except some instrument specific configuration for selecting AC or DC etc. A logger program could look like this (I don't know much about Python, so this might not compile) :

try {
  # create a new instrument object. Opens the default port for this instrument
  # and initializes it to be used with the framework, e.g. ASCII output format, 9 digits etc.
  voltageMeter = new HP34401A();

  # application specific configuration of an input of the instrument.
  # optional parameter: channel=x, if there are more than one input
  voltageMeter.configure(command=HP34401A.DCV, value=10);

  # creates a new instrument object for a LM75A temperature sensor
  # uses the default I2C address 0x48 for A0-A2=0, if not specified in the constructor
  # the I2C address could be a generic parameter "port", which could be the GPIB address, or an I2C address,
  # and a factory function in the instrument which lists all available ports, to create a GUI for port selection later
  i2cTempSensor = new LM75A();

  # create a new logger object and add all inputs. The getInputtReader-function could have an optional channel parameter
  log = new Logging("/pub/logs/test.csv");
  log.add(voltageMeter.getInputReader());
  log.addInstrument(i2cTempSensor.getInputtReader());

  # start logging
  # this creates the log file, writes the CSV header and saves the current time for the exact measurement interval
  log.start();
  while (true) {
    # measures all configured inputs and writes it to the CSV file, with a leading timestamp
    log.measureInputs();

    # waits for the specified number of seconds, relative to the last call of this function, so that there is an the exact same interval between every measurement
    log.waitSeconds(10);
  }
  log.createWebpage("/pub/html/test.html");
} catch (exception) {
  print(exception);
}

So all you need to write for a volt/temperature combination logger, with website output, are about 10 lines of easy to understand code, which can be mixed with custom tasks, like switching relays after some time etc. The generated CSV file header should name the instrument and unit, and optionally the channel, or I2C address etc.:

(timestamp)	(HP34401A, V)	(LM75A, C)
10/12/2016-07:53:27	9.152	22.3
10/12/2016-07:53:37	9.264	22.2

The InputReader class has a function "measure", which returns a float for the measured value, and it has a function getUnit. Now the log object can have a function to create a standard webpage to display all configured instruments and inputs, with some nice diagram header and axis labeling. There could be also a getLastMeasure function in the InputReader class, which you can use in the measure loop to get the last value, if you want to compare it to something to do something, in addition to the log output.

One step further: There is a webpage, which lists all available instruments. You can add multiple instruments with a mouse click and individually configure each instrument and the measurement interval. The set of instruments with the configuration can be saved as a project. You can start a measurement and then a log file is named with the project name and a sequential number suffix. You can click on a log file to display, download and delete it.

An instrument can list the possible set of configuration parameters so that you can edit this in the web page when configuring an instrument. There could be some templates for an instrument with a set of configuration parameters, e.g. "measure DC voltage", "measure AC ampere", so that you don't have to lookup the meaning of all parameters. The templates are provided by the concrete instrument class. Each parameter has a description, so that it is self documenting, without needing to read a manual for an instrument.

For the webserver it might be a good idea to use the Python webserver http.server, because then it is easier to access the Python instrument classes and configuration. The Python webserver could also provide a JSON server interface, so that you can call your Raspberry Pi from other systems and create a set of distributed network connected measurement devices.

Shouldn't be too difficult to implement. An experienced Python developer with webserver and object oriented programming experience might be able to do it in one week full time. Too bad I don't have much time at the moment , but I can help with testing, bugfixing and framework design ideas, if someone wants to do it.

I have not tried the http.server and I would like to see how easy it is to implement.

I just tried the webserver, now I can read the value of my benchtop multimeter which has only RS232, in a webpage and even from the internet, if I would add a NAT rule to my router 

https://github.com/FrankBuss/RPi_LogNut/blob/master/pub/python/HM8012_Webserver.py

How it looks like (the real version reloads automatically every second) :



Of course, this is just a quick hack. You would not create the web pages in the Python code, but state of the art is probably to use some WebSocket API, serve local static files and then some JavaScript communicates over the WebSocket with JSON requests with the Python script.

Quote from: ManateeMafia on December 10, 2016, 09:14:38 pm

I have not tried the http.server and I would like to see how easy it is to implement.

I just tried the webserver, now I can read the value of my benchtop multimeter which has only RS232, in a webpage and even from the internet, if I would add a NAT rule to my router 

https://github.com/FrankBuss/RPi_LogNut/blob/master/pub/python/HM8012_Webserver.py

How it looks like (the real version reloads automatically every second) :



Of course, this is just a quick hack. You would not create the web pages in the Python code, but state of the art is probably to use some WebSocket API, serve local static files and then some JavaScript communicates over the WebSocket with JSON requests with the Python script.

I like it, so on additional page can be actual values.

Running multiple scripts and having multiple output files could have some problems, like out of sync and it is more complicated for the web page. Maybe as a start a universal Python script would be a good idea, which reads some simple JSON project file. Then all a user has to do, is to write a JSON project file, no need to program anything (and the JSON file creation could be supported by a neat web interface). An example for measuring volt and temperature:

{ 
   "LogFile":"/pub/log/test.csv",
   "MeasureInterval":"10",
   "Instruments":[ 
      { 
         "class":"HP34401A",
         "InitCommands":[ 
            { 
               "Command":"DCV",
               "Value":"10"
            },
            { 
               "Command":"LFILTER",
               "Value":"ON"
            }
         ],
         "Unit":"V"
      },
      { 
         "class":"LM75A",
         "Unit":"C"
      }
   ]
}

(I'm not sure if it makes sense to allow to specify multiple input channels, as proposed earlier, maybe better to just instantiate multiple instrument objects, even for the same physical instrument, and each instrument has just one channel.)

The Python script reads this file, creates all instrument classes and configures them, and writes the log file. The script could be even created now by merging all existing Python scripts in one big script, and evaluating the JSON input with it, but would be much better to create some clean classes. The same JSON file can be used from a general webpage, which creates the diagram with it. Special format specifiers, like colors etc., could be added to the JSON file.

This would be not as flexible as hand written Python, e.g. with custom actions when some limits are triggered, and custom HTML code, but I guess would work well for many measurement applications.

TiN's documentation ends with a pyvisa example.

I'm in.
Lately I'm in a hurry with some projects, but whenever possible I could contribute. I have some gears, and a NI PCI GPIB card in my computer.

I will order a new Rasp, since mine is the first one....

Some gears are LAN, some have serial and a lot have GPIB and I can test, and help code something.

Quote from: plesa on December 11, 2016, 08:25:21 pm

I suppose it is only question of linux-gpib settings and firmware. I used measat_releaseX1.8.hex.
TiN makes it work, maybe the clones are different. Till it is solved 82357B clones are out of game.Only genuine NI-GPIB HS, E5810 and Prologix will be supported.

Seems like a strange decision , unless you meant 82357B clones , and still supports the original 82357B.
My Agilent clone & Beimings are running excellent w. linux-gpib.

How do you experience the problem ?

/Bingo

I don't know if that is what plesa is referring to - I am getting for ibtest with Genuine Agilent 82357B (and similar errors for Python):

gpib status is:
ibsta = 0xc100  < ERR TIMO CMPL >
iberr= 14
EBUS 14: Bus error
ibcnt = 0

I was able to see something happen with pyVisa - but can't even recreate that. 

Thanks z01z.
Which file in Windows is firmware?
I just started clean Gentoo installation on RPi3 to check if issue persist.
On older kernel/linux-gpib this error has been solved by changing kernel parameter (timing), but it was for PCI and ISA boards.
Document with error messages
http://digital.ni.com/public.nsf/allkb/2FA525A8585A92E9862566EE002A3755

Concur changing the 2 words did not change the behavior for me as well.

I've tested the image on an old Raspberry Pi 1, model B, and works without problem on this hardware.

Is my undersatnding correct:
Raspberry is same time also logging at the environment (temperature. humidity, pressure) using the BME280 sensore (I2C)?
If yes - would great, as I have two of BME280 waiting for activity.

BR
PeLuLe

But currently is 82357B adapter not working

Understood, but worth to wait for.

But currently is 82357B adapter not working

@plesa et all.

I can confirm that currently the 82357B adapter is not working, on newer raspi kernels.

I have just build linux-gpib (svn) on both a raspi v1 , and a raspi v3 , both fails reading from the adapter.

Both are using latest kernel

Raspi V3 - Linux raspi4 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l GNU/Linux

Raspi V1 - Linux raspi3 4.4.38+ #938 Thu Dec 15 15:17:54 GMT 2016 armv6l GNU/Linux


I build the same  linux-gpib (svn) , on my Corei5 lappy , where it's working
Linux  3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux


$ cat idn1.py
#!/usr/bin/python
# -*- coding: utf-8 -*-

import Gpib
inst = Gpib.Gpib(0,16) # address 6
inst.write("*IDN?")
INST=inst.read(100) # read 100 bytes
print(INST)




 ./idn1.py
KEITHLEY INSTRUMENTS INC.,MODEL 2015,1043877,B15  /A02

Something is wrong on the newer kernels (devicetree or ??).

I have used the 82357B (china prob. clone) adapter on my raspi v1 w. debian wheezy , without problems.
Furthermore it works 100% if i build the same linux-gpib on my Corei5 w. Mint 17.3  - (same kernel as Ubuntu 14.04).


/Bingo

@plesa please add the USBTMC standard Linux driver when you create the next image. On my Debian Wheezy on PC I can now access my SPD3303D over USB, worked out of the box without needing to install a driver, with some quirks how to access it, as someone figured out here (but only the first Device class implementation works with my device), and add it to the documentation. Now I can control a good laboratory power supply from Python scripts, this is going to be fun 

Hi Frank,

USBTMC is already there including example how to control 34411A.
Currently we needs to solve kernel problem with 82357B. Also genuine 82357B is not working with kernels 4.4.34-38.

I hope that with Raspberry, Python, D3 we can have lot of fun and gain from sharing scripts
I already receive request for various things like controlling PSU  and reading temperature for testing resistors tempco.

The Python USBTMC implementation doesn't work with my device. I checked it with the 34410A_Log.py example, changing the instrument creation line to

inst =  usbtmc.Instrument("USB::0x0483::0x7540::INSTR")

which is the vendor and product ID I can see with lsusb. And it shows after a while "usb.core.USBError: [Errno 110] Operation timed out". If I change the vendor or product ID in the instrument creation, or unplug the device, it says "usbtmc.usbtmc.UsbtmcException: Device not found [init]", so I guess it finds the device and can open it. But it might be the same problem when using the Linux kernel driver: without the sleep it doesn't work, at least not with the SPD3303D power supply.

I don't know if it makes sense to dig deeper into the cause of the problem, this could result in days of reading kernel source code and using USB logging. I would assume it is some sloppy implementation in the power supply USB connection. I don't know anyway if it is a good idea to implement the USBTMC driver in user mode with usb.core, but maybe it has more features than the kernel module. The simple solution would be to add the USBTMC kernel driver as well, if it doesn't conflict with the Python implementation, but I guess not, because it uses the low level USB PyUSB interface. The author of the 34410A script with a 34410A instrument could test this. If you integrate it as a kernel module and if it doesn't work, the module could be unloaded as default, and I can load it for my scripts.

I think this is a very good idea.  To have a bunch of python scripts in one spot on a raspberry PI.   I hope everyone contributes scripts for their devices that are not implemented yet.  Is PyVisa included in the image?   I'm just working on the Rigol DM3068 stuff.

Dwaine

Did you guys know there is some kind of kernel latency patch for the Raspberry Pi if you need it to send data as it comes in, because it's Ethernet interface is implemented via USB?


So for some kinds of uses, where USB timing is critical, you need this patch, and for others, its not the best choice. Sharing the USB bus allowed them to trim several dollars off the price. A substantial amount of money relative to other parts. So, for certain kinds of uses, other SBCs are better.

The Odroid C2 kicks a.. on ethernet (900Mb both ways)
Too bad they are loooong behind in kernel support.
C2 is one of the fastest (if not the fastest) sbc , but lacks in vendor support.

/Bingo

@Bingo
I remember you reporting in the other topic that Jessie was working for you. Might it be that you only tried it with a v1 board?
For me Jessie never worked (v3 board). I'll also give Wheezy a try.

Oldest Jessie with kernel 4.4.11 is also not working. Other adapters with uploading firmware like NI GPIB-USB-B are working properly.
Currently I trying older linux-gpib versions.

Could it be that Wheezy just soesn't support WiFi & BT on the V3 boards ??

Else maybe give Ubuntu Mate a try , that would be my next step , for distro that supports v1..v3 boards
https://www.raspberrypi.org/downloads/

And i'd expect that kernel headeres are available , instead of that incredible stupid KLUDGE you have to do on Raspbian 

/Bi

root@raspi2:/home/bingo# ./idn1.py
Traceback (most recent call last):
  File "./idn1.py", line 4, in <module>
    import Gpib
  File "/usr/local/lib/python2.7/dist-packages/Gpib.py", line 2, in <module>
    import gpib
ImportError: libgpib.so.0: cannot open shared object file: No such file or directory

****  I missed the ldconfig

root@raspi2:/home/bingo# ldconfig
root@raspi2:/home/bingo#
root@raspi2:/home/bingo# ./idn1.py
KEITHLEY INSTRUMENTS INC.,MODEL 2015,1043877,B15  /A02 

root@raspi2:/home/bingo#


**** Success on Noobs 1.4.1  - on a Raspi v1  - I disabled devicetree under advanced , but am not sure if it's needed
https://downloads.raspberrypi.org/NOOBS/images/NOOBS-2015-05-12/


uname -a
Linux raspi2 3.18.0-trunk-rpi #1 PREEMPT Debian 3.18.5-1~exp1+rpi19 (2015-08-08) armv6l GNU/Linux

Using my "old recipee"
https://www.eevblog.com/forum/reviews/using-a-raspberry-pi-with-linux-gpib-and-a-beiming-or-agilent-usb-gpib-adapter/msg329067/#msg329067

TIN's: Might be clearer
https://xdevs.com/guide/agilent_gpib_rpi/

Basically install Noobs 1.4.1 then do a : 
1: sudo apt-get update
2: sudo apt-get upgrade
3: reboot
4: sudo apt-get install linux-image-rpi-rpfv   (If you are using newer Raspberry Pi 2, please use linux-image-rpi2-rpfv)
5: reboot
6: sudo apt-get install linux-headers-$(uname -r)

Rest from the recipee

Remember
sudo apt-get install fxload


Kernel stuff to append to /boot/config.txt  (Kernel version dependant , look in /boot for the latest kernel installed)
# Set params for "raspbian debian-style kernel" boot
kernel=vmlinuz-3.18.0-trunk-rpi
initramfs initrd.img-3.18.0-trunk-rpi followkernel


Ohh - Seems like the udev "autoload firmware doesn't work"
I had to do the loads manually

******** Load firmware begin ********

lsusb
Bus 001 Device 005: ID 0957:0518 Agilent Technologies, Inc. 82357B GPIB Interface

/dev/bus/usb/001/005

#Load fw 2 times , but the id changes after first and second load

fxload -t fx2 -D /dev/bus/usb/001/008 -I /usr/share/usb/agilent_82357a/measat_releaseX1.8.hex
fxload -t fx2 -D /dev/bus/usb/001/009 -I /usr/share/usb/agilent_82357a/measat_releaseX1.8.hex

lsusb after 2'nd load
Bus 001 Device 010: ID 0957:0718 Agilent Technologies, Inc.

sudo gpib_config

If : gpib_config: error while loading shared libraries: libgpib.so.0: cannot open shared object file: No such file or directory
     You missed the : ldconfig


*** From syslog ***
Dec 17 11:43:55 raspi2 kernel: [  713.777579] usb 1-1.2: USB disconnect, device number 10
Dec 17 11:43:55 raspi2 kernel: [  713.778097] agilent_82357a_driver_disconnect: exit
Dec 17 11:43:57 raspi2 kernel: [  715.511199] usb 1-1.2: new high-speed USB device number 11 using dwc_otg
Dec 17 11:43:57 raspi2 kernel: [  715.600619] usb 1-1.2: New USB device found, idVendor=0957, idProduct=0718
Dec 17 11:43:57 raspi2 kernel: [  715.600658] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Dec 17 11:43:57 raspi2 kernel: [  715.600677] usb 1-1.2: Product: 82357B ()
Dec 17 11:43:57 raspi2 kernel: [  715.600694] usb 1-1.2: Manufacturer: Agilent Technologies, Inc.
Dec 17 11:43:57 raspi2 kernel: [  715.600712] usb 1-1.2: SerialNumber: MY49450180
Dec 17 11:43:57 raspi2 kernel: [  715.611862] probe succeeded for path: usb-bcm2708_usb-1.2
Dec 17 11:43:57 raspi2 /etc/hotplug/usb/agilent_82357a: entered for Product: 957/718/0 Device: $devnode Serial: MY.... Devpath: /devices/platform/bcm2708_usb/usb1/1-1/1-1.2
Dec 17 11:50:49 raspi2 kernel: [ 1127.274586] attached to bus interface 0, address 0xd9806800
Dec 17 11:50:49 raspi2 kernel: [ 1127.281251] agilent_82357a_attach: attached


******** Load firmware end ********

Remember to make your user member of the gpib group ,
and put  agilent_82357a in /etc/modules

Hmm .... Seems like i have to do a : sudo chmod 666 /dev/gpib*
Even though i'm a member of the gpib group .. strange


/Bingo

Have you tried the 4.x kernel on v1? If not, could you? It might be good to know whether this is a generic issue or just for the newer boards.

A while back I've tried Ubuntu Mate, without much success. I don't remember the details, probably it was my lack of Linux expertise - as if some of the commands didn't work properly. I can give it another try.
Btw, forget the Ubuntu Snappy, it is said to be not working.

I did try the latest 4.38 (Jessie) on my v1 yesterday , same problems as on my v3

Quote from: Dwaine on December 16, 2016, 10:05:39 pm

I think this is a very good idea.  To have a bunch of python scripts in one spot on a raspberry PI.   I hope everyone contributes scripts for their devices that are not implemented yet.  Is PyVisa included in the image?   I'm just working on the Rigol DM3068 stuff.

Dwaine

I have the Rigol DM3068 meter done for LAN connection.   I can test the USB setup too.  How are we doing this.  Separate scripts for each connection type or just have each connection in the python script commented out?

Dwaine

Is there a GIThub that I can do a pull request.

Go to the xDevs site and download image
https://xdevs.com/doc/_Images_RPI-DL/
Restore it on SD card. After boot go to the pub/python folder where are multiple scripts.
For test USB connection use this Test_USB.py, you needs to change the USB meter PIV/VID and run script   .


# Test USB
import usbtmc
instr =  usbtmc.Instrument("USB::0x0957::0x0a07::INSTR")
print(instr.ask("*IDN?"))

response will be something like this
pi@raspberrypi:/pub/python $ sudo python Test_USB.py
Agilent Technologies,34411A,MY12345678,2.41-2.40-0.09-46-09


For LAN there is Test_LAN.py   example.

# Test VXI11
import vxi11
instr = vxi11.Instrument("192.168.0.10")
print(instr.ask("*IDN?"))

you can add as a first line #!/usr/bin/python2
and run script by sudo ./Test_LAN.py

This Noobs 1.4.1 doesn't boot on my PI3. If you observe, the newer releases (I've checked the 2.1) have files like bcm27*, which seem to correspond to the different hardware versions. The 1.4 has no such files.

USB tested OK, so both USB and LAN are fully functional on the Rigol DM3068.   I have the Rigol DM3068 scripts working.  Is there a GITHub I can do a pull request to get the DM3068 added.  Then other people can enjoy. 

plesa created this repository:
https://github.com/PlesaEEVBlog/RPi_LogNut
@plesa please accept my pull request for the initial content, so that it doesn't get out of sync for too long.

Quote from: ManateeMafia on December 10, 2016, 09:14:38 pm

I have not tried the http.server and I would like to see how easy it is to implement.

I just tried the webserver, now I can read the value of my benchtop multimeter which has only RS232, in a webpage and even from the internet, if I would add a NAT rule to my router 

https://github.com/FrankBuss/RPi_LogNut/blob/master/pub/python/HM8012_Webserver.py

How it looks like (the real version reloads automatically every second) :



Of course, this is just a quick hack. You would not create the web pages in the Python code, but state of the art is probably to use some WebSocket API, serve local static files and then some JavaScript communicates over the WebSocket with JSON requests with the Python script.

I will also do an example web server view for the Rigol DM3068.

Nice

plesa

How do you create images? Just simple plain bit-bit clone of SDcard, or there is some tool?
I'd like to make few images too, for DE1-SoC FPGA board running linux-gpib. Got I2C working today with BME280 on it. Next step is GPIO and SPI, so I can control ADCs/DACs as well.