Menü
Aktuelles
Von:
Filter

RESET cause: watchdog

Mr. Tree schrieb:
I am Not Sure, I know there was a Problem with watchdog reset for some Users, but from what you described and the Log, the Board dies in middle of a dump. 4p is pretty beefy, but.. If you have Access to a laboratory Power source, Connect the battery and Stress it with 3 to 5 amps shorting and See what the voltage does, then you can be Sure its Not the battery? You could use an RC or any charger with discharging function too. Another Thing ist to use and measure the battery over the dead Switch. I think the orig deadswitch of the Set is too cheapo, ITS really a very Bad switch and can cause troubles. Thats my experience.
Or use .230 and See If Things are different and No reset occurs. Sorry for Capital Letters, used my Phone in German language.
Zum Vergrößern anklicken....
thanks for your reply.
I've changed the push button.... let see
 
In the log file LOGxxxx.txt, a line is output every 5s (5000ms) with, among other things, free memory ("freem=") and the value of the stack pointer ("sp="). If you look at the difference between two consecutive values of the stack pointer, you will always find a value around 5000. That correlates very well with the time difference of the line output. Why should the value of the stack pointer increase by about 5000 every 5s? I do not understand that! @AlexanderG: Can you explain that?
 
Silberstreifen schrieb:
Did that solve your problem?
Zum Vergrößern anklicken....
Unfortunately no. as work around I've setup an MQTT communication, and when my home system (jeedom) detects the rover is IDLE, it restarts it automatically.

I don't know what could be the problem. To investigate deeper, I'm thinking to use and RPI and arduino IDE connected to the Grand central and act as a gateway when running.
I'm looking to this type of solution (how to power it, how to add good wifi, etc)
 
I found, that my GPS reset doesnt Work any more. It did, I believe before I updated the ublox. Now, the robot restarts If a GPS reset is triggered.
 
At the beginning of Last year, GPS reboot did Work for me. But eventually i updated the Firmware of the ublox and changed some settings to be permanent. This year, i noticed that the sunray configuration of ublox doesnt Work. If I define GPS_FILTER true ardumower Software will Error ON start. If I leave this off, and just Trigger restart GPS from App, mower restarts.. as If there is No GPS wire fix present and sunray Crashes or Errors which leads to a reset.
 
Mr. Tree schrieb:
At the beginning of Last year, GPS reboot did Work for me. But eventually i updated the Firmware of the ublox and changed some settings to be permanent. This year, i noticed that the sunray configuration of ublox doesnt Work. If I define GPS_FILTER true ardumower Software will Error ON start. If I leave this off, and just Trigger restart GPS from App, mower restarts.. as If there is No GPS wire fix present and sunray Crashes or Errors which leads to a reset.
Zum Vergrößern anklicken....
Ok thanks for the explanation.
I've also updated the firmware of the GPS, but I don't think I'm in your context has the configuration is successfully loaded from my log files :

UBLOX::begin serial
using gps driver: UBLOX
trying to connect to ublox f9p...
NOTE: if GPS is not responding either set 'GPS_CONFIG=false' in config.h or perform GPS wire fix (see Wiki)
trying baud 115200
ERROR: GPS receiver is not responding
trying baud 38400
GPS receiver found!
ublox f9p: sending GPS rover configuration...
idx=0...OK
idx=1...OK
idx=2...OK
config sent successfully
 
This night the rover was not able to have a FIX signal, strange because the precision was 0.02

I've tried a reboot GPS, and reboot robot from the application, but doesn't fix the issue

only a power off, power on of the robot has worked..... :unsure:
 
That might be, because the GPS isn´t resetted cold, but hot or warm... there are 3 reset modes for the ublox. hot, warm, cold. Cold would be like power off and on again. If you research the reset routine, you might find out that there is no cold reset. Cold means start from beginning with nothing, hot means something like i saw some sattelites and had a solution... i will use now too... XD At least i believe that. But a cold reset does the trick for me. Last year.... There is a cold reset enable somewhere in the code, i think... but if you research what it does, you find it´s not used anywhere.
 
Zuletzt bearbeitet:
Hmmm, gute Frage. Ich bin vor 2 Jahren mal durch die ganze ublox PDF Doku geflogen, dort müsste hot, warm und cold beschrieben sein. Also, was der reset alles beinhaltet und ob diese Register auch dabei sind.
 
Ich habe auf jeden Fall hardreset ausprobiert, ist nur eine Zeile Änderung im Code. Ohne Sunray FW reboot bleibt der mower im invalid status
 
Forcing a receiver reset
Typically, in GNSS receivers, a distinction is made between cold, warm, and hot start, depending on
the type of valid information the receiver has at the time of the restart.
• Cold start: In cold start mode, the receiver has no information from the last position (e.g.
time, velocity, frequency etc.) at startup. Therefore, the receiver must search the full time and
frequency space, and all possible satellite numbers. If a satellite signal is found, it is tracked
to decode the ephemeris (18-36 seconds under strong signal conditions), whereas the other
channels continue to search satellites. Once there is a sufficient number of satellites with
valid ephemeris, the receiver can calculate position and velocity data. Other GNSS receiver
manufacturers call this startup mode Factory startup.
• Warm start: In warm start mode, the receiver has approximate information for time, position,
and coarse satellite position data (Almanac). In this mode, after power-up, the receiver
normally needs to download ephemeris before it can calculate position and velocity data.
As the ephemeris data usually is outdated after 4 hours, the receiver will typically start with
a warm start if it has been powered down for more than 4 hours. In this scenario, several
augmentations are possible. See Multiple GNSS assistance.
• Hot start: In hot start mode, the receiver was powered down only for a short time (4 hours
or less), so that its ephemeris is still valid. Since the receiver does not need to download
ephemeris again, this is the fastest startup method.
Using the UBX-CFG-RST message, you can force the receiver to reset and clear data, in order to see
the effects of maintaining/losing such data between restarts. For this, the UBX-CFG-RST message
offers the navBbrMask field, where hot, warm and cold starts can be initiated, and also other
combinations thereof.
The reset type can also be specified. This is not related to GNSS, but to the way the software restarts
the system.
• Hardware reset uses the on-chip watchdog, in order to electrically reset the chip. This is an
immediate, asynchronous reset. No Stop events are generated.
• Controlled software reset terminates all running processes in an orderly manner and, once
the system is idle, restarts operation, reloads its configuration and starts to acquire and track
GNSS satellites.
• Controlled software reset (GNSS only) only restarts the GNSS tasks, without reinitializing the
full system or reloading any stored configuration.
• Hardware reset (after shutdown) uses the on-chip watchdog. This is a reset after shutdown.
• Controlled GNSS stop stops all GNSS tasks. The receiver will not be restarted, but will stop any
GNSS-related processing.
• Controlled GNSS start starts all GNSS tasks
 
Hmm, das ja doof. Ich kann es bei mir leider gar nicht testen, da der mower sich zur Zeit komplett rebootet wenn ich einen gpsreset mache. Auch noch sone Baustelle XD
 
Ok thx,
wenn ich in den Sunray config reinschaue, dann steht dort
Code: 
// configure ublox f9p with optimal settings (will be stored in f9p RAM only)
also wenn man noch nie mit U-Center das Modul beschrieben hat ist das Teil nach einem reset auf Werkseinstellungen, so meine Theorie
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben