Guys that are interested in this topic,
I have now been running my "QUICK_AND_DIRTY" type of fix for several
hour and it works perfectly.
It is an external uC (PIC16F630 which I had lying around), programmed
in a few lines of assembler and hardwired to the reset pins on the
little devil (868 XBee PRO). It sends the HW variant of the "three
finger salute" once every 6'th minute or so. Dependant on SERIAL_DEBUG
option used in MP, you could do with a lot lower reset frequency, but
this takes care of even the most demanding debug format
(SERIAL_UDB_EXTRA) running with fully opened throttle.
It works so well that I have yet to see the reset in the debug data
captured to disk. (it WILL be some lost characters, but I really don't
care if it is a second of data missing from a file that spans 2 hours
Now I'm running SERIAL_ARDUSTATION as debug format to be able to read
debug data in realtime while in HIL simulation environment. Here I
haven't seen a single "hickup" (lost line) while the reset triggers.
The reset takes about 200ms I.I.R.C and it is possible that I have
been lucky and the reset have executed "between the lines".
ARDUSTATION pumps out 5 lines of text every sec as default. Dataspeed:
I'll have a closer look at this later, but the new XBees I received
yesterday behave much better than the first set I got. They often got
hung up in an "un-known state" after a reset and had to be reset
again. Sometimes up to several times before they came back to life
again. Possibly I have a different firmware in these, I actually think
so, or I had got a defect one with my last order.
Now I'm looking forward to take this setup outside and do some serious
range testing.The last setup managed to give me a distance of right
under 3km without any lost packages (NON-LOS in urban terrain with TX
power set to the maximum of 300mW.)
On Sep 7, 8:13 pm, Marc-X <marcus.fah...@gmail.com
> That's exactly what I was planning to do, but instead of using
> hardware resources (IO pins on the UDB for example, or an external
> timer for the reset), I thought os just sending the "soft reset" AT -
> code (FR) through the UART. That way it happens without any need for
> additional hardware.
> Or do I miss something here? Is theXBeeuC accessible for programming