JP1 Remotes

JohnParks · Joined: 05 Jan 2004 Posts: 60

Why does ir refuse to open a file i just saved... cause i don't have a backup? Was working fine.

The Robman · Posted: Wed Jan 07, 2004 10:04 pm Post subject:

Define "refuse". If you think there might be a problem with the file, post it in the Diagnosis Area and one of us will look at it.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

JohnParks · Joined: 05 Jan 2004 Posts: 60

How do i get there??

JohnParks · Joined: 05 Jan 2004 Posts: 60

OK - found the site, the files name is JP's8811 Remote.txt. When I try to open it ir complains "Can't open file..."

usblipitor · Joined: 10 Oct 2003 Posts: 516 Location: Greenbelt, MD

I just opened your file in IR.exe so it is not the file that is the problem.

Maybe you should reboot your computer and try to open the file again?

How are you attempting to open the file?

The correct way is to use the File/Open from the drop down menu in IR.

-Steve

JohnParks · Joined: 05 Jan 2004 Posts: 60

Thanks Steve, that's how I've been loading it. This jp1 thing is the worst experience I have ever had with technology. First the interface wouldn't work. Just before I was ready to kick the system unit across the room I took the batteries out of the 8811... guess what? Then ir started complaining that it couldn't find a system file decon.sys. So then I threw everything out and started all over and now this. Are ir gods trying to tell me something??? If my post seem a little "short" you know why.

JohnParks · Joined: 05 Jan 2004 Posts: 60

Well after a 3x's longer then normal boot the file load, but ir is not happy... Warning - Bad checkskum at $0000. Expected $20 $DF, but found $DC $23. Now how the hell does it know what to expect? I don't... it sounds like its getting smarter than i am!

I'm going to bed or blow my brains out... I'm not sure which would be more relaxing.

usblipitor · Joined: 10 Oct 2003 Posts: 516 Location: Greenbelt, MD

do a 981 reset on the remote to completely wipe the eeprom so you can start with a clean slate. (hold set button till 2 blinks, then 9-8-1)

Start IR.exe and do File/New/Select and pick:
URC-881x_801x_601x(6_806_80)
from the list of rdf files.

now connect your newly wiped remote to the jp1 cable and click "download from remote"

now click "file/save as" and call it "IR_Virgin_8811.txt"

now disconnect the remote and exit IR.exe.

now restart IR.exe and click file/open and open that file and let us know if it works or if you still get the checksum error.

Good Luck,
-Steve

The Robman · Posted: Thu Jan 08, 2004 8:13 am Post subject:

JohnParks · Joined: 05 Jan 2004 Posts: 60

J-O-H-N-N-Yeeee's back. After a nights sleep I'm starting to feel like the world is round again. I would like to thank Rob, Steve, and everyone else for putting up with my newbie incompetence... hope to be able to pay back.

Some questions please:
1. What is the structure of a remote program-wise? From posts, I assume that there is rom, ram, and eprom, but it's not running like a computer is it... in a loop waiting for a key press? I ask this because removing the batteries from my urc-8811 cured all my ir interface problems. It's dormant until a key press, right?

2. What's in rom. I know generally know what's in a computer's flash rom. Is it run every time a key is pressed and then jumps to ram/eprom or just data for factory resets, product_id, etc.

Answers or an info pointer would greatly appreciated.

johnsfine · Posted: Thu Jan 08, 2004 12:32 pm Post subject:

It has ROM, RAM, registers (more than you'd expect), and eeprom.

Data can be accessed easily in registers, with more difficulty in RAM or ROM, and with much more difficulty in EEPROM. Code can be executed easily in ROM or RAM and not at all in registers or eeprom. Those constraints lead to a fair amount of copying things around prior to use:

Several models have two different memory use patterns depending on whether the eeprom is present:

No eeprom:
1) Basic setup data kept in registers.
2) KeyMoves and Macros kept in RAM and copied into registers for use.
3) Built-in setup codes used directly from ROM
4) Learned signals and upgrades not supported.

With eeprom:
1) Basic setup data kept in registers, but backed up in eeprom.
2) KeyMoves and Macros kept in eeprom and copied into registers for use.
3) Built-in setup codes used directly from ROM
4) Learned signals and upgrades kept in eeprom and copied to RAM for use.

The MPU is in a loop waiting for (and processing) keystrokes, but there is an interrupt system so that the loop is really waiting for the flag set by the keyboard interrupt service routine rather than for the keyboard itself. There is also an instruction to pause the MPU in a lower power mode waiting for the next keyboard, timer, or other interrupt, and there is a way to pause it in an even lower power hibernate mode waiting for only keyboard interrupts. That mode is so low power that it maintains its CPU state, registers, and RAM sometimes for several hours without batteries.

JohnParks · Joined: 05 Jan 2004 Posts: 60

Thanks John. What happens data-wise when the batteries go south? Is it able to recover without data loss?[/b]

The Robman · Posted: Thu Jan 08, 2004 2:05 pm Post subject:

JohnParks · Joined: 05 Jan 2004 Posts: 60

I loaded Remote Master and must admit, the interface is much more intuitive, but I will always be amazed at what Rob Crowe and others were able to do with a spreadsheet... incredible.

With the explanations rendered here things are beginning to make a lot more sense. Now all I have to do is decide if I want to do an extender on my URC-6131. Thanks all.

johnsfine · Posted: Thu Jan 08, 2004 3:34 pm Post subject: