This sounds like an interesting project. http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=2680&dDocName=en537999
http://ww1.microchip.com/downloads/en/AppNotes/01045b.pdf
@erm213 - Not a lot - the eeprom is only 256 bytes, the data RAM is similarly limited, and the program memory is not writable. The data patterns would have to be algorithmically generated with a small amount of custom code, it's not really practical IMO to download part of a vixen sequence into the part (besides, there isn't an interpreter available for Renard now).
@tjetzer - that's possible, if someone is up to writing the code for that. Are you more interested in having each PIC run independently, or have server/client type of setup? Bear in mind that the clocks are not perfectly synchronized, so even if the patterns will end up out of phase, even if they started out in sync.
@budude - while it isn't there now, I intend to incorporate the ren4flood changes into this code. It's only a few lines of code to do the r4f changes.
P. Short wrote:@erm213 - Not a lot - the eeprom is only 256 bytes, the data RAM is similarly limited, and the program memory is not writable. The data patterns would have to be algorithmically generated with a small amount of custom code, it's not really practical IMO to download part of a vixen sequence into the part (besides, there isn't an interpreter available for Renard now).@tjetzer - that's possible, if someone is up to writing the code for that. Are you more interested in having each PIC run independently, or have server/client type of setup? Bear in mind that the clocks are not perfectly synchronized, so even if the patterns will end up out of phase, even if they started out in sync.
Phil,
Quite honestly in my case I don't really care. A server/client setup would be fine if could swap the first PIC and leave the existing PICs in place w/o modifying their code. If not, swapping all 6 PICs would be fine. I guess it's easiest to say, whatever the solution is I would be happy.
That product description only mentions PIC18 and up, not the PIC16 family. And, unfortunately, I don't think that the PIC16F688 socket is compatible with anything from those part families. To use that product would probably require an approach like joeytx used.
