Hello,
after an evaluation, the information given in the wiki regarding the support of
the PCE PCE-322A [1] led to an investment [2]. Tests with the installation
packages available on the part of Ubuntu 20.04 & 22.04 were unfortunately
unsuccessful and only the use of all successfully compiled master branches of
libserialport, libsigrok and sigrok-cli let me successfully communicate with
the device.
./sigrok-cli --driver pce-322a:conn=/dev/ttyUSB0 --scan
The following devices were found:
pce-322a - PCE PCE-322A with 1 channel: SPL
./sigrok-cli --driver=pce-322a:conn=/dev/ttyUSB0 --show
Driver functions:
Sound level meter
Scan options:
conn
pce-322a - PCE PCE-322A with 1 channel: SPL
Supported configuration options:
continuous: on, off
limit_samples: 0 (current)
spl_weight_freq: A (current), C
spl_weight_time: F (current), S
spl_meas_range: 30-130 (current), 30-80, 50-100, 80-130
power_off: on, off (current)
data_source: Live (current), Memory
However, this is where the problems start because even testing to change
configurable values fails and subsequent getter calls always returned the
default value.
./sigrok-cli --driver=pce-322a:conn=/dev/ttyUSB0 --config spl_weight_time=S
--set --show
...
spl_weight_time: F (current), S
...
./sigrok-cli --driver=pce-322a:conn=/dev/ttyUSB0 --get spl_weight_time
'F'
More importantly, however, the attempt to read out the "live data" of the
device was unfortunately unsuccessful. At the beginning of a reading process
there are small differences in the first bytes (see the beginning of the
following three measurements), but after that you only get "0" as information.
My hope was to get at least a usable value of the device, unfortunately the
value displayed by the device is in no way comprehensible with the data sent
via USB. Only the activation or deactivation via device "Setup" button allows
the data transmission to the computer to start or stop.
cutecom /dev/ttyUSB0
00000000 00 fd 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000016 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000032 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000048 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
...
00000000 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ␈
00000016 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000032 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000048 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
...
00000000 06 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ␆␒
00000016 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000032 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000048 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
...
Upon inquiry in #sigrok IRC, I was told that there is evidence of newer
PCE-322A devices with a different protocol that does not seem to be compatible
with the one supported by sigrok.
My tests so far could not find a cause, but there are documents (unknown age)
that differ at least from the command set implemented by sigrok and the images
in the sigrok wiki clearly differ from a newer variant. [3][4]
Kind regards
[1] https://sigrok.org/wiki/PCE_PCE-322A
[2]
https://www.pce-instruments.com/english/measuring-instruments/test-meters/decibel-meter-pce-instruments-decibel-meter-pce-322a-det_5840592.htm
[3]
https://www.pce-iberica.es/medidor-detalles-tecnicos/protocolo-interfaz-pce-322a.pdf
[4]
https://www.pce-italia.it/html/dati-tecnici-1/link/protocolo-interfaz-pce-322a.pdf
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
