damn, I was hoping there was a pre-programmed device ID that the remote was set to. Thanks for the great info though. having the raw codes is useful. I’ll have to see if I can run them through my Android phone to program my remote with the original codes since it has an IR transmitter.
Thanks!
Thanks marqs. Do you know if there is a way to reprogram it without another working remote? My friend lives out of state and it might be a few months until I have the opportunity to use his remote to reprogram mine. I’ll have have to ask around and see if I can find another local OSSC owner.
If you hold BTN1 while booting the OSSC, and it asks you to press a button on the remote, and it doesn’t work
That’s exactly what I’ve tried and it doesn’t work.
then either your remote is at fault or the OSSC IR sensor is.
As I said in the first post. I had a friend visit with his OSSC remote and it was able to work on my OSSC, so we’ve confirmed that the OSSC IR Sesnsor is good.
Hence why I created this thread asking how I can properly re-program the remote.
the very first step: “To configure the OSSC for a new infrared remote, find a suitable manufacturer code (e.g. from Toshiba, NEC etc.) so that the OSSC’s green LED blinks when a remote button is pressed”
As I said in my first post: this isn’t happening with my remote. I guess I’m trying to figure out how to set the remote to a “suitable manufacturer code”.
I did find some generic instructions for the chunghop l336 s but trying to use NEC and Toshiba codes listed in those instructions didn’t have any effect.
I did see that page before in my searching, but that seems to be instructions on how to reprogram the OSSC to accept a different remote, not to how program the remote with the default OSSC codes, unless I’m miss-reading it?
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
__gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
wordpress_apbct_antibot | session | No description |
wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |