Can't configure the time (or anything actually) on a RC-5+, reading parameters works just fine

[Fescron]

Hello, your code seems to work perfectly for getting parameters but I can't seem to set any. ConfigWriteCommand seems to be called correctly, but the values are not being set... My device has firmware version 0x52, not sure if this could explain why the device is supposedly tested but mine won't take new settings?

Furthermore, there are some typos in the line to (in theory) set the device time: python elitech --device [/dev/path] parameter<s> <get> configuration-time "$(date '+%Y-%m-%d %H:%M:%S')" -> python elitech --device [/dev/path] parameter set configuration-time "$(date '+%Y-%m-%d %H:%M:%S')"
Actually, parameters needs to become parameter for every example-command.

Thanks for the code, I hope I can get it working so I don't have to use the proprietary Windows-application to set the time after not having used the device in a while :)

[pasccom]

Hello, that is strange (I retried successfully just now on my own device), but can be explained by the new firmware version, I suppose. I also noticed that they published a new software for Windows (v7.2.2 whereas I analyzed v6.2.0). I will try to look into it. It should not be so hard for me as it is in the same language and seems to have a similar architecture. However, I cannot tell you when I will finish.
Anyway, I would be interested by the following data (to add your device to an unsupported list):

• Name of the device
• USB vendor id (should still be 0x04d8)
• USB product id
• model

The 3 first should be obtained from python elitech device list, the last using python elitech --device [/dev/path] parameter get model. I also would be interested in the request and the response used to set the configuration-time.
Thanks for the typos in the README, I corrected them.

[Fescron]

Hello again, thank you for the quick response!

The VID & PID remained the same compared to your supported list, I checked some time ago with lsusb, but I'll list it just to be sure using your proposed program calls:

python3 elitech device list

DeviceListCommand
Available devices:
/dev/hidraw4: Elitech RC-5+ (04d8:3005)

python3 elitech --device /dev/hidraw4 parameter get model

ConfigReadCommand(Device('/dev/hidraw4'), "model")
[[0, 2)]
Request:  00 33 CC 00 0C 03 00 00 00 00 00 02 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 00 00 02 30 05 47 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
model: 0x3005

python3 elitech --device /dev/hidraw4 parameter set configuration-time "$(date '+%Y-%m-%d %H:%M:%S')"

ConfigWriteCommand(Device('/dev/hidraw4'), "configuration-time=2024-06-28 21:59:45")
[[40, 47)]
Request:  00 33 CC 00 0C 03 00 00 00 28 00 07 3D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 13 03 00 00 00 28 00 07 17 0B 04 17 09 37 01 C2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[Response[40, 47)]
Request:  00 33 CC 00 13 04 00 00 00 28 00 07 18 06 00 1C 15 3B 2D FC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0D 04 00 00 00 28 00 01 01 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Additionally some info from the latest generated PDF:

• Device Code: RC-5+
• Mode Code: TLC30A08B
• Firmware Version: V5.2

Thanks again for creating the code and for the quick response!

[pasccom]

Thanks for the even quicker response! Indeed your device seems to be exactly the same as mine... Except for the firmware version.
What is strange is that it does not return an error code... The response is identical to mine.

[Fescron]

Yes indeed it is strange behavior. I tried setting other parameters too (travel-number for example) but it always seems to work but when getting the parameters again they are unchanged :/

[Fescron]

Ah yes, I did however find a command which doesn't seem to work as expected:

python3 elitech --device /dev/hidraw4 record get 1:

RecordReadCommand(Device('/dev/hidraw4'), slice(0, None, None))
(0, 6, 6)
Request:  00 33 CC 00 0C 01 00 00 00 00 00 06 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0C 01 00 00 00 00 00 00 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/.../python-elitech-master/elitech/src/frames.py:162: UserWarning: Answer length does not match: 0 != 6
  warning(f"Answer length does not match: {answer[10]} != {l}")

[pasccom]

Hello, I finally finished checking the official code for some changes that they made in the new version. It took me quite some time, because I was a bit busy and I had to update the plugins I used to disassemble the byte-code.
Here are my findings:

• For parameter settings: I don't find any major changes, but for the dates they now explicitly specify the day of week (Sunday, Monday, ...). For travel-number, the length was not correct, so maybe the device was not happy when it expected a string padded to 13 bytes and he got only 7. Also, I don't do as the official software does: The official software gets the whole config and sets the whole config after modifying it, whereas I try to change only the desired parameters. Maybe this mode of operation is simply not supported anymore in the new firmware version.
• For records: It seems that the format for the records has changed, which may explain why it does not answer (records are now 4 bytes whereas they were 6 bytes previously)

If you have some time to devote to some trials, here is what you could do:

• Can you give me protocol-version ?
• Try to set the date of a Sunday (I send a 0 for day of week, which corresponds to Sunday)
• Try to set travel-number with the latest version, up to 13 chars (it is zero-padded)
• Try to change interval parameter to 1m (one minute) or 30s (30 seconds)
• Ensure there are at least 4 records in memory (read record-number) and try to read 4 records

(always read again to check whether it changed and send me the buffers)

Also, if you installed the official software, I would be interested by the records of the buffers if you know how to do it (Wireshark should be able to do this).
Best regards,

[Fescron]

Hello, no worries! Although I was starting to wonder if I should send you a reminder or something 😅 Thanks again for all the work!

Here are my findings:

python3 elitech --device /dev/hidraw9 parameter get protocol-version

ConfigReadCommand(Device('/dev/hidraw9'), "protocol-version")
[[149, 150)]
Request:  00 33 CC 00 0C 03 00 00 00 94 00 02 A4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 94 00 02 40 38 1E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
protocol-version: 0x38

python3 elitech --device /dev/hidraw9 parameter get device-time

ConfigReadCommand(Device('/dev/hidraw9'), "device-time")
[[136, 143)]
Request:  00 33 CC 00 0C 03 00 00 00 88 00 07 9D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 13 03 00 00 00 88 00 07 18 08 00 14 13 13 35 33 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
device-time: 2024-08-20 19:19:53


python3 elitech --device /dev/hidraw9 parameter set configuration-time "2024-08-18 13:00:00"

ConfigWriteCommand(Device('/dev/hidraw9'), "configuration-time=2024-08-18 13:00:00")
[[40, 47)]
Request:  00 33 CC 00 0C 03 00 00 00 28 00 07 3D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 13 03 00 00 00 28 00 07 17 0B 04 17 09 37 01 C2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[Response[40, 47)]
Request:  00 33 CC 00 13 04 00 00 00 28 00 07 18 08 00 12 0D 00 00 84 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0D 04 00 00 00 28 00 01 01 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


python3 elitech --device /dev/hidraw9 parameter get device-time

ConfigReadCommand(Device('/dev/hidraw9'), "device-time")
[[136, 143)]
Request:  00 33 CC 00 0C 03 00 00 00 88 00 07 9D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 13 03 00 00 00 88 00 07 18 08 00 14 13 14 24 23 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
device-time: 2024-08-20 19:20:36

# NOTE: The "configuration-time" remained unchanged

python3 elitech --device /dev/hidraw9 parameter get travel-number

ConfigReadCommand(Device('/dev/hidraw9'), "travel-number")
[[16, 29)]
Request:  00 33 CC 00 0C 03 00 00 00 10 00 0D 2B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 19 03 00 00 00 10 00 0D 30 30 30 30 30 30 31 00 00 00 00 00 00 89 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
travel-number: 0000001


python3 elitech --device /dev/hidraw9 parameter set travel-number 0000002

ConfigWriteCommand(Device('/dev/hidraw9'), "travel-number=0000002")
[[16, 29)]
Request:  00 33 CC 00 0C 03 00 00 00 10 00 0D 2B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 19 03 00 00 00 10 00 0D 30 30 30 30 30 30 31 00 00 00 00 00 00 89 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[Response[16, 29)]
Request:  00 33 CC 00 19 04 00 00 00 10 00 0D 30 30 30 30 30 30 32 00 00 00 00 00 00 8B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0D 04 00 00 00 10 00 01 01 22 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


python3 elitech --device /dev/hidraw9 parameter get travel-number

ConfigReadCommand(Device('/dev/hidraw9'), "travel-number")
[[16, 29)]
Request:  00 33 CC 00 0C 03 00 00 00 10 00 0D 2B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 19 03 00 00 00 10 00 0D 30 30 30 30 30 30 31 00 00 00 00 00 00 89 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
travel-number: 0000001


python3 elitech --device /dev/hidraw9 parameter set travel-number 0000000000002

ConfigWriteCommand(Device('/dev/hidraw9'), "travel-number=0000000000002")
[[16, 29)]
Request:  00 33 CC 00 0C 03 00 00 00 10 00 0D 2B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 19 03 00 00 00 10 00 0D 30 30 30 30 30 30 31 00 00 00 00 00 00 89 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[Response[16, 29)]
Request:  00 33 CC 00 19 04 00 00 00 10 00 0D 30 30 30 30 30 30 30 30 30 30 30 30 32 AB 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0D 04 00 00 00 10 00 01 01 22 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


python3 elitech --device /dev/hidraw9 parameter get travel-number

ConfigReadCommand(Device('/dev/hidraw9'), "travel-number")
[[16, 29)]
Request:  00 33 CC 00 0C 03 00 00 00 10 00 0D 2B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 19 03 00 00 00 10 00 0D 30 30 30 30 30 30 31 00 00 00 00 00 00 89 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
travel-number: 0000001

python3 elitech --device /dev/hidraw9 parameter get interval

ConfigReadCommand(Device('/dev/hidraw9'), "interval")
[[76, 78)]
Request:  00 33 CC 00 0C 03 00 00 00 4C 00 02 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 4C 00 02 00 0C 6A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
interval: 2m


python3 elitech --device /dev/hidraw9 parameter set interval 1m

ConfigWriteCommand(Device('/dev/hidraw9'), "interval=1m")
[[76, 78)]
Request:  00 33 CC 00 0C 03 00 00 00 4C 00 02 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 4C 00 02 00 0C 6A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[Response[76, 78)]
Request:  00 33 CC 00 0E 04 00 00 00 4C 00 02 00 06 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0D 04 00 00 00 4C 00 01 01 5E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


python3 elitech --device /dev/hidraw9 parameter get interval

ConfigReadCommand(Device('/dev/hidraw9'), "interval")
[[76, 78)]
Request:  00 33 CC 00 0C 03 00 00 00 4C 00 02 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 4C 00 02 00 0C 6A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
interval: 2m

python3 elitech --device /dev/hidraw9 parameter get record-number

ConfigReadCommand(Device('/dev/hidraw9'), "record-number")
[[72, 74)]
Request:  00 33 CC 00 0C 03 00 00 00 48 00 02 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 48 00 02 01 55 B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
record-number: 0x0155


python3 elitech --device /dev/hidraw9 record get 1:10

RecordReadCommand(Device('/dev/hidraw9'), slice(0, 10, None))
(0, 6, 6)
Request:  00 33 CC 00 0C 01 00 00 00 00 00 06 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0C 01 00 00 00 00 00 00 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/home/brecht/Qsync/Documents/Python/python-elitech/elitech/src/frames.py:162: UserWarning: Answer length does not match: 0 != 6
  warning(f"Answer length does not match: {answer[10]} != {l}")
(6, 4, 4)
Request:  00 33 CC 00 0C 01 00 00 00 06 00 04 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

# NOTE: The command "hangs", I have to "Ctrl+C" to return to the terminal

Response: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
python-elitech/elitech/src/commands.py:493: UserWarning: Got invalid response (Invalid answer header: 00 00 00)
  warning(f"Got invalid response ({str(e)})")

Sooo... regarding parameters everything unfortunately seems to be the same... Regarding the records I think the behaviour is slightly different?

Just to be sure, I cloned this whole repository in another folder, and also used git submodule update --init to clone the submodules (I think I did that "manually" before). All above commands are executed there. Also python3 elitech -v yields elitech 0.0.

[Fescron]

And regarding the official software/Wireguard, as their application is unfortunately not available on Ubuntu which I daily drive (22.04(.04) LTS) I don't have that installed (hence why I searched for something like this). I initially got the device and configured it on my work computer which does run Windows, but I removed it thereafter since it seemed to also change some drivers for other devices also plugged in to that computer. I suppose I could install it again and perform some more testing if that could help you (and me as well in the future :) )?

[pasccom]

Hi! Thanks for the really quick response.
Annoying that nothing works for the set command :'(. I did not see any configuration locking mechanism. Maybe I will try to reproduce exactly the requests they send to set the configuration.
Regarding the records, could you try to read only 4 records? So that the data fits in one single answer buffer.
Regarding the official software, I am also on Linux (openSUSE Tumbleweed), that is why I had to reverse engineer the official firmware. I was not totally sure that I could install it even using WINE or in a virtual machine (due to the drivers). If you ever have the opportunity to record the USB frames, that would be very helpful!

[Fescron]

So you mean this?

python3 elitech --device /dev/hidraw9 record get 1:3

RecordReadCommand(Device('/dev/hidraw9'), slice(0, 3, None))
(0, 3, 3)
Request:  00 33 CC 00 0C 01 00 00 00 00 00 03 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0C 01 00 00 00 00 00 00 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
python-elitech/elitech/src/frames.py:162: UserWarning: Answer length does not match: 0 != 3
  warning(f"Answer length does not match: {answer[10]} != {l}")

Now I don't have to Ctrl+C to get back to the terminal...

Regarding the USB frames, I work as an electronics engineer and it's possible we have a USB analyzer at my company. I suppose the ideal setup would be: Windows PC running the vendor supplied software <-> USB analyzer recording the frames during configuration <-> Elitech RC-5+?

[pasccom]

Hello!
As I was looking into the special commands (format device, stop device, ...), I was wondering whether your device is still recording data? Also can you check the device-state ? I am not yet sure of the meaning of all values, but this might give me some insight.
Yes, if you have a logic analyzer at work with the adequate cable, it will do the job (Wireshark with USB Pcap is a software USB analyzer, which may be simpler to deploy).

[Fescron]

Hello again, no the device is stopped, because when I plug it into a PC its internals heat up quite a bit resulting in inflated temperature measurements... I will retry all previous commands with the device running? As far as I remember during previous tests device-state yielded stopped or something.

[pasccom]

Hi! Could you retry reading the device state and record the exchange? And then simply retry to write something in interval parameter.

[Fescron]

Well, turns out it doesn't result in stopped, but in an error ( I was testing it out/writing this message as your comment came in).

python3 elitech --device /dev/hidraw9 parameter get device-state

ConfigReadCommand(Device('/dev/hidraw9'), "device-state")
[[37, 38)]
Request:  00 33 CC 00 0C 03 00 00 00 24 00 02 34 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Response: 33 CC 00 0E 03 00 00 00 24 00 02 01 09 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
python-elitech/elitech/src/parameters.py:280: UserWarning: Invalid value for enum parameter: 0x09
  warning(f"Invalid value for enum parameter: 0x{s}")
device-state: 

I also tried plugging the device in when it is taking measurements, but all previous commands seem to get exactly the same results (no errors, but also no saved parameters, while the record-number parameter increases).

Regarding the USB packet logging, as I have to install the software again and setup the analyser takes a bit more time than I currently have, I'm not sure when I'll get around to it :/ Keep you posted! Thanks again for everything so far!

[pasccom]

Hello!
I was expecting that it would return an error (because that was not programmed). I could confirm this morning that 9 is indeed stopped and that it should be able to set parameters in this mode. I was also expecting it not to allow writing parameters while it is recording. Surprising that it does not return an error code though. I think that is how I got them.
Regarding USB packet logging, it is not an issue, take your time! I don't know whether other people are using the library and it works for me. In the meantime, I will check whether they do something special at the HID layer (I may have missed that) and I will program the parameters settings as the software does (but later, because I don't have a device available right now)