Recently I installed both kits in this machine. As soon as I started it up I got a C2102. Color motor lock. I found the Yellow unit was bound. Put the old one back in and ordered another DLP Y unit. Got that today and instantly got a C2102. Pulled it out and it was bound. Called hotline and they had no history on this other than to replace the unit. So I ordered another unit.
I think I know what's happening here. If you look on the box it says max temp 104F. I think somewhere in transport it's sitting in a hot area and the toner is melting causing the bind. Look at the temps in Dallas lately.
Anyone else having similar problems? Just looking for input for now.

Last summer I had the Voyager E version of this story. It came time for the color developer kit. I powered up after completing the parts installation and "Crack!...crunch, crunch, crunch, then "Add Toner" for all the colors (but black).

The two-stage gear that mates with the color developing motor snapped into pieces, and the cyan developing unit was really difficult to start with the drive handle. Once it was started though and the gear was changed, it agitated fine.

I did not connect it to the heat, but I think you're right. Since that one occurrence I resolved to hand turn every developing unit before installing. Since then I have only had (1) color developing drive gear fail, but have come across quite a few 'stiff' developing units, that loosen up eventually (none that I absolutely couldn't use.

Keep in mind they come from Dallas Texas (tommorrow's high 105F, and a hell of a lot hotter in the back of the semi). =^..^=

Ok, I got one now, Dev units are fine, were swapped out when problem first came up, also engine board, and today I swapped the color dev motor for the black one. Machine runs for an hour or so, then codes out, I can get it to restart, can even run the color motor in Sim 30..but it keeps coming back, any suggestions??

Ended up replacing the whole drive pack, DR 855, finally did the trick.

or, we had same issue, tried replacing devs, reoccurred many times. Shook the heck out of the developers, and no re occurrance..so far!!!
check out ta 500 troubleshooting tips on kmaconnect.