Justin Kuhn
Veteran
That's what worked for me, taking the SD card out. A corrupt SD card will bind up the bus that controls all the cards.
System Error - P2 Micon Error
- Thread starter James Webb
- Start date
That's what worked for me, taking the SD card out. A corrupt SD card will bind up the bus that controls all the cards.
Thanks again, Barry, for the help - both here and at dvinfo. I sent my card to Panasonic, hopefully they'll find something soon.
I have a shoot tomorrow - 7 interviews - I'm really hoping that I don't have any other "issues" with the camera. I hate the fact that I'm second guessing with it now. I'm actually bringing my beta along just in case because I don't want to lose this client . . . I didn't think I'd have to worry about something going wrong with a new camera. Oh well, I'm sure it's just a bad card but I'll always wonder. Wish me luck!
John
I have a shoot tomorrow - 7 interviews - I'm really hoping that I don't have any other "issues" with the camera. I hate the fact that I'm second guessing with it now. I'm actually bringing my beta along just in case because I don't want to lose this client . . . I didn't think I'd have to worry about something going wrong with a new camera. Oh well, I'm sure it's just a bad card but I'll always wonder. Wish me luck!
John
hey barry,
how did you fix that?
i have one 16 gb P2 Card that the camera is not recognizing anymore...
could it be an SD Card/Scene File thing?
thanks!
-aaron
Barry_Green
Moderator
Power off/Power on took care of it.
earthling
Active member
By system, I take it you mean HVX. Driver was not up to date, it is now, and... same thing. Wether importing in FCP, copying in the finder or ingesting in P2 viewer I get this same message : "System error, P2 micon error". I don't know what to do.
Cheers,
Damien
Barry_Green
Moderator
No, I mean on the computer system.
Every piece of equipment that sees that card, needs to be updated. The HVX, the card reader, the computer, the P2 Store, everything. There's a different driver for every stitch of equipment.
Every piece of equipment that sees that card, needs to be updated. The HVX, the card reader, the computer, the P2 Store, everything. There's a different driver for every stitch of equipment.
Would like to point out that Barry_Green is probably right about this error. I just got it, I have a feeling it's because of my Firewire Bus. None of the clips are corrupt, the P2 Cards are not broken as I can transfer fine (and suprisingly quickly) via USB2.0 to OS X. So, it's a computer hardware issue, not an HVX200 issue.
However, my Firewire port craps out after a few seconds which is strange. I will try it on the G4 Powerbook and Windows soon.
Oh well, guess that's what the PCMCIA slots are for. =P Gotta try one of those suckers in OS X now.
However, my Firewire port craps out after a few seconds which is strange. I will try it on the G4 Powerbook and Windows soon.
Oh well, guess that's what the PCMCIA slots are for. =P Gotta try one of those suckers in OS X now.
I'm a bit late to this thread, but it did give me a few ideas on what to look into to find a fix.
I started out w/ pretty much the same thing, it seemed to work at first, but then stopped on our lab computers (I work in a school). It wouldn't work on several models of g5s, or mac pros. We figured it was my security, so I tried unmodified systems w/ OSX 10.4.5-11, I tried w/ FCP 5, 5.1, 5.1.4, 6, etc. No luck, but it was still working for one of our instructors on their powerbook, and one of my students MBP.
I tried to transfer via a powerbook... and it worked. I then made it a target disk, and booted a previously 'broken' mac from it, it worked. I tried the other way around, putting a g5 in target disk mode, and booting the powerbook from it, it also worked. So i just pulled my builds out of the equation (a big worry for me). I rebooted the previously broken g5 from its own drive.... and it worked.
To narrow down the fix, I took another 'broken' mac, booted it from a powerbook's drive, it didn't fix it. I took another, and booted the powerbook from it, and it works.
I dont know how yet, but booting a powerbook from a desktop's (put in target mode) seems to fix this problem. I need to test this w/ intel macs yet, and try to narrow down a real fix (is it the firewire controller, is it getting reset when you do this? Is it some setting in open-firmware that is getting fixed? Is it some system-level config that is being reset by introducing the laptops hardware to it?). I also need to test to see if I clone this system if it sticks, or if the individual system needs to have this done (which will suck, I have 150 Macs). I also need to verify this works across my 3 HVX-200s, and 6 p2 cards.
Hope this is of some use to you guys. Ill post more as I figure it out.
I started out w/ pretty much the same thing, it seemed to work at first, but then stopped on our lab computers (I work in a school). It wouldn't work on several models of g5s, or mac pros. We figured it was my security, so I tried unmodified systems w/ OSX 10.4.5-11, I tried w/ FCP 5, 5.1, 5.1.4, 6, etc. No luck, but it was still working for one of our instructors on their powerbook, and one of my students MBP.
I tried to transfer via a powerbook... and it worked. I then made it a target disk, and booted a previously 'broken' mac from it, it worked. I tried the other way around, putting a g5 in target disk mode, and booting the powerbook from it, it also worked. So i just pulled my builds out of the equation (a big worry for me). I rebooted the previously broken g5 from its own drive.... and it worked.
To narrow down the fix, I took another 'broken' mac, booted it from a powerbook's drive, it didn't fix it. I took another, and booted the powerbook from it, and it works.
I dont know how yet, but booting a powerbook from a desktop's (put in target mode) seems to fix this problem. I need to test this w/ intel macs yet, and try to narrow down a real fix (is it the firewire controller, is it getting reset when you do this? Is it some setting in open-firmware that is getting fixed? Is it some system-level config that is being reset by introducing the laptops hardware to it?). I also need to test to see if I clone this system if it sticks, or if the individual system needs to have this done (which will suck, I have 150 Macs). I also need to verify this works across my 3 HVX-200s, and 6 p2 cards.
Hope this is of some use to you guys. Ill post more as I figure it out.
Did you ever figure this problem out, bc we are having the same issue with our school's edit bays? I can load off of the camera at my personal workstation, which is the same as the edit systems (G5 connected to Fibrejet), but those systems lock up with the dreaded error message. We logged in as administrator to bypass security, but you can't even drag the raw files to a disk without the error. Students have been off loading files to a hard drive connected to the camera (host mode) and then importing.
Barry_Green
Moderator
DON'T try to copy firewire on the PC. And don't try USB on a Mac. Those two options are specifically mentioned in the user manual as being "not guaranteed."
Mac is guaranteed with firewire.
PC is guaranteed with USB.
Mac is guaranteed with firewire.
PC is guaranteed with USB.
filmguy123
Veteran
FWIW... I actually solved this problem on my MAC by changing my camera away from the recommended firewire mode to USB 2.0. I've been using it on USB 2.0 is OSX with no problems; actually, it performs faster (480mbps > 400mbps).
Some research shows that 1394 was developed by Apple, USB developed for Windows. They both work totally fine together; I've used firewire for years in Windows, and USB hard drives for years on Mac. Really does not matter, but I suppose one you could make any argument that 1394 is *more* compatible on Mac... but really... doesn't matter...
Anyhow, switching to USB 2.0 on Mac made my P2 Micon Error disappear.
Barry_Green
Moderator
If you're having a problem, I guess it doesn't hurt to try it. Just remember that they clearly state in the manual that USB mode is not guaranteed to work on the Mac.
p2 Micon Error fix for Panasonic HPX p2HD
p2 Micon Error fix for Panasonic HPX p2HD
found this thread searching for the p2 micon error with our panasonic HPX p2HD that was occurring on one Mac Pro but not another. This turned out to be the fix!
p2 Micon Error fix for Panasonic HPX p2HD
found this thread searching for the p2 micon error with our panasonic HPX p2HD that was occurring on one Mac Pro but not another. This turned out to be the fix!