Ticket #562 (assigned defect)

Opened 7 years ago

Last modified 5 years ago

[DEPENS] at+mode=2 stops the cell from reacting any more

Reported by: felixmoeller Owned by: andrewb
Priority: normal Milestone:
Component: Plugin: moto Version: 0.38
Severity: normal Keywords:
Cc:

Description

Just playing with trunk and found out the following.

Doing two msynctools --discover the second hangs at AT&F. This is caused by

        self.__do_cmd('AT+MODE=2') # change mode again
        line = self.__readline()   # swallow the "+MBAN" output that MODE=2 generates
        assert(line.startswith('+MBAN:'), "Unexpected output after AT+MODE=2: " + line)

Removing the block above solves the problem. Otherwise I know no other way then reattaching the phone. (RazrV3xv)

Change History

comment:1 Changed 6 years ago by felixmoeller

  • Version changed from 0.32 to 0.34

Nothing changed. So updating my ticket to 0.34.

comment:2 Changed 6 years ago by andrewb

  • Status changed from new to assigned

Hi Felix,

Are you sure AT+MODE=2 is to blame for the hang? Does your phone reliably and repeatedly hang at this point?

The reason I ask is that I have observed my phone appearing to "hang" (ie. fail to respond to commands) when moto-sync starts talking to it, but this happened even before we changed to use AT+MODE=2. I have not been able to figure out what causes it, but unplugging/replugging the phone always fixed it, as it did for you. So, I would like to be sure that your problem is related to the change of mode before trying to change it (because this fixed bugs for other people).

Cheers, Andrew

comment:3 Changed 6 years ago by felixmoeller

yes i can reproduce it here with:

python-opensync-0.34_SVN2779-1.1
libopensync-plugin-python-module-0.34_SVN2779-1.1
libopensync-devel-0.34_SVN2779-1.1
libopensync-plugin-vformat-0.34_SVN2779-1.1
libopensync1-0.34_SVN2779-1.1
libopensync-plugin-file-0.34_SVN2779-1.1
libopensync-plugin-syncml-0.34_SVN2779-1.1
libopensync-plugin-moto-0.34_SVN2779-1.1
libopensync-tools-0.34_SVN2779-1.1

comment:4 Changed 6 years ago by felixmoeller

For the record with the following it works for me.

--- /usr/lib/opensync/python-plugins/motosync.py.orig    2007-11-10 23:30:41.000000000 +0100
+++ /usr/lib/opensync/python-plugins/motosync.py         2007-11-10 23:36:27.000000000 +0100
@@ -801,9 +801,10 @@
         # people have reported that other commands only work in MODE=2, hence this...
         self.__do_cmd('AT+MODE=0') # change mode
         self.__do_cmd('AT&F')      # reset to factory defaults
-        self.__do_cmd('AT+MODE=2') # change mode again
-        line = self.__readline()   # swallow the "+MBAN" output that MODE=2 generates
-        assert(line.startswith('+MBAN:'), "Unexpected output after AT+MODE=2: " + line)
+        # This hangs the phone on the second run (at least my RAZRV3xv).
+        # self.__do_cmd('AT+MODE=2') # change mode again
+        # line = self.__readline()   # swallow the "+MBAN" output that MODE=2 generates
+        # assert(line.startswith('+MBAN:'), "Unexpected output after AT+MODE=2: " + line)

         self.__do_cmd('ATE0Q0V1')  # echo off, result codes off, verbose results

The poster of http://opensync.org/ticket/505 added these lines ...

comment:5 Changed 6 years ago by felixmoeller

  • Version changed from 0.34 to 0.35

updating.

comment:6 Changed 5 years ago by tuju

  • Version changed from 0.35 to 0.38
  • Summary changed from at+mode=2 stops the cell from reacting any more to [DEPENS] at+mode=2 stops the cell from reacting any more

python-api is broken.

Note: See TracTickets for help on using tickets.