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
Can you please give use more information about the sw. version you are using and the scenario where the module restars?
Is it a fixed or a mobile application?
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.
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.
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…
Sorry should be AT+CGMR of course.
What message are you receiving, and did you try the test without SIM?
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>
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
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
Can you please give use more information about the sw. version you are using and the scenario where the module restars?
Is it a fixed or a mobile application?
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.
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.
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…
Sorry should be AT+CGMR of course.
What message are you receiving, and did you try the test without SIM?
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:
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.
OK but this version number shows is not the production release is it?