Hi Rob
I haven't mentioned this earlier, but I do appreciate the feedback and time you are spending on this. I know what its like to have a product that everyone uses with no problems, except for a couple of "problem children"

One thing I noticed, in relation to a comment you mentioned about ".... the power PIC crashing". When I apply ignition, the unit boots. Pretty obvious. If I turn the ignition off, while the unit is still booting (ie the logo has come up, but before the "loadinng visuals..." etc comments are done, the unit continues to boot. It finishes loading whatever modules it has to and then shuts down. (with the pop).

If I understand how everything fits together correctly, then the power pic you were referring to earlier is keeping this thing up until the boot has completed.

Does the processor signal the PIC not to dump the power until the boot has completed. If so, why does it not keep it up when the ignition is killed.

It sounds as if the PIC is working correctly.....

Peter

If it's just the two of them we need to work out what is different about their setups compared with everyone elses; and which would also be affected by 2.0 and not 1.0.

Well, here's something I haven't mentioned yet. My alarm has an "extended accessory power" module, which basically keeps everything on until a door is opened. So every time I have been referring to turning the ignition off, I really meant turning the ignition off and opening a door. When I tested with a multimeter, I still had 12-14v on the ignition sense wire with the ignition off before the doors were opened. After opening a door it dropped right to 0v. I didn't think this was an issue because many luxury type cars have this feature. This shouldn’t affect anything, right?

Tom

WOOHOO!!!

It's gone. I have no idea what happened, I haven't touched a thing. The power down thump is now gone, and it goes into standby correctly! It's been gone the whole day (tested it many times), if it comes back I'll keep this updated.

Tom

The worst problems to find are the ones that miraculously fix themselves.

Calvin

Well I've found the problem
Turns out that it was the shutdown delay. I had mine set at 20,000 so I could synchronize, via wireless lan, with the unit still in the car. 2.0b3 and higher writes that as 20,000,000 (milliseconds) to the player .ini file. Whats the bet that when the ignition is switched off, the player reads the value from the file, does an atol on it and ......shits itself.

Of course the question remains why did 20,000 seconds work on 1.03. Did you previously store the value as seconds?

I guess the next question is, what is the maximum timeout, and will it be increased to allow for long standby times.

Cheers
Peter

Tony: This might be a good one for the FAQ

Tony: This might be a good one for the FAQ

Or better yet, for the internal bug list. Heading there now.

Wow. Really good find. That would expain why mine started working because my config.ini was corrupt.

Tom

Hi Rob / Support

I hadn't heard anything back on this one.

Can you confirm that this is the cause.........

Cheers
Peter Kerr

Hi Guys
Its been 10 days and I haven't heard a result yet.
I figured that with the new release, and all the new postings, this one keeps getting lost.

Can someone please check the shutdown code and confirm/deny that this is the cause

Cheers
Peter Kerr

Ahem, this is the *unofficial* BBS. We reserve the right to *not* use this as a support forum.

That said, Richard fixed this bug a couple of days ago.

The value in the config.ini file is in milliseconds. The upper and lower limits in emplode are now correct, and the player bounds-checks the value when it's read from the config.ini file.

The bug with the shutdown delay value is on the internal bug list, and the current internal code now properly bounds-checks the shutdown delay. The next release will have it fixed.

With Beta 11, I tried setting my timeout to 3000, and I got the same shutdown pop others had here. Set it back to my default of 1000, and it's fine.

Also, emplode puts in a comma to seperate the numbers, but will not accept it until it's taken out.

(I finally remembered a few days back I now had a MK2a, and for some reason it dosen't intefere with my keyless remote like my MK2 did. Here is the thread on that issue, from a while back.)