| View previous topic :: View next topic |
| Author |
Message |
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
 Posted: Sat Jun 12, 2004 3:02 pm Post subject: |
 |
|
| Mark Pierson wrote: |
| mr_d_p_gumby wrote: | | 32.5 mS would be 3F 7A |
No change with this. If anything, the rapid-fire might be just a tad faster, though it's hard to tell. |
But you don't get 32.5 ms just by changing those two bytes.
There is another bit (I forget where and don't have PB on THIS computer) that tells whether roughly 65 ms is added to the value specified by those bytes. The upgrade had that bit set to get the original lead out. You need to clear that bit as well as changing those two bytes. |
|
| Back to top |
|
 |
jon_armstrong
Expert
Joined: 03 Aug 2003
Posts: 1238
Location: R.I.P. 3/25/2005
|
| Posted: Sat Jun 12, 2004 3:18 pm Post subject: |
|
|
You can also set only Ch+/-, Vol+/-, FF, and Rew to repeat (since Temp is on Ch+/-):
Upgrade Protocol 0 = 01 C9 (S3C8+) Kaseikyo (KM v8.22)
46 90 51 8B 12 87 45 08 08 00 D7 00 B5 00 D7 02
6A 88 B8 06 AA 03 41 08 08 E4 07 08 09 07 F0 C0
B4 07 C0 56 C0 0F B4 C0 08 8D 01 46
End
Change to 46
_________________
-Jon |
|
| Back to top |
|
|
Mark Pierson
Expert
Joined: 03 Aug 2003
Posts: 3017
Location: Connecticut, USA
|
| Posted: Sun Jun 13, 2004 8:06 am Post subject: |
|
|
| jon_armstrong wrote: | You can also set only Ch+/-, Vol+/-, FF, and Rew to repeat (since Temp is on Ch+/-):
...
Change to 46 |
That's a workable compromise for now, even though the repeats are still rapid-fire.
Rob's offered to learn the signals on his Pronto, so I may just take him up on that offer. I'll probably wait until I install the 2nd unit, which will be a while since a family of Finches has taken up residence under the old A/C unit! 
_________________
Mark |
|
| Back to top |
|
|
jon_armstrong
Expert
Joined: 03 Aug 2003
Posts: 1238
Location: R.I.P. 3/25/2005
|
| Posted: Sun Jun 13, 2004 8:26 am Post subject: |
|
|
How about the maximum interval (131,072 uS) plus repeat only for c+/- etc:
Upgrade Protocol 0 = 01 C9 (S3C8+) Kaseikyo (KM v8.22)
46 90 51 8B 12 87 46 08 08 00 D7 00 B5 00 D7 02
6A FF FF 06 AA 03 41 08 08 E4 07 08 09 07 F0 C0
B4 07 C0 56 C0 0F B4 C0 08 8D 01 46
End
_________________
-Jon |
|
| Back to top |
|
|
Mark Pierson
Expert
Joined: 03 Aug 2003
Posts: 3017
Location: Connecticut, USA
|
| Posted: Sun Jun 13, 2004 9:05 am Post subject: |
|
|
| jon_armstrong wrote: | | How about the maximum interval (131,072 uS) plus repeat only for c+/- etc |
That's marginally better. I still get the rapid-fire, but not as many or as quickly. I also tried it with standard repeat (using $45) to test the other buttons.
This seems like an awful lot of work for a simple air conditioner. But I suppose in the pursuit of JP1 perfection, it's a worthwhile endeavor! 8)
_________________
Mark |
|
| Back to top |
|
|
mr_d_p_gumby
Expert
Joined: 03 Aug 2003
Posts: 1370
Location: Newbury Park, CA
|
| Posted: Sun Jun 13, 2004 12:00 pm Post subject: |
|
|
| johnsfine wrote: | | There is another bit (I forget where and don't have PB on THIS computer) that tells whether roughly 65 ms is added to the value specified by those bytes. The upgrade had that bit set to get the original lead out. You need to clear that bit as well as changing those two bytes. |
The protocol only loads the first two flag bytes, and I don't see a bit in either byte that would alter the leadout off time, other than the off-as-total bit, which is not set. If you are referring to pf2 bit 6, it's not being set here. When you get a chance, could you tell me which bit you are talking about so I can confirm that PB takes it into account?
_________________
Mike England |
|
| Back to top |
|
|
johnsfine
Site Admin
Joined: 10 Aug 2003
Posts: 4766
Location: Bedford, MA
|
| Posted: Sun Jun 13, 2004 2:55 pm Post subject: |
|
|
| mr_d_p_gumby wrote: | | The protocol only loads the first two flag bytes, and I don't see a bit in either byte that would alter the leadout off time, other than the off-as-total bit, which is not set. If you are referring to pf2 bit 6, it's not being set here. When you get a chance, could you tell me which bit you are talking about so I can confirm that PB takes it into account? |
I was misremembering the boundary by a factor of 2. It is the bit for times greater than around 130ms, not for greater than 65ms. So it wasn't set in this upgrade. I think you're right that it's pf2.6 |
|
| Back to top |
|
|
jon_armstrong
Expert
Joined: 03 Aug 2003
Posts: 1238
Location: R.I.P. 3/25/2005
|
| Posted: Sun Jun 13, 2004 3:36 pm Post subject: |
|
|
Does PB support Off times greater than ~132 mS? When I was experimenting earlier the field turns red when it is exceeded and it looks like it adds one or two bytes near the beginning. I assumed something "overflowed" and that the red was indicating a max had been exceeded.
_________________
-Jon |
|
| Back to top |
|
|
mr_d_p_gumby
Expert
Joined: 03 Aug 2003
Posts: 1370
Location: Newbury Park, CA
|
| Posted: Sun Jun 13, 2004 4:19 pm Post subject: |
|
|
Yes, the red indicates that the value is overflowing one or more bytes in the protocol. The actual value where this occurs varies from one remote type to another. I'm not certain if the current PB version supports the extra leadout bit that John was talking about, but I will look into supporting it in a future version. In the meantime, you'd have to add code manually to extend the off time.
_________________
Mike England |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
File Section
Wiki
