Just finished uploading the FP2 bin file, flipped the PMU switch and pushed the reset button. Started to load the FP2 code (i can see it scroll by) but the system keeps looping in this startup stating that certain things failed.

Bank 0 is still partially loading FP1, Bank 1 is partially loading FP2. I can recieve data over the serial line, but I am unable to get to the password prompt to try the upload again.

I'm guessing this needs to go back for reprogramming? This is FP2 Beta Field Test CD...I'm not sure if that has anything to do with the issues...

Thanks.

I have never had any luck doing the upgrade procedure as the book says it goes. We always get a backup of the current database using Hyperterminal, etc., perform the upgrade, default the system, then upload the former database into the system.

When we have tried to use the "book" procedure, we end up with extensions numbered things like "1j%". Despite the fact that they claim you can do an upgrade and rely upon bank switching to save everything, I don't trust it.

i have done many upgrades and i always do what EV said pull a download before you upgrade then do your uprgrade. It sounds like you might have had something go wrong with the upgrade either a corrupt .bin file or the upgrade wasn't finished before you defaulted the switch. Did you try setting the dip switch back to bank 0 it should load the old software? and you should be able to try the upgrade again. let us know

I did do a download before I tried to upgrade. I have that DB saved.

FP1.00 is still loading from Bank 0, but it seems like only partially. I couldn't access VM through 440...it just kept ringing so I checked the slot assignments and for slots 5,6 and 7 is shows a string of numbers, hyphens and letters..I think I remember CKIT somewhere in there (im not at a station to check)...I can push hold on that screen to give me the normal display, then it switches back to the CKIT stuff.

I can't get any response to ENTER at the terminal. I can receive the startup diagnostic data and version display though.

That's exactly what happened to me the first time I tried to do an upgrade. What ended up happening (I think) is that the serial port parameters got messed up during the switch. I ended up completely defaulting the system after the bank switch and then uploaded the database. I have never been successful doing an upgrade without having to completely default the system. I suppose it's probably better that way because the way they say it works in the manual sounds almost too good to be true.

You mentioned you were working with beta software. Do you know what version it is? I know there were problems with ver 2.10.

Are you a registered dealer with Vodavi? I ask only because you can download the latest approved software from Vodavi's website.

ev607797,
You mentioned after the bank switch you defaulted the system with the 2.0 software and it worked? I've been switching back to bank 0 before defaulting with sw8.

A6,
I have all versions of the software available on the ftp site. I just downloaded and tried 2.1 friday with the same results (although this time all messages were human readable. last time it was a bunch of odd chars that looked like the output was corrupted.)

Vodavi had told me 2.1 was the latest stable release. You said there are some issues? I was using the FP2.0 Beta Field trial version because I happened to have it on CD. I've since downloaded the more recent 2.x versions.

No, what I ended up doing is defaulting the system with the old software in it, then performing the upload. After that was done, I did the bank switch and then uploaded the old database. I used WinDBA of course, because they say that's the only way you can safely go from FP1 to FP2 and I didn't want to risk it. I couldn't get it to work any other way, but since this just about happens to me every time (as if I am doing something wrong-probably), I have just used this procedure across the board and it seems to do OK.

Well, I uploaded the 2.0 bin and it looped again, but this time I defaulted the system while it was looping. (I had defaulted it before the upload too)

Seems like it worked. I have term access to with the FP2 software running (and its not looping now.)

I haven't used WinDBA yet. What's the default pass?

Still don't have access to the Overflow to VMID from a UCD. Says it should have been in 2.0 button Flash 60, Button 15 is not working.

in term programming right befor the password prompt what rev of software are you running?

Eng. V2.00 p04-2FE3

Do you happen to know the default password for WinDBA? I saw in the help section of WinDBA that there is a spot for VMID when programming the overflow for UCD groups. I'm wondering if I have to do it through that interface rather than on the 30 button (Although the 2.00 manual says it should work).

I'm also wondering if maybe using a database from a 1.0 system on a 2.0 system is causing the issue with the missing features. Unfortunately I can't shut it down to test it out during business hours.

So it turns out I needed to download the DB to WinDBA for it to convert to a 2.0 DB. I tried doing this by "Downloading from File" using my 1.0 backup. I selected that it was an FP1 DB and then I "Uploaded to File". I used this uploaded file to upload through HyperTerm.

Still doesn't to work.

Another piece to the puzzle. Apparently the XTSc is a little different than the XTS in programming. They told me you must default the system at the same time you toggle the PMU. (Which solved the looping term issue)