EGold Watchdog

8 thoughts on “EGold Watchdog

  1. Hello!

    Our company is currently using the GE865-Quad module togather with a PCB antenna (cable connected not on the same board) within our products. 

     

    The system works fine so fare,  but sometimes I get a message form EGold watchdog at the serial debug interface. After this message the module restarts and runns into the same issue again. It will repeat this until it is disconnected form power supply for some seconds.

     

    So fare I couldn’t find any information about this EGold wathdog or what is happening to cause these watchdog resets.

     

    For some devices (which are running very often into this issue) it helped to change the antenna position or the whole antenna.  

     

    It would be very grate if you could provide some information about the EGold watchdog.  Or if you have any idee what couses this behavior it would be very helpful for me.

     

    Thanks in advance and all the best.

    Stefan Leipold 

      1. Could you please tell me where to look up the sw version?

         

        It is a mobile application, but the restarts happend during baisic testing (module stationary, power supplied by an  power supply unit). 

        The resart occures befor any python script is started (therfore within the first 10 seconds after power on) .

        It seems that the resatart occurs when the module is trying to connect to the GSM network.

         

        1. Stefan, this is a common bad behavior because of a weak power suypply, the higher current needed doing RF jobs cannot be sustained provoking the reset.

          Take out the SIM and read the firmware with AT+CREG.

  2. Thanks for your reply!

    AT+CREG returns the network registration report not the firmware version, dosn’t it? 

     

     For the power supply: this was also my first thought. I had issues with the power supply before. In this cases the module just tried to connect and then restarted without any reply at the debug interface. The blinking pattern of the staus LED showed the same.

     

    The last tests I did with an power supply unit (3A) and an LiPo (2600mAh). I receive the EGold Watchdog reset message at the debug interface and the module restarts. The module continues this cycle until powering off and on again. After that it’s working again…

     

     

  3. Sorry for the delayed answer:

    I used the version 10.00.004 and updated now to 10.00.005

     

    During a test today (module powered from a fully charged 2400mA LiPo – directly connected to the module as mentioned in the hardware user guide) I received the following messages during startup at the aux-uart:

     

     ‘import exceptions’ failed; traceback:<n>

    ImportError: No module named exceptions<n>

    Warning!  Falling back to string-based exceptions<n>

    Python 1.5.2+ (#0, Jan 24 2008, 14:55:00) [C] on GE865<r><n>

    Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam<n>

    <n>

    Last FN 0<n>

    <n>

    Protocols Version: 5.05.000<n>

    System Version: 10.00.005.2-B000_F<n>

    <n>

    *** EGOLD Watchdog <n>

    ‘import exceptions’ failed; traceback:<n>

    ImportError: No module named exceptions<n>

    Warning!  Falling back to string-based exceptions<n>

    Python 1.5.2+ (#0, Jan 24 2008, 14:55:00) [C] on GE865<r><n>

    Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam<n>

    Index = 10<n>

    <n>

    Last FN 1404599<n>

    <n>

    Protocols Version: 5.05.000<n>

    System Version: 10.00.005.2-B000_F<n>

    <n>

    *** Odd address word access 

     The device stuck in this loop until I disconnected the battey for a few seconds. After connecting the battery again everything works just fine.

    During this time I didn’t receive any URC messages at the primary serial interface.