¿ªÔÆÌåÓý

Help needed programming 34972A Data Acquisition/Switch Unit


 

Hi all,

I am currently programming a 34972A Data Acquisition/Switch Unit that contains 3x 34901A modules to scan cell voltages in battery packs.
I am building the configuration file in BenchLink Data Logger 3 and transferring the resulting 'config.blcfg' config file to the instrument with a USB stick and using said stick to save the measured data.

I have the scanning, measuring and saving working fine so far, no problems there, but I'm looking for a way to display messages to the user on the instrument display during and at the end if the scan ("Scanning..." and "Scan Complete" respectively) along with beeps to alert the operator to a finished scan as one scan takes a few minutes to complete.

I know I can do this by directly sending commands to the instrument via an attached computer, but this needs to be a portable solution for field use with a minimum of parts (Hence using the USB stick), so no PC/Raspberry Pi/etc can be used here.


Does anyone have any experience with programming these instruments who can help me out with displaying messages and making beeps when using only the aforementioned USB stick and config file?



Thanks!
Jared


 

Been playing around a bit tonight, and found something...

When I apply my config file from the USB stick and press scan, it all works as expected, but I never get the 'Scanning...' display as is apparently expected, only the 'mux VDC' as shown before the scan started.

So I made a simple 3 channel program from the front panel set to automatically loop a few times and found it doesn't say 'Scanning' on the first run through, but does so on subsequent scans. It also does the same no matter how I load the program into the instrument, via PC connection, USB memory stick or front panel.
As my program runs only once through at a time, it never shows 'Scanning' as it never gets to a second scan. I wonder why it never says 'Scanning' on the first run-through? A bug or my misconfiguration somewhere? (I'm running v1.17 firmware, the latest I think?)