Figuring out the OFA URC7980
Moderator: Moderators
Raw download I tried so many times... "No remotes found!" No matter the orientation of the socket on the remote.
But I did notice that when I connect the remote reversed (marked pin is 6) but not connect the USB part, the two LED's on the USB part light up dimmed.
So I assume that the marked pin is 1.
The interface in RMIR is set to Auto-detect.
Any other ideas?
But I did notice that when I connect the remote reversed (marked pin is 6) but not connect the USB part, the two LED's on the USB part light up dimmed.
So I assume that the marked pin is 1.
The interface in RMIR is set to Auto-detect.
Any other ideas?
OK,
Let's go under the assumption that it is a JP1.4, JP1.4N, JP2, or JP3 remote. We have a tool called JP2Sniffer that allows you to better control the sequence of events compared to RMIR.
Plug in your cable, start JP2Sniffer, tell it which Com port, go to the Low Level tab, and click Begin Comm. Hopefully, you'll see 00 02 51 53 00 02 00 02. The program sends 00 02 51 53, and the remote should send back 00 02 00 02. If it does send back 00 02 00 02, then click Get Info, and Get SigBlk, copy the text and post it here. If there is no reception from the remote or some other set of bytes, click End Comm while watching the remotes LED. It should blink twice. Let us know what you see.
Let's go under the assumption that it is a JP1.4, JP1.4N, JP2, or JP3 remote. We have a tool called JP2Sniffer that allows you to better control the sequence of events compared to RMIR.
Plug in your cable, start JP2Sniffer, tell it which Com port, go to the Low Level tab, and click Begin Comm. Hopefully, you'll see 00 02 51 53 00 02 00 02. The program sends 00 02 51 53, and the remote should send back 00 02 00 02. If it does send back 00 02 00 02, then click Get Info, and Get SigBlk, copy the text and post it here. If there is no reception from the remote or some other set of bytes, click End Comm while watching the remotes LED. It should blink twice. Let us know what you see.
Maybe I should have started from the beginning with this.
Sadly I do not see anything. I JP2sniffer I only get 00 and time-out. And no LED's flash on the remote. No LED's are flashing on the USB port of the interface either.
I measured the voltage between remote pins (without anything connected) and it seems that between pin 1 and 2, 3, 4 and there seem to bi a 3.8-3.9 voltage difference.
Sadly I do not see anything. I JP2sniffer I only get 00 and time-out. And no LED's flash on the remote. No LED's are flashing on the USB port of the interface either.
I measured the voltage between remote pins (without anything connected) and it seems that between pin 1 and 2, 3, 4 and there seem to bi a 3.8-3.9 voltage difference.
No LEDs on the interface means the program isn't communicating with the interface. Verify you're running the latest driver, and confirm you're selecting the correct comm port. The port can change when you plug in the cable.
http://www.ftdichip.com/Drivers/VCP.htm
I know you said you bought the chip partner cable, but could you post a link so we know exactly what you have?
http://www.ftdichip.com/Drivers/VCP.htm
I know you said you bought the chip partner cable, but could you post a link so we know exactly what you have?
I updated the driver to latest version. (before I was using 2.10 as recommended somewhere around the forum) Now the green LED on the USB port flashes once but I still get a time-out.
The cable I have is this one: http://www.ebay.com/itm/261101529602
I somehow feel that the pinout on this remote is different.
Did you guys know about any successful story when it comes to getting information from the manufacturer (One Fol All in my case)?
PS: Redid the loopback test and it works.
The cable I have is this one: http://www.ebay.com/itm/261101529602
I somehow feel that the pinout on this remote is different.
Did you guys know about any successful story when it comes to getting information from the manufacturer (One Fol All in my case)?
PS: Redid the loopback test and it works.
I very much doubt that OneForAll wants to describe how you can hack their remotes.
Anyway, perhaps the remote actually is a JP1.3. If so, try following the instructions here for low level communications with a JP1.3
Anyway, perhaps the remote actually is a JP1.3. If so, try following the instructions here for low level communications with a JP1.3
A signature blink back wouldn't hurt either.
3FG, the remote doesn't stay in serial mode. With or without Set/Clear Break, it comes back to normal state after 2-3 seconds (in that moment, the receive LED blinks once). I also noticed that while I am pushing the remote's buttons, in normal mode, I get some repeated character on the terminal prompt.
mdavej, the signature blink back is 502604 (didn't count the last blink as it remains solid). After the 6th digit, the LED turns off.
mdavej, the signature blink back is 502604 (didn't count the last blink as it remains solid). After the 6th digit, the LED turns off.
-
The Robman
- Site Owner
- Posts: 22028
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Hey Daves (3FG and mdavej), if Loft is willing to send it to one of you, are either of you up for seeing if you can hack it in person?
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!