i'm working on resuscitating my pic programmer (althought hey aren't that expensive on ebay) to read out the existing program to modify the board to ''clone''.

+

* i mis-wiki-ed before, the programmer's PGC (13) and PGD (14) signals are nc. hijacking these is pretty simple.

−

* the led pins overlap w/ the programmer's CLOCK and DATA signals. these are inputs so it should probably be ok to drive these (from the programmer) w/ both the pic and leds connected.

+

* conveniently MCLR# (4) is tied to vcc through the resistor just above the pic when looking at the board w/ the edge connector on your left. one less pin you have to lift.

* conveniently MCLR# (4) is tied to vcc through the resistor just above the pic when looking at the board w/ the edge connector on your left. one less pin you have to lift.

* RB4/PGM (11) looks like it is nc. having only dorked w/ a pic once in my life (why it was easy to canabalize my homebrew pic programmer for something else), i've never paid attention to lvp or hvp mode. PGM only matters to lvp (and only at startup to set the programming mode).

* RB4/PGM (11) looks like it is nc. having only dorked w/ a pic once in my life (why it was easy to canabalize my homebrew pic programmer for something else), i've never paid attention to lvp or hvp mode. PGM only matters to lvp (and only at startup to set the programming mode).

i mis-wiki-ed before, the programmer's PGC (13) and PGD (14) signals are nc. hijacking these is pretty simple.

conveniently MCLR# (4) is tied to vcc through the resistor just above the pic when looking at the board w/ the edge connector on your left. one less pin you have to lift.

RB4/PGM (11) looks like it is nc. having only dorked w/ a pic once in my life (why it was easy to canabalize my homebrew pic programmer for something else), i've never paid attention to lvp or hvp mode. PGM only matters to lvp (and only at startup to set the programming mode).