@Sebastian do ou use a ttl converter vor 3.3V or 5V?
you need one for 3.3V
i am using SSCOM:
https://www.gps4pets.de/de/downloads/SSCOM.zip
just got a new pet tracker 4g today and rewriting the h02 protocol
i am using a ch340 3.3V USB2TTL interface.
tested a pl2303 but that had the same problem like you
I tried two pl2303 and in this moment an ch340 3.3V interface. the problem persists, reading of bootloader and other messages works, sending an command (was corectly echoed by device self) returns nothing.
I was sending AT%TEST=START#
@GPS4PETS With an windows laptop and your SSCOM it works :D
good to hear.
the trackers are a bit picky
@GPS4PETS thanks for your support and software!
@GPS4PETS did you manage to get light and sound activated via protocol / traccar commands?
i am at debugging stage.
one tracker is bound to original paj portal and i sniff traffic via the onboard usb interface of the lte modul
i will publish all my findings here
it reacts on S20 commands (curoff / recover engine).
but not on other standard commands like S26 for device information or CR for sending location
Found this for controlling light and sound with h02 protocol:
light on
*HQ,YYYYYYYYYY,X2,062108,1#
light off
*HQ,YYYYYYYYYY,X2,062108,0#
sound on
*HQ,YYYYYYYYYY,X1,062108,DURACTION_IN_SECONDS#
sound off
*HQ,YYYYYYYYYY,X1,062108,0#
YYYYYYYYYY = your tracker ID
livemode on
*HQ,YYYYYYYYYY,X5,062108,5,DURATION_IN_SECONDS#
livemode off
*HQ,YYYYYYYYYY,X5,062108,5,10#
WiFi Scan
*HQ,YYYYYYYYYY,CHWALL,062108,#
@GPS4PETS light and sound works with your commands and original firmware, great!
Clever idea to sniff the commands on the interface ;)
@GPS4PETS: strange, i can see the messages on boot and shutdown, but commands send by serial do nothing. I testet two of my usb ttl converters without success :(