Support and General Use > Hardware

H120 remote control

<< < (7/8) > >>

bluebrother:

--- Quote from: bonapardo on July 20, 2011, 11:39:05 AM ---I just unprogrammed the CKDIV8 fuse and now I get the LED lighting up whenever I press a button.  So I know the chip is fine and I'm flashing it correctly.  Nice.  However, the LED remains on and I have to press again to turn it off (rather than turning off when I release).  All buttons have the same effect and can disable the LED if lit up by another button.
--- End quote ---

That is correct -- the LED is toggled on the toggle bit of the remote, and that is not only enabled if a button is pressed ;-) I was thinking about changing that behaviour but still haven't done that. Having the LED react on the toggle bit was useful to see if a new button has been pressed or a button is held down :)

I've documented the fuse values in the repository. For programming I've used the following line (you might need to adjust the programmer if you're using avrdude):

--- Code: ---avrdude -p t2313 -c dragon_isp -P usb: -U lfuse:w:0xe4:m -U hfuse:w:0xdb:m -U efuse:w:0xff:m
--- End code ---


--- Quote ---(also, as I'm in a position to test the circuit and program, please let me know if you'd prefer my enquiries to go through the project page from now on)
--- End quote ---

I don't care much about the platform used. Feel free to keep this thread going, and if you prefer messaging me at github you can do that as well. It's really nice to see someone is still interested in this (gives some motivation to look into the other ideas I had, like making the receiver programmable) :)

bonapardo:
It works!

I had touching resistors in the network.  The play button currently does not respond, but I am getting vol up, down, fwd and rew.  I suspected a simple RC5 problem but somehow I managed to pause playback after repeated pressing.  I've not been able to reproduce that again but I'll look at the circuit tomorrow - it's all very breadboardy, no soldering just yet.

Once I get the play button working, it'll be time for me to try the LCD version.  Yikes.


Post Merge: July 20, 2011, 06:55:01 PMOh, and I programmed the additional fuse bit BODLEVEL1 as per your avrdude command which may well have had an effect.

bonapardo:
Haven't had a chance to look at my Play button yet, will do this weekend.  I have another quick question in the meantime though...

Do you have an RC5 mapping of the Hauppauge remote?  Just wondering how you got those decimal values I can see in the code.  Did you use a particular type of 'learning' software? 

For the LCD remote, I'll have to program additional buttons and I may duplicate some of the buttons so the navigation buttons of the HP remote can also be used.  One thing I want to do is make the HP Play = iRiver Navi and set an alternative for iRiver Play (it has always been a mild frustration of mine that Play actually just returns to the WPS screen rather than playing the selected track in browser).


Thanks!

bluebrother:

--- Quote from: bonapardo on July 22, 2011, 06:41:38 AM ---Do you have an RC5 mapping of the Hauppauge remote?  Just wondering how you got those decimal values I can see in the code.  Did you use a particular type of 'learning' software?
--- End quote ---

I used a similar setup I built up a couple of years ago (basically using the same code, but without the "create correct output for H100" part) that did output the value via UART. You could implement that of course, but the UART uses Vcc levels, i.e. 3.3V so you need level shifters for connecting it to a PC. The codes are kinda standardized, just google the web :) Anyway, I've written down the codes:


--- Code: ---Device Address: 0


| Button    | Code (dec) |
|===========|=========== |
| TV        |  15        |
| Radio     |  12        |
| Mute      |  13        |
| Source    |  34        |
| Ch+       |  32        |
| Ch-       |  33        |
| Vol+      |  17        |
| Vol-      |  16        |
| 1         |   1        |
| 2         |   2        |
| 3         |   3        |
| 4         |   4        |
| 5         |   5        |
| 6         |   6        |
| 7         |   7        |
| 8         |   8        |
| 9         |   9        |
| 0         |   0        |
| Reserved  |  30        |
| Minimize  |  38        |

--- End code ---


--- Quote ---For the LCD remote, I'll have to program additional buttons and I may duplicate some of the buttons so the navigation buttons of the HP remote can also be used.
--- End quote ---

What are you referring to by HP? Hauppauge?

bonapardo:
Thanks for the list, I managed to pick up some generic codes from Wikipedia (http://en.wikipedia.org/wiki/RC-5#Command_Tables). Since my last post, I bit the bullet and put together the LCD version, realising I don't even need the play button if I have Navi (rc5 code 53 didn't work either). The resistor values on the iRiver hardware page work fine. I'm about to reprogram the buttons as they are in a different order to the non-LCD version.

I've had a bit of trouble with Navi. I'm using PD6 but it seems to think I'm either pressing it repeatedly or holding it down. Tried to replicate the play button code as it's a PD pin but no luck. Will give it another go today.
Post Merge: July 24, 2011, 10:34:24 AMNavi button is enabled in addition to FWD, REW and Stop, meaning I have four way navigation of the menus and the ability to browse and play while a track is playing.  Basically, this is all I need, my project is complete!

I'll tidy up my changes and submit code and schematic to the gitHub page this week.  I still haven't got Play working but that could be due to an alternative transistor I'm using.  I'll post details on that once I'm over my current excitement!

Thanks again for all your help, I've learned a lot.




Post Merge: July 24, 2011, 03:58:30 PMThis was the alternative transistor I used: BC548B.  Not sure if that could be my problem...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version