Hi guys,
I don't know if someone here have any copy of DM500HD remote control firmware, but if yes please post it here or contact me. I can instruct you how to read the firmware of your remote control via JP1 interface using RMIR software and an USB-serial converter.
Thanks !
Hello !
I have installed this image on my original DM500HD left aside for years and it works like a charm. The problem I'm facing now is that I'm using a remote control which is not genuine , I bought it in AliExpress, and it was supposed to work with dm800HD,dm800SE and DM500HD, but it is behaving strangely. The remote itself sends the IR signals (I tested with my phone camera), but some times it works and some times not. I'm not sure if this an image problem or something with remote control which I'll try later to flash with RemoteMaster using JP1 interface and usb-to-serial interface. Please let me know if someone is having the same issue. Thanks !
Update: Today I run a test following the steps below and it looks that remote control is ok, but maybe something is wrong with keymap.xml or something else.
Below are listed the steps and the log.
1. opkg install evtest #installed evtest binary
2. init 4 #stopped running enigma2
3. evtest /dev/input/event0
I pressed on my remote control few buttons menu, ok, etc and it looks that remote control is sending the correct keys as shown below.
Please help to resolve this strange issue.
Thanks !
######## pressing keys log of evtest #####################
Testing ... (interrupt to exit)
Event: time 1779559713.423212, type 1 (EV_KEY), code 139 (KEY_MENU), value 1
Event: time 1779559713.423216, -------------- SYN_REPORT ------------
Event: time 1779559713.593904, type 1 (EV_KEY), code 139 (KEY_MENU), value 0
Event: time 1779559713.593907, -------------- SYN_REPORT ------------
Event: time 1779559722.568526, type 1 (EV_KEY), code 174 (KEY_EXIT), value 1
Event: time 1779559722.568530, -------------- SYN_REPORT ------------
Event: time 1779559722.859765, type 1 (EV_KEY), code 174 (KEY_EXIT), value 0
Event: time 1779559722.859769, -------------- SYN_REPORT ------------
Event: time 1779559733.837710, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1779559733.837713, -------------- SYN_REPORT ------------
Event: time 1779559734.008386, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1779559734.008390, -------------- SYN_REPORT ------------
Event: time 1779559739.946840, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1779559739.946844, -------------- SYN_REPORT ------------
Event: time 1779559740.117571, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1779559740.117574, -------------- SYN_REPORT ------------
Event: time 1779559743.274775, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1779559743.274779, -------------- SYN_REPORT ------------
Event: time 1779559743.445496, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1779559743.445500, -------------- SYN_REPORT ------------
Event: time 1779559748.706972, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1779559748.706976, -------------- SYN_REPORT ------------
Event: time 1779559748.877662, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1779559748.877665, -------------- SYN_REPORT ------------
Event: time 1779559777.949114, type 1 (EV_KEY), code 352 (KEY_OK), value 1
Event: time 1779559777.949118, -------------- SYN_REPORT ------------
Event: time 1779559778.119788, type 1 (EV_KEY), code 352 (KEY_OK), value 0
Event: time 1779559778.119791, -------------- SYN_REPORT ------------
Event: time 1779559782.097891, type 1 (EV_KEY), code 401 (KEY_BLUE), value 1
Event: time 1779559782.097895, -------------- SYN_REPORT ------------
Event: time 1779559782.268561, type 1 (EV_KEY), code 401 (KEY_BLUE), value 0
Event: time 1779559782.268565, -------------- SYN_REPORT ------------
Event: time 1779559784.567536, type 1 (EV_KEY), code 400 (KEY_YELLOW), value 1
Event: time 1779559784.567541, -------------- SYN_REPORT ------------
Event: time 1779559784.716913, type 1 (EV_KEY), code 400 (KEY_YELLOW), value 0
Event: time 1779559784.716917, -------------- SYN_REPORT ------------
Event: time 1779559789.301647, type 1 (EV_KEY), code 399 (KEY_GREEN), value 1
Event: time 1779559789.301651, -------------- SYN_REPORT ------------
Event: time 1779559789.472315, type 1 (EV_KEY), code 399 (KEY_GREEN), value 0
Event: time 1779559789.472319, -------------- SYN_REPORT ------------
Event: time 1779559791.460748, type 1 (EV_KEY), code 398 (KEY_RED), value 1
Event: time 1779559791.460752, -------------- SYN_REPORT ------------
Event: time 1779559791.631411, type 1 (EV_KEY), code 398 (KEY_RED), value 0
Event: time 1779559791.631414, -------------- SYN_REPORT ------------
Hi guys,
I have read this thread since the beginning and I'm not still clear on that.
My question is simple: having up and running patched oscam-icam, copied bouquets, and configuring the settings,is that enough if I get sly card and use it in my server and clear my channels in my box?
As far as I understand, that's not enough. You should have also the pairing keys for which no one is giving info on how to extract and how configure in oscam.server file. If this issue of keys is true then the only other way is to get the ecm-s from your pairs hoping that any of them is able to resolve the keys issue. Please correct me if I'm wrong in this statement. If there is no a clear way how to get those keys the rest is losing time.
I have read many post of users claiming to have completed successfully all the steps in this thread , but not clearing any channel, simply because, I think this is only staying at the top of the iceberg ... 
