Bugger.

I just tried to update the firmware on my PCR800, and halfway through (when I hit the C3 button) the display switched to FFF. Not only can I not get rid of this, when I flick the switch (under the barcode) back into the 'normal' position, the PCR won't even switch on.

Any ideas?

Sorry to derail, just hoping someone else familiar with the PCR800 might know what to do.

A bit of a long shot..........Have you tried to resend it?
 
Also make sure you haven't touched the other switch under the barcode, that'll stop a power up.

Steve

if you get it sorted let me know. I'm in the same position. If your keyboard is less than 3 years old Roland will fix it but I don't suppose it will be if you are on 1.03. Mine was just over 3 years old and they didn't want to know and weren't helpful.
 
I won't be buying another Roland keyboard as a result.

FastBikerBoy


A bit of a long shot..........Have you tried to resend it?
 
Also make sure you haven't touched the other switch under the barcode, that'll stop a power up.

Cheers Karl, I didn't even get as far as sending the update. After I turned the unit on as directed with the switch in the 'reset' position, I followed the bumph on which buttons to press on the unit:
 
2. Use a USB cable to connect the PCR to your PC, and set the PCR's power switch to the USB position.
3. When the PCR's display indicates 103, press the [ENTER] button.
4. When the PCR's display indicates "ERAS," press the [DYNAMIC MAPPING] button.
5. When the PCR's display indicates "SURE," press the [C3] button.
 
I got the 'ERAS' message in the window but when I pressed the Dynamic Mapping button, that's when I got the 'FFF' error.
 
And yup, I have been using the correct switch mate.
 
The connection via the USB is definitely still working because whenever I have the switch in the 'Update' position, the unit fires up (with the FFF message); it's only with the switch in the normal position that it's completely dead. I also double-checked in X2 and it 'sees' the PCR in update mode, but not in normal mode.
 
 

maxsax


Steve

if you get it sorted let me know. I'm in the same position. If your keyboard is less than 3 years old Roland will fix it but I don't suppose it will be if you are on 1.03. Mine was just over 3 years old and they didn't want to know and weren't helpful.
 
I won't be buying another Roland keyboard as a result.

Hi Martin
 
I've tried posting this problem on the Roland forums HERE, and I've also just stumped up £11 on JustAnswer to see if an 'expert' knows how to sort it out.
 
I'll let you know if I get an answer that actually solves this.
 
 
 

SteveStrummerUK


I also double-checked in X2 and it 'sees' the PCR in update mode, but not in normal mode.

 

Have you tried sending the sysex file from X2 or is the unit itself locked up completely? (And if that works I'm only a tenner. )

FastBikerBoy

SteveStrummerUK


I also double-checked in X2 and it 'sees' the PCR in update mode, but not in normal mode.

 

Have you tried sending the sysex file from X2 or is the unit itself locked up completely? (And if that works I'm only a tenner. )

 
Woo-hoo!!
 
I'm not quite sure how, but I think I've cracked it. And thanks for the advice Karl
 
Martin, if it helps, here's what I did:

1. Make sure the switch is in the 'update' position on the underside of the PCR800
2. Turn the PCR on while holding down the Enter button, this seems to clear the FFF error message and puts you back where you were before it 'crashed' - in my case, the message showing was ERAS
3. Carry on the installation from that point in the process (i.e. in my case it was to press the Dynamic Mapping button)
4. Run UpdSMF, select your PCR, navigate to the downloaded p00001.mid file and hit Scan SMF:
   
   
5. Once you get the message to tell you the transfer is complete:
   
   
   
   ... follow the instructions to switch off the PCR, put the switch back and then perform a factory reset.
   
   

SteveStrummerUK

FastBikerBoy


A bit of a long shot..........Have you tried to resend it?
 
Also make sure you haven't touched the other switch under the barcode, that'll stop a power up.

Cheers Karl, I didn't even get as far as sending the update. After I turned the unit on as directed with the switch in the 'reset' position, I followed the bumph on which buttons to press on the unit:
 
2. Use a USB cable to connect the PCR to your PC, and set the PCR's power switch to the USB position.
3. When the PCR's display indicates 103, press the [ENTER] button.
4. When the PCR's display indicates "ERAS," press the [DYNAMIC MAPPING] button.
5. When the PCR's display indicates "SURE," press the [C3] button.
 
I got the 'ERAS' message in the window but when I pressed the Dynamic Mapping button, that's when I got the 'FFF' error.
 
And yup, I have been using the correct switch mate.
 
The connection via the USB is definitely still working because whenever I have the switch in the 'Update' position, the unit fires up (with the FFF message); it's only with the switch in the normal position that it's completely dead. I also double-checked in X2 and it 'sees' the PCR in update mode, but not in normal mode.
 
 

maxsax


Steve

if you get it sorted let me know. I'm in the same position. If your keyboard is less than 3 years old Roland will fix it but I don't suppose it will be if you are on 1.03. Mine was just over 3 years old and they didn't want to know and weren't helpful.
 
I won't be buying another Roland keyboard as a result.

Hi Martin
 
I've tried posting this problem on the Roland forums HERE, and I've also just stumped up £11 on JustAnswer to see if an 'expert' knows how to sort it out.
 
I'll let you know if I get an answer that actually solves this.

 

So sorry to here this.  I have not tried to update yet, and given two of you having what looks like the same problem updating the firmware, I think I am going to live with vers 1.03 for a while.  


Please keep us updated as to any remedy you find.

We must have posted at the same time.  Are you saying that you now have v.1.05 working?  

cecelius2


We must have posted at the same time.  Are you saying that you now have v.1.05 working?  

 
Hi Wayne, yes, everything now seems to be working fine with v1.05.
 
 

Thanks Steve, I'll give it a try tomorrow and let you know. Glad you got yours running ok.