Thankyou for your response, just re-flashed the 1.0.2 version and carried out a check, yes it does look like it is the watchdog that is causing the reset, see snip of log from Repetier Server below. So the watchdog is not getting fired/reset in time, not sure how to profile a running arduino due to work out where the time is being used up, is it possible to alter the watchdog timeout or do I need to look at removing / disabling features?
In the meantime I'll take a look at the watchdog functionality between 0.92.9 and 1.0.2 to see if anything has changed.
10:05:50.124: wait
10:05:50.739: T:21.25 /0 B:20.83 /0 B@:0 @:0
10:05:51.124: wait ( started a 'home all' from the control panel )
10:05:56.344: start
10:05:56.344: Info:Watchdog Reset <= watchdog reset
10:05:56.344: Detected EEPROM version:19
10:05:56.345: M110 N0
10:05:56.346: N2 M115
10:05:56.346: N3 M220 S100
10:05:56.346: N4 M221 S100
10:05:56.347: N5 M355
10:05:56.347: N6 G92 E0
10:05:56.347: N7 M114
10:05:56.348: N8 G90
10:05:56.348: N9 M111 S6
10:05:56.349: N10 M360
10:05:56.349: N11 M539 S1
