This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 Remote Control

The remote control I got with my DM365 EVM does not match any of the diagrams used in the getting started guides.

I've entered "0220" and "0020" but only get partial key functionality. For example, the PLAY button works sometimes but the UP/DOWN keys don't and the STOP button doesn't stop.

Any suggestions? What DVD model is being used in the demos?

  • The 0020 code should work with DVD mode on the remote, though sometimes the demo can be sluggish to respond, if the buttons do not appear to be working try pressing the button in question multiple times in succession, I have found that the record button in particular for the encode demo seems to work more reliably by pressing it twice. What does your remote look like? The one I am using looks just like the picture on the wiki here.

    Hank Magnuski said:
    What DVD model is being used in the demos?

    There is not a particular DVD model that was used, the 0020 code just happens to be the default on these particular remotes which was programmed into the EVM firmware, in theory you could change the codes it looks for by modifying the MSP430 firmware which manages the IR sensor.

  • The documentation says it's a Philips SRU3004/27 and it looks like this:

  • That is interesting, they must have started shipping a new revision of the remote control, I have not come across one that looks quite like that yet, but I suspect it is just a new revision of the remote and uses the same codes, I would be suprised if it does not (it is meant to be universal after all). I suspect what you are seeing is just the general flakyness of the remote control aspect of the demos. I have had differing levels of success depending on what sort of room the board is setup in and such, in general I have been able to get the commands to work eventually by trying repeatedly (though sometimes I have given up and restarted ./interface which seemed to help), I suspect the IR sensor is seceptable to IR noise in the room.

  • I believe there is an error/mismatch in the DMAI function that reads the IR value (getIrVal in dmai/linux/dm365/Ir.c). The LOW byte should be read before the HIGH byte. The MSP430 code advances it's internal buffer pointer after the high byte is read, so if you read this byte first you can sometimes get invalid codes returned (but sometimes it works). If you fix the function in Ir.c, you should see better performance from the remote.

  • Thanks for the code update, I think that helped. I'm using program code "0020".

    I'm able to get most, but not all of the keys to work now, more or less. The CH+ and CH- keys map into Scroll Up and Scroll Down, The Volume +/- will select entries in the list. The Play, REC and Stop buttons appear to work correctly. Buttons that work are working well and consistently.

    But the OK button and buttons around it do nothing, the Info/Select does nothing and the Pause does nothing.

    At least I was able to make a recording using the demo interface, so that's progress.

  • Hi everyone,

    I got the DM365EVM this month, and I got the same problem as Hank met. The IR remote controller is the same one as Hank's post photo. Only the Play, Stop, Pause key work for the demos program. I want to change the IR mapping code to my own remote controller, but I am all confused for the entire program structure and flowchart. I found some related source code such as ir.c, ir-keymaps.c, input.h, _event.h, but which one is the correct one for the DM365EVM demos? And where is the customer code define? How to add my own remote controller key maps?

    Willy