Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 2 days, 21 hrs ago - more...
 |
Copernicus |
2012-09-26
, 20:48
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#741
|
Originally Posted by davdav
I will try to work some more on the air conditioners.
But they really are hard to manage -- not even the experts at the hifi-remote website have found a good way to cram stateful A/C controls into a JP1 remote control...
|
|
2012-09-26
, 20:59
|
|
Posts: 282 |
Thanked: 220 times |
Joined on Aug 2011
|
#742
|
Maybe at least basic functions ?
?
|
|
2012-09-26
, 23:54
|
|
Posts: 840 |
Thanked: 823 times |
Joined on Nov 2009
|
#743
|
Originally Posted by Copernicus
I have no background of IR spec but I've noticed that some of my remotes I can never get working on ANY other infra-red remote.
It is also true that many manufacturers set up their devices to be extremely tolerant of off-spec IR signals. (After all, most remote controls are constructed very cheaply.) I'm always amazed looking at the LIRC config files; some of the timings in them are off by more than 20 or 30 percent, and yet they still work fine. I have a sneaking suspicion that the problem with Sony devices is that Sony builds their equipment so well, they don't have to be tolerant of off-spec timing. And, therefore, they are unhappy with some aspect of my protocols that other devices just don't care about.
(Which reminds me; maybe an additional column for the controlled device's make and model would be useful.)
What I mean by that is I can never get any other universal remote or LIRC (on a PC) to learn commands from these 2 remotes I have.
The remote was for a DiSEqC (USALS) satellite receiver (made by echostar), I bought several universal remotes to to try and "teach" them from this remote and they would always fail to do so. This forced me to get another DiSEqC satellite receiver made by another company (don't remember the name but it wasn't echostar) and oddly they couldn't learn from it either. All other remotes worked except these. Is there some special protocol for DiSEqC receivers which make them incompatible with universal remotes and LIRC?
Last edited by Cue; 2012-09-27 at 01:42.
| The Following User Says Thank You to Cue For This Useful Post: | ||
|
|
2012-09-27
, 01:34
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#744
|
Originally Posted by davdav
The problem is that most A/C remotes now work in this "stateful" mode; in short, the remote itself remembers your settings for temperature, fan speed, oscillation, etc.; and each time you press any one of the buttons, it sends ALL of the settings over to the air conditioner. So even the basic functions end up being not so basic.
Maybe at least basic functions
(I mean, even to send a power on / power off command, you've gotta send a valid signal with temperature / fan / oscillation data, and there's usually a checksum or two mixed in to force you to get all the numbers correct...) In short, these guys practically require writing a whole new code path just for themselves. 
I do intend to get it done eventually!
| The Following 4 Users Say Thank You to Copernicus For This Useful Post: | ||
|
|
2012-09-27
, 01:56
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#745
|
Originally Posted by Cue
There are indeed a number of IR protocols out there that most universal remotes just can't handle. The "stateful" A/C remotes I've been talking about earlier are one type -- they require the remote to keep track of a handful of variables, and most universal remotes just can't do that. LIRC isn't set up to remember state information either, although I suppose you could probably hack it to work...
I have no background of IR spec but I've noticed that some of my remotes I can never get working on ANY other infra-red remote.
What I mean by that is I can never get any other universal remote or LIRC (on a PC) to learn commands from these 2 remotes I have.
The remote was for a DiSEqC (USALS) satellite receiver (made by echostar), I bought several universal remotes to to try and "teach" them from this remote and they would always fail to do so. This forced me to get another DiSEqC satellite receiver made by another company (don't remember the name but it wasn't echostar) and oddly they couldn't learn from it either. All other remotes worked except these. Is there some special protocol for DiSEqC receivers which make them incompatible with universal remotes, LIRC?
Bang & Olufsen uses a ridiculous carrier frequency (455 khz, as opposed to the 36-38 khz used by most manufacturers), so that's another way to defeat the universal remotes.
A lot of the trickier recent protocols, such as those used for IR keyboards, keep very close track of the exact time of each pulse to squeeze in more data; so that, say, a 400 usec pulse is a 0, 500 usec is a 1, 600 usec is a 2, and 700 usec is a 3. This system passes two bits of data in roughly the same time used to pass a single bit in ordinary protocols. You can, of course, extend this system to pass as many bits as you like. And yeah, many universal remotes can't easily handle this type of protocol yet either. (LIRC has no trouble with this, though.)
I don't know what protocol the Echostar receiver is using. Most Echostar devices that I know of are using protocols that a learning remote would be able to recognize; but then, most Echostar devices that I know of are Dish Network units.
| The Following 4 Users Say Thank You to Copernicus For This Useful Post: | ||
|
|
2012-09-27
, 20:03
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#746
|
Here's a question for Pierogi users: I've been working on different ways to control the Pierogi UI via the keyboard, and have only just now noticed that Qt already allows you to switch between tabs by using the right and left arrow keys on the keyboard. So, (a) does anyone out there already use this feature, and (b) should this feature be maintained, or allowed to be overridden by other commands? (I was thinking of associating the arrow keys with the arrows in the menu tab, or with the channel/volume buttons of the main tab...) Thanks!
So, (a) does anyone out there already use this feature, and (b) should this feature be maintained, or allowed to be overridden by other commands? (I was thinking of associating the arrow keys with the arrows in the menu tab, or with the channel/volume buttons of the main tab...) Thanks!
| The Following 2 Users Say Thank You to Copernicus For This Useful Post: | ||
|
|
2012-09-27
, 20:57
|
|
Posts: 2,290 |
Thanked: 4,134 times |
Joined on Apr 2010
@ UK
|
#747
|
Originally Posted by Copernicus
No I don't use this due to not being able to select Favourites or Panels.
should this feature be maintained, or allowed to be overridden by other commands? (I was thinking of associating the arrow keys with the arrows in the menu tab, or with the channel/volume buttons of the main tab...) Thanks!
IMO Channel/Volume Buttons from the main tab, unless there's a better idea.
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
| The Following 3 Users Say Thank You to sixwheeledbeast For This Useful Post: | ||
|
|
2012-09-27
, 21:01
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#748
|
Originally Posted by sixwheeledbeast
Well, I could add the ability to select favorites and panels as well; say, up/down for panel collections, backspace/enter for favorites?
No I don't use this due to not being able to select Favourites or Panels.
(Actually, I suppose I could make all these options configurable, if I tried hard enough...)
| The Following 2 Users Say Thank You to Copernicus For This Useful Post: | ||
|
|
2012-09-27
, 21:24
|
|
Posts: 2,290 |
Thanked: 4,134 times |
Joined on Apr 2010
@ UK
|
#749
|
Originally Posted by Copernicus
Quicker to tap the screen IMO that's why the tab bar is there.
Well, I could add the ability to select favorites and panels as well; say, up/down for panel collections, backspace/enter for favorites?
Plus if you decided to use the QWERTY thing I mentioned, there would be no need.
You could jump striaght to the tab instead of scrolling to it
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
| The Following 3 Users Say Thank You to sixwheeledbeast For This Useful Post: | ||
|
|
2012-09-27
, 21:42
|
|
Posts: 840 |
Thanked: 823 times |
Joined on Nov 2009
|
#750
|
Originally Posted by Copernicus
I didn't know the arrow keys did this to begin with
Here's a question for Pierogi users: I've been working on different ways to control the Pierogi UI via the keyboard, and have only just now noticed that Qt already allows you to switch between tabs by using the right and left arrow keys on the keyboard.
I think mapping them to volume and channel would be great.
| The Following 3 Users Say Thank You to Cue For This Useful Post: | ||
