Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Axima Qualcosonic - q400 driver does not work #1221

Open
PhilippGrashoff opened this issue Mar 27, 2024 · 1 comment
Open

Axima Qualcosonic - q400 driver does not work #1221

PhilippGrashoff opened this issue Mar 27, 2024 · 1 comment
Labels
device support Request for new device support or existing driver improvement Stale

Comments

@PhilippGrashoff
Copy link

Type of request

Existing device improvement

Meter description

I am trying to read telegrams from Axioma Qualcosonic W1 meters.
These WmBus telegrams received are a sligthly different format than the ones in the q400 driver. Some decrypted telegrams are listed below.
wmbusmeters cannot parse them with the q400 driver and also does not find another suitable driver when setting the device to driver=auto. The message in the log is:

Started config im871a[00104623] on /dev/ttyUSB0 listening on t1,c1
(meter) Axioma_06425771: meter detection did not match the selected driver q400! correct driver is: unknown!
(meter) Not printing this warning again for id: 06425771 mfct: (AXI) UAB Axis Industries, Lithuania (0x709) type: Water meter (0x07) ver: 0x01
(meter) please consider opening an issue at https://github.com/wmbusmeters/wmbusmeters/
(meter) to add support for this unknown mfct,media,version combination 

The telegrams however seem to be valid OMS: Running them trough a generic OMS Parser returns parsed data like:

BUFFER(68): 434409077157420601078C203D900F002C253D6C0400663BF3F234EB1F6A7A3D002007102F2F046D21081A330413CECE0100446D000001334413979301002F2F2F2F2F2F
DECRYPTED DATA(32):2F2F046D21081A330413CECE0100446D000001334413979301002F2F2F2F2F2F
IDENTIFICATION
	- Product name: AXI_1	
	- Serial number: AXI0106425771	
	- Medium: Water	
	- Generation: 1	
	- Device time: 26.03.2024 08:33:00	
	- Device time deviation: 1 day, 5 hours, 13 minutes	
VALUES
	- 2024-03-27 13:46:33 Volume: 118.478 m³	
LOGGER
	- 2024-03-01 00:00:00 Volume: 103.319 m³	Storage 1

If you give me a hint how to improve the q400 driver (or adding a new Q1 driver?), I could create a PR to get this working.

Thanks & best regards

Logged telegrams from meter in decrypted format

434409077157420601078C203C900F002C253C6C0400638D7C07E590614C7A3C002007102F2F_046D20081A330413CECE0100446D000001334413979301002F2F2F2F2F2F
434409077157420601078C203D900F002C253D6C0400663BF3F234EB1F6A7A3D002007102F2F_046D21081A330413CECE0100446D000001334413979301002F2F2F2F2F2F
434409077157420601078C203E900F002C253E6C040045DE27E3C2314F087A3E002007102F2F_046D21081A330413CECE0100446D000001334413979301002F2F2F2F2F2F
434409077157420601078C203F900F002C253F6C0400CF2AEAA77EDB90A27A3F002007102F2F_046D21081A330413CECE0100446D000001334413979301002F2F2F2F2F2F
@PhilippGrashoff PhilippGrashoff added the device support Request for new device support or existing driver improvement label Mar 27, 2024
Copy link

This issue is stale because it has been open for 2 month with no activity. Remove stale label or comment or this will be closed in 1 month.

@github-actions github-actions bot added the Stale label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device support Request for new device support or existing driver improvement Stale
Projects
None yet
Development

No branches or pull requests

1 participant