meloncookie
commented
2 years ago I'm sorry for the late reply.
unable to connect to the device.
Since it was written for M5Stack ATOM (Lite, Matrix), it is necessary to rewrite a part of communication.py. See the readme for details.
--- Modify communication.py ---
class Communication():
_DEFAULT_VID = 11914 # <-- this
_DEFAULT_PID = 5 # <-- thisAnd the micropython program main.py also needs to be rewritten.
--- Modify micropython main.py ---
_GROVE_PIN = {'ATOM': (32, 26),
'CORE2': (33, 32),
'BASIC': (22, 21),
'GRAY': (22, 21),
'FIRE': (22, 21),
'GO': (22, 21),
'Stick': (33, 32),
'Else': (16, 19)} # Rewrite (RxPin Number, TxPin Number) <-- For your PRi Pico
_DEVICE = 'Else' # Rewrite 'Else' <-- For your PRi PicoThe longest signal
Air conditioner signals tend to be long because they send all state variables, even if the temperature is changed.
My received signals consists of 4 values.
This would be the NEC format series.
Header frame => ON: 16T, OFF: 8T (Top of the signal) Bit data Low => ON: T, OFF: T Bit data High => ON: T, OFF: 3T
T = 562[usec]
after which the actual command is sent?
The header frame is followed by the data.
0001: 8,896 # 0002: 4,448 # HEADER 16T/8T 0003: 556 # 0004: 1,668 # T/3T = 1 0005: 556 # 0006: 1,668 # T/3T = 1 0007: 556 # 0008: 556 # T/T = 0 0009: 556 # 0010: 556 # T/T = 0 ...
Demodulated signal = 1100...
Please refer to here. In the case of air conditioners, the signal length is long, so it is derived from the strict NEC format.
the last highest bit is on 210 ... power state bit ...
I couldn't understand here. power state bit???
I hope it helps you even a little.
Vendelator
I have been at it for days now without success, i think i need some help.
I am using the Raspberry Pi Pico board for this project, the latest firmware.
I am using this module to send the signal: https://www.electrokit.com/uploads/productfile/41015/41015733_-_IR_Transmitter_Module.pdf (and this one to receive: https://www.electrokit.com/uploads/productfile/41015/41015734_-_IR_Receiver_Module.pdf)
The transceiver is 5V, but is supposed to work with 3V. The TX Signal is connected to GPIO 19 and RX Signal to GPIO 16.
When sending a signal through python directly, the receiver reacts to something being sent. Both List and Tuple seems to yield the same results.
When using GUI, i am able to Record, but unable to Send, and i am prompted with an error message saying it's unable to connect to the device. From what i can tell, this error is generated when signalframe.py uses
def _send(self):uses commonication.pyif not self._communication.is_connect(): if not self._communication.connect(): messagebox.showerror('Error', "Can't connect device.") self._edit_on() returnI am using the standard pid and vid.
I have tried changing idle back and forth in the Micropython UpyIrTx.
The longest signal i have been able to acquire as of now is 211 long. Over several attempts it seems that if properly recorded, the last highest bit is on 210, but most often it barley reaches 158, which i am assuming is the power state bit, If its low, it enters power saving.
My received signals consists of 4 values. Two which happens initially, and two other through out the code. I am assuming the first part is to make the AC-unit know that it is supposed to receive a signal at all, after which the actual command is sent?