JP1 Remotes

[stangbat]

If this is the wrong forum for this, my apologizes.

I'm able to get my Tommy Tyler USB JP1 cable to work on Windows 7 x64 using XP Mode (Windows Virtual PC). I have an 8910. The only problem I've encountered is when downloading from the remote I get the following error:

Bad checksum at address $0000. Expected $DD $22 but found $88 $77.

I am using the extender for the 8910. After getting the error, I added a key move in IR and uploaded. After uploading I got an error that the data on the remote did not match the data in IR. However, everything seems to work just fine.

I haven't ran though every function on the remote but some quick testing shows that the added key move works, and the 8910 controls other devices as expected. Any ideas what is going on? Thanks!

[The Robman]

How are you getting IR to work with a 64-bit machine? Are you using the official IR 8.02 version of IR or the new IR 8.03 Release Candidate 2 which has been modified to work with 64-bit machines?

http://www.hifi-remote.com/forums/viewtopic.php?t=12179

When you download from the remote, does the rest of the data look OK? Maybe you should post a copy of your IR file so one of us can take a look.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[3FG]

We've put a fair amount of work into getting IR to work with 64 bit operating systems, and during that we found that the Delcom chip that is used in all the USB JP1 cables doesn't work well with some USB host controllers. The primary issue is read errors, and that seems to match your symptoms.

mathdon has recently made available IR version 8.03 Release Candidate 2, which includes support for the Microsoft-written WinUSB driver which works natively with Win7, both 32 and 64 bit versions. This driver replaces the Delcom driver. IR 8.03 in conjunction with WinUSB includes error correcting code that seems to eliminate problems with reads.

Please download

IR 8.03 RC2

The error correcting code requires the WinUSB driver.

First download and read the WinUSB installation instructions,

and then depending on whether you have a 32 bit or 64 bit OS, the driver files:
64 bit driver or the
32 bit driver

[stangbat]

[stangbat]

[The Robman]

Here's a link to your old post (Hint: you can get the link using the icon next to the post's timestamp) :
http://www.hifi-remote.com/forums/viewtopic.php?p=83999#83999

[stangbat]

Thanks Rob and Dave, I appear to be in business. I installed the WinUSB drivers and successfully interfaced and downloaded from the remote in Win7 x64 with no errors. Thanks a bunch for all the effort to get this working with 64 bit OSes.

Rob, I knew there had to be a way to link directly to posts but for the life of me I kept overlooking that little itty bitty folder icon next to the time stamp. Thanks.

[The Robman]

Yup, it's not for the visually challenged!
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[3FG]

stangbat,
Please let us know if you have OHCI or UHCI host controllers. The WinUSB installation instructions describe how to find out. It'll help us build up an understanding of what problems are fixed (or not).

Thanks

[stangbat]

Looks like mine must be OHCI. Device Manager reports "OpenHCD USB Host Controller."

[ElizabethD]

In case don't know how to find out,
Right click My Computer > Properties > Hardware > Device manager
Scroll down to and expand + on the USB jobs at the bottom.
OHCI displays in Device manager as "... OpenHCD USB Host Controller"
UHCI displays as "... Universal Host Controller"

edit - ooops, I was writing as you posted, thanks. Good info. and I forgot WinUSB tells how to find out.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride

[3FG]

Great! Yep, that's OHCI, and so the behavior you saw matches what we've seen during development.

Thanks.

[mathdon]

[stangbat]