P. Short wrote:OK, I've got some sample code here that flashes all of the lights on and off at about a two-second pace (don't time me...) when there isn't any incoming data. It doesn't send data downstream, although code could be added to do so at the spot where new code is hooked in.I'm not sure if I want to upload the code for general use yet, for fear that it would be confused with the regular Renard start_address firmware. Any suggestions (or volunteers) for avoiding a general mess at this point?
PS By 'here', I mean on my computer.
I'd like to try it an modify it for the PIC18Fxxxx stuff if thats OK with you.
Mactayl wrote:I'd like to try it an modify it for the PIC18Fxxxx stuff if thats OK with you.
Sent. Not that there is much to it. It's just a counter that is incremented at the end of each PWM cycle (120 times/sec for 60 Hz, 100 times/sec for 50 Hz), and is reset whenever a character is received. When that counter overflows the user code is called.
I will try it tonight.:)
Thanks Phil,
Took a quick look at it and as for other controllers down the line if they had the firmware installed they would also start running there own sequence and you would not need to transmit any data from the first controller to the other controllers as the they would respond to the Renard data stream as soon as they receive Renard data correct
Yes. It could be done either way - each controller could run independently when the data stops coming, or the lead PIC could start sending data when it stops receiving data. In the latter case all of the downstream PICs would see a one or two second gap in incoming data before the first PIC starts sending, so they would need to be programmed to ignore that gap (i.e. use current, unmodified firmware). At the moment that duration of that gap is hard-coded, but it would be fairly easy to make it configurable.
