Error 10901 with FlashIIP station

Hi, I can walk me through running the RUPC tool and regist357a registration, let me know your response 

I am available after 10:30am cst today.  When are you available?  If you would prefer to remote in, that is possible.

i need Capsula XL and DryPix smart 6000 software.have anyone can help  me

can you send me your email

I have sent you mail, check your email 

My timeline for this problem is :

• Reader internally registered to Flash IIP from another clinic.
• I connected it to a Console Advance computer
• Reader showed Online superficially but was actually looking for Flash IIP and couldn't find it
• My cassette rejected because the reader couldn't complete its workflow without the Flash IIP
• Technician arrived to re-register the reader to Console Advance
• During that re-registration attempt something went wrong
• Errors 10901 and 11907 appeared
• Connected FlashIIP computer to Reader, didn't change errors.  It appears the reader now has no valid registration at all

On the Fujifilm FCR Carbon X (CR-IR 357) with Flash IIP, the pattern you’re describing (10901 ? 11907 after a re-link attempt) strongly points to a RUPC / system registration mismatch, not a hardware failure. That usually means the issue is in device registration / RU configuration layer, not the reader or console hardware.

What likely happened:

• The system got partially re-registered as the wrong model (355 profile)
• Now Flash IIP and RU0 are out of sync on device type definition
• Boot errors (10901 / 11907) are consistent with invalid RU initialization sequence

What I would focus on:

• Confirm Flash IIP is still pointing to the correct RU type (357), not cached 355 config
• Re-run RUPC, but ensure it fully clears old registration (not just overwrite)
• Verify no leftover 355 registry entries / device definitions in Flash IIP config
• Rebuild RU registration from the original 357 APL package only, not mixed environment
• Restart services after re-registration (important on V8.3)

Important point - Even if IP/ping is correct, Flash IIP will still fail boot if the RU type handshake doesn’t match expected model definition.

This looks like a software registration corruption/mismatch between 355 vs 357 RU profiles, introduced during the attempted console link change—not a failing reader.

Mr Linton, 

Would the above apply if a tech was trying to get the 357 to work with a computer that has Console advance?  Would it be better if someone tried to get the unit working back with the original FlashIIP work station?