Reply to thread

Message: [QUOTE="rmc_olderthandirt, post: 1185490, member: 68872"] I just bought a used Pacemaker III. I don't know if I got a broken unit, one that is so old that the software is funny or if Pacemakers have a serious flaw. It doesn't act like it is broken. It acts like a software bug. I used the route sheet from an actual enduro and tried to go through the steps of programming the Pacemaker. It took me a while to get things figured out and it is definately not something I would want to do in a hurry and under pressure. But I think I got everything entered okay. then I used the milage adjust to quickly run through the sequence. Things definately were not right! The Enduro that I used as a test case has four loops. At the start of each loop they have a "RESET to Zero" and a "WAIT" and a speed change. The first, third and fourth loops also have the normal resets within the loop. I found in the manual that the Pacemakers can't handle three things at one milage so I offset the reset by .05 miles, per the instructions. (Actually the instructions said 0.01 miles but I wanted to be able to see the sequence while stepping through). The sequence then is a speed change and a Wait at the actual loop end, then a "JUMP to 0.05" and a speed change (to the same speed, as the manual said a Reset MUST be followed by a speed setting) to If I programmed two loops in things worked fine. When I stepped over the normal reset the milage changed and the diffrence time adjusted accordingly. When I reached the end of the loop the difference time reflected the proper wait period. 0.05 miles later the odometer jumped to 0.05 and the clock was perfect. The rest of the loop (abuot 8 speed changes) worked just as expected. When I added the WAIT, and the JUMP for the start of the third loop everything got messed up. Not at the start of the third loop, back at the start of the second. With the second JUMP programmed into the memory the difference clock gets all messed up when I step across the first JUMP. It handled the first reset okay, and the WAIT, but going across the jump suddenly adds some random amount of time to the difference clock. I tried adjusting the clock to bring it to the proper time for being at the end of the first loop but that didn't help, it just made the difference readout smaller (but still very wrong). I have triple checked that I had the Jumps entered in both the SPEED and RESET section. I have tried clearing the entire memory and starting fresh. This is definately a Pacemaker III (not a 2), but I am guessing it is an older unit. The boot screen says "Pacemaker III" instead of "Pacemaker 3", "By A-Loop Offroad" instead of "by FHR". I have tried contacting via email but I have not been able to get a response. Does anyone have experience with this and know of a work around? Anyone want a Pacemaker III that doesn't handle Jumps to zero? Thanks Rod [/QUOTE]

Verification: Which ocean is California closest to?