Yardstick One code

[evilpete]

code to send / receive with Yardstick One

requires rfcat library

the code ain't pretty but i works

secplus_v2-send.py send security+ v2 secplus_send.py send security+ (v1) secplus_v2_reciv.py receive security+ v2

was too lazy to write receive security+ (v1) :-)

Enjoy...

usage: secplus_v2-send.py [-h] [-F FREQ] [--rolling ROLLING] [-b button_id] [-n] [-f fixed_code | -i remote_id] [-v]

optional arguments:
  -h, --help            show this help message and exit
  -F FREQ, --Freq FREQ, --freq FREQ
                        Set Frequency [default=315000000]
  --rolling ROLLING     Set Rolling code [default=0]
  -b button_id, --button button_id
                        Button [default=91]
  -n, --noop            No op/Do not transmit
  -f fixed_code, --fixed fixed_code
                        Set Fixed code [default=0]
  -i remote_id, --id remote_id
                        Remote-ID
  -v, --verbose         Increase debug verbosity

[argilo]

Both transmit scripts are failing here.

secplus_send.py:

Exception: Packet too large (1800 bytes). Maximum fixed length packet is 510 bytes.

secplus_v2-send.py

Exception: Packet too large (1148 bytes). Maximum fixed length packet is 510 bytes.

[evilpete]

that's odd I'll test it again tonight and also check the HW firmware version.

On Thu, Jan 12, 2023, 15:44 Clayton Smith @.***> wrote:

Both transmit scripts are failing here.

secplus_send.py:

Exception: Packet too large (1800 bytes). Maximum fixed length packet is 510 bytes.

secplus_v2-send.py

Exception: Packet too large (1148 bytes). Maximum fixed length packet is 510 bytes.

— Reply to this email directly, view it on GitHub https://github.com/argilo/secplus/pull/16#issuecomment-1381112069, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASFLKNVJDXZR2LU7WYU5NDWSCJOZANCNFSM6AAAAAATVFVUYI . You are receiving this because you authored the thread.Message ID: @.***>

[argilo]

Oof, I did some playing and quickly reminded myself how buggy and unreliable rfcat is. I'm not sure it's worth the trouble of adding support for it. :disappointed:

[evilpete]

i have some work in Koto correct but I find time, I think I pushed the wrong branch before (sorry is low priority)