Works!
What format to choose? ASCII,HEX or something else?
What format to choose? ASCII,HEX or something else?
Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
p.kaczmarek2 wrote:Wait, is it possible to change reporting interval on that device or not?
p.kaczmarek2 wrote:Is that a capture from TXD1 of WiFi module? It seems so. There is no humidity, no temperature data. You can get that data if you capture on RXD1.
p.kaczmarek2 wrote:But still, dpIds are known for that device, the only question still pending is is there a packet for report interval configuration?
superjedi wrote:
Is there any standard way (standard, as in, tuya protocol) to configure the MCU for a particular wakeup interval ?
чип UNICMICRO UM8005 отправляет данные при изменении температуры на заданный в приложении smart life интервал.
ionoleinic wrote:I have captured again TuyaMCU packets.
On Pairing with Tuya App:
55 AA 00 02 00 00 01 55 AA 00 02 00 00 01 55 AA 00 02 00 00 01 55 AA 00
08 00 0F 00 01 01 01 01 01 01 01 02 00 04 00 00 01 00 24 55 AA 00 08 00
0F 00 01 01 01 01 01 01 02 02 00 04 00 00 00 3A 5E 55 AA 00 08 00 0C 00
03 03 03 03 03 03 03 04 00 01 02 2F 55 AA 00 10 00 02 01 09 1B 00
ionoleinic wrote:
On Restart:
55 AA 00 01 00 24 7B 22 70 22 3A 22 6C 66 33 36 79 35 6E 77 62 38 6A 6B
78 77 67 67 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D 99 55 AA 00 02 00
00 01 55 AA 00 02 00 00 01 55 AA 00 08 00 0F 00 01 01 01 01 01 01 01 02
00 04 00 00 00 FB 1E 55 AA 00 08 00 0F 00 01 01 01 01 01 01 02 02 00 04
00 00 00 3C 60 55 AA 00 08 00 0C 00 03 03 03 03 03 03 03 04 00 01 02 2F
55 AA 00 10 00 02 01 09 1B 00
ionoleinic wrote:
On Button Pressed:
55 AA 00 01 00 24 7B 22 70 22 3A 22 6C 66 33 36 79 35 6E 77 62 38 6A
6B 78 77 67 67 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D 99 55 AA 00 02
00 00 01 55 AA 00 02 00 00 01 55 AA 00 08 00 0F 00 01 01 01 01 01 01 01
02 00 04 00 00 00 FA 1D 55 AA 00 08 00 0F 00 01 01 01 01 01 01 02 02 00
04 00 00 00 34 58 55 AA 00 08 00 0C 00 03 03 03 03 03 03 03 04 00 01 02
2F 55 AA 00 10 00 02 01 09 1B 00
ionoleinic wrote:
Reporting:
55 AA 00 01 00 24 7B 22 70 22 3A 22 6C 66 33 36 79 35 6E 77 62 38 6A 6B
78 77 67 67 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D 99 55 AA 00 02 00
00 01 55 AA 00 02 00 00 01 55 AA 00 08 00 0F 00 01 01 01 01 01 01 01 02
00 04 00 00 00 FC 1F 55 AA 00 08 00 0F 00 01 01 01 01 01 01 02 02 00 04
00 00 00 39 5D 55 AA 00 08 00 0C 00 03 03 03 03 03 03 03 04 00 01 02 2F
55 AA 00 10 00 02 01 09 1B 00
ionoleinic wrote:
Now i can flash module with OpenBeken?
p.kaczmarek2 wrote:Wait, is it possible to change reporting interval on that device or not?
"{{ ((value | float * 0.1 | round(1))) }}"
startDriver tuyaMCU
startDriver tmSensor
linkTuyaMCUOutputToChannel 1 val 1
setChannelType 1 Temperature_Div10
linkTuyaMCUOutputToChannel 2 val 2
setChannelType 2 Humidity
Xinayder wrote:
First, the battery powered temp and humidity sensor is just like the OP one except that the PCB is a bit different. The sensor used is a AHT20 and there's a TuyaMCU module as well. I soldered the wires and tried to connect it to my programmer and a weird behavior occurred.
Xinayder wrote:
Whenever I'd power the sensor with the UART programmer (both 3v3 and GND), the DRX and DTX LEDs of the programmer would blink at a low intensity. The programmer stopped being detected by my system. As soon as I removed one of the power wires it was detected again.
Xinayder wrote:
I found out that the TX pin of the CB3S is connected to pin 15 of the TuyaMCU chip, but the RX isn't connected anywhere on the chip. There are 2 vias on the PCB labeled TX2 and RX2 which are connected to the TX1/RX1 pins of the wifi module.
Xinayder wrote:
(yes I know the solder is bad, I was experimenting with my brand new iron that I got from aliexpress).
Xinayder wrote:
p.kaczmarek2 wrote:Maybe there is a 100ohm resistor on the way?
p.kaczmarek2 wrote:can you do a UART packet capture first (in hex string mode, both from rx and tx) for further analysis before flashing obk?
Also do 2MB firmware backup.
Xinayder wrote:
For that reason I can't even do a firmware dump because it can't read data from the sensor. I tried plugging the GND to the programmer and powering the sensor with the batteries but no luck either.
p.kaczmarek2 wrote:Xinayder wrote:
For that reason I can't even do a firmware dump because it can't read data from the sensor. I tried plugging the GND to the programmer and powering the sensor with the batteries but no luck either.
Doing firmware backup will not work with TuyaMCU on board. You first have to cut the trace or desolder TuyaMCU or desolder WiFi module.
Doing packets capture should work.
Please show your wiring connections...
Quote:
The USB port keeps popping up and disappearing, as if I was unplugging and replugging the programmer several times a second.
p.kaczmarek2 wrote:You can fix soldering job, just apply flux now, fix joints, clean PCB with IPA.
How was the antenna damaged? Maybe you can fix it by doing a short jumper with solder.
Was TXD11 damaged on wifi module board or on the mother board?
Quote:
The USB port keeps popping up and disappearing, as if I was unplugging and replugging the programmer several times a second.
do you have USB doctor? Maybe something is taking too much current.
p.kaczmarek2 wrote:It might be missing from template, you may need to set it yourself by looking at this topic.
If you have a github account, you can also add a correct config with a pull request.
crashyourself22 wrote:I don´t know which pins i have to configure in OBK and how tzo receive the data from the IC.
I´m using the same board as @minusync
