JP1 Remotes

gfb107 · Expert Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC

OK, so the Fujitsu executor is a combo (it supports any sub-device for any command), and the sub-device should be a command parameter, not a protocol parameter.

gfb107 · Expert Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC

The next question is whether or not we want to expose X as a protocol parameter. If we do it now we have the flexibilty to simply set it in a device upgrade without having to make changes to protocols.ini to enable that. OF course we can use a default value so that we don't require that users specify a value for it.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

vickyg2003 · Posted: Fri Aug 20, 2010 7:13 pm Post subject:

gfb107 · Expert Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC

OK, the first thing to figure out is if the variant built into the 7800 is actually one of the 3 variants already defined in protocols.ini. My guess is that it is variant 1, but I don't know how to find out if that is indeed the case.

This is further complicated by the fact that the Fujitsu executor is also the Sharp DVD executor, and we must use the same variant names for both, so the correct variant of both can be identified with a single entry in the Protocols section of RDFs.

Assuming for the moment that it is variant 1, we need to

Update protocols.ini to remove the variantName=1 for consistency with SharpDVD and
Change the default FixedData for this variant so the first byte is 00

The Robman · Posted: Mon Aug 23, 2010 12:21 pm Post subject:

gfb107 · Expert Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC

OK. Given that the 00F8 executor in the URC-7800 is already known as the "base" variant (all that means is it has no variantName) for Sharp DVD, we need to also use no variant name in the Fujitsu context. Based on Vicky's input we should change the default FixedData so the first byte is 0.

The revised protocols.ini entry is

gfb107 · Expert Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC

Vicky,

Have you had a chance to try this?
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

vickyg2003 · Posted: Tue Aug 24, 2010 6:31 am Post subject:

No I hadn't tried it, but I'll do that today.

Question though, there is a

Does this replace the stuff that is in there for fujitsu where it currently says
VariantName=1

I know that the RDF's say 00f8, 00f8:2 and 00f8:3, so since there is no colon in the 7800 00F8 this would then be a "variant 1", but since the :1 isn't there the variantName should not have been there?

Its making more sense to me this morning.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

vickyg2003 · Posted: Tue Aug 24, 2010 7:07 am Post subject:

Very nice work Greg,

Tried the fujitsu on the 7800.

The upgrade worked as advertised. No upgrade required, signals sent decode properly.

If there is more that you want me to test, just say so.

Working through this has helped me with my understanding of protocols.ini.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

gfb107 · Expert Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC

The Robman · Posted: Mon Sep 13, 2010 11:45 am Post subject:

Did we come up with an upgrade file that digital_silence can test?
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

vickyg2003 · Posted: Mon Sep 13, 2010 12:00 pm Post subject:

There were plenty of fujitsu upgrades in the file area, that all used the same obc's, it was just that the fixed data was bad. They should all work now from RM, including the one that I uploaded.

Mike is aware of the change needed for KM, and I believe he was working on that for the 9.21
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

The Robman · Posted: Mon Sep 13, 2010 1:07 pm Post subject:

digital_silence, can we close this one out? Did you get your upgrade to work?
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

digital_silence · Joined: 22 May 2004 Posts: 257

vickyg2003 · Posted: Wed Sep 15, 2010 8:46 am Post subject:

Oh boy, I've gone through so many changes of RM versions since this post that I don't remember where RM Fixed this in protocol.

If when you choose Fujitsu off the menu, you only protocol parameter you see is Main Device, (no subdevice setting on the main page), then you've got a version of RM that correctly handles the Fujitsu protocol.

You should be able to open the Fujitsu TV upgrades in RM and they should work

The key is that the fixed data needs to be in the correct order, and it wasn't.

the screen should say

Main Device 132
Fixed Data 03 D7 39 FF DE
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.