Quote:
Originally Posted by basilisk
The LED on the module lights up when the buttons on the remote are pressed, but the resistance between ground and any of the SWC pins doesn't change when I press the buttons (it's a poor test, I know - if the unit sends only short commands, they may be too short to be detected by my cheap multimeter). I've checked the resistance between SWC1 and SWC2 on the HU and it was infinity - which leaves me with not too many other things to try.
|
You can't try to measure resistance on a circuit that is powered. You could try measuring voltage -- on either the HU's SWC1 or SWC2 pin with respect to ground (test one SWC pin at a time). When the OESWC-RF module is not sending a command, or when nothing is connected, you'll probably see the HU outputting +5V. When the module sends a command, the voltage should drop to something between 0 and 5V (different value for each button).
But if the module is not detecting the HU, it likely won't even try sending commands to the HU.
Quote:
|
PS: Do I understand correctly that ASWC-1 can be manually forced to use a specific set of commands and not try to do the whole "auto-detect" thing with a FT HU? If I won't be able to make the OESWC module work, then at least I will have another option!
|
Yes. Except ASWCs talk to aftermarket HUs. They won't talk to an OEM HU (as far as i know).
On an ASWC, you can also use their app for Android phones to pre-program the module via its USB port (or go back and remap buttons if you decide you want to change something, or change to a different aftermarket HU brand). That lets you skip going through the ASWC's auto-programming sequence in the car.