Announcement

Collapse
No announcement yet.

Moto E4 Phones Disconnecting

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • FTC11180
    replied
    We are not using vuforia, only dogeCV. However, when we downloaded a fresh app, and only used a very simple linear autonomous (the dogecv modules were not imported, it was a fresh app) that just moved the robot forward, the phones still disconnect when sitting in the "init" state.

    Leave a comment:


  • Cheer4FTC
    replied
    I can confirm that we are seeing this also with our Moto E4 phones. For some opModes (see below), if Init is pushed and the phones and robot are sitting and waiting (as usually happens before autonomous starts), after 30-60 seconds the phone will disconnect and the DS goes back to "Select Op Mode" with nothing selected.


    Some data points:

    We ran a moderately complex opMode, with Vuforia initialized. It DOES disconnect in this case.

    We ran a simple linear opMode with nothing but runTime telemetry messages being sent to the DS. It does NOT appear to disconnect in this case (we waited for over 3 minutes and it was still OK waiting for the Play button to be pressed).

    We ran the ConceptVuforiaNavRoverRuckus sample opMode with the only change being adding our vuforia key. It DOES disconnect in this case. Tech team, can you reproduce this problem by running this opMode on a pair of synced MotoE4 phones?

    So perhaps the issue is Vuforia related? FTC11180, did you have Vuforia active?

    Tech team, please help ASAP as this makes the Moto E4 phones unusable in competition (at least with Vuforia and/or Vuforia-frame-based CV)!!

    A few lines of the AS Logcat when this happens are below
    Code:
    10-31 08:49:20.779 1466-1936/? E/IzatSvc_Wiper: W/Num of elements returned by LOWI 1
    10-31 08:49:20.784 1466-1760/? D/HS20: Clearing ANQP cache: all: false
    10-31 08:49:20.787 1954-2033/? I/QCNEJ: |CORE| CNE received action: android.net.wifi.STATE_CHANGE
    10-31 08:49:20.788 1954-2033/? I/QCNEJ: |CORE| Updating network info: [type: WIFI[], state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: <unknown ssid>, failover: false, available: true, roaming: false, metered: false]
    10-31 08:49:20.788 1954-2033/? D/QCNEJ: |CORE| Wifi Info Reset
    10-31 08:49:20.788 1954-2033/? I/QCNEJ: |CORE| WifiInfo was reset, abandoning update
        |PB_MSG| sendWifiStatus - subType: 101 networkState: 4 wifiState: 3 rssi=0 freqBand = _2GHz ssid= bssid=00:00:00:00:00:00 ipV4Addr= ifNameV4= ipAddrV6= ifNameV6= timeStamp:2018-10-31 08:49:20.788 net handle=0 isAndroidValidated = false DNS addrs= 0.0.0.0, 0.0.0.0, 0.0.0.0, 0.0.0.0, 
    10-31 08:49:20.790 1954-2033/? I/QCNEJ: |PB_MSG| ****encoding**** --> notifyRatConnectStatus ratType=1 status=4 ipV4Addr= ipV6Addr=
    10-31 08:49:21.822 10896-11063/com.qualcomm.ftcrobotcontroller V/Robocol: issuing peerDisconnected(): lastRecvPacket=2.029 s
    10-31 08:49:21.823 10896-11063/com.qualcomm.ftcrobotcontroller V/RobotCore: Network: unknown, disconnected
    10-31 08:49:21.826 10896-11063/com.qualcomm.ftcrobotcontroller I/RobotCore: ******************** STOP - OPMODE /storage/emulated/0/FIRST/matchlogs/Match-0-Concept:_Vuforia_Rover_Nav.txt ********************
    10-31 08:49:21.826 10896-11054/com.qualcomm.ftcrobotcontroller W/AudioTrack: AUDIO_OUTPUT_FLAG_FAST denied by client; transfer 4, track 44100 Hz, output 48000 Hz
    10-31 08:49:21.827 10896-11063/com.qualcomm.ftcrobotcontroller I/RobotCore: Lost connection while running op mode: Concept: Vuforia Rover Nav
    10-31 08:49:21.828 10896-11908/com.qualcomm.ftcrobotcontroller I/RobotCore: saving match logcat to /storage/emulated/0/FIRST/matchlogs/Match-0-Concept:_Vuforia_Rover_Nav.txt
        logging command line: exec logcat -d -T '10-31 8:48:47.000' -f /storage/emulated/0/FIRST/matchlogs/Match-0-Concept:_Vuforia_Rover_Nav.txt -n4 -v threadtime UsbRequestJNI:S UsbRequest:S art:W ThreadPool:W System:W ExtendedExtractor:W OMXClient:W MediaPlayer:W dalvikvm:W  *:V
    Code:
    
    


    Leave a comment:


  • FTC11180
    replied
    Sorry, here it is

    Leave a comment:


  • FTC11180
    replied
    Here is the code working

    Leave a comment:


  • FTC11180
    replied
    Tom Eng thank you for responding. It is the wifi that is disconnecting. We have 3 pair of moto e4's, and we have been programming with them since September. However, it was not until a competition that we discovered the problem. Once we have pressed init in autonomous, within a minute or so the wifi seems to disconnect. The phones make a chime, and autonomous is no longer initialized. Upon returning to school we tried the other two pair of moto e4's and found they disconnect in the same manner. We loaded the same code onto moto g4s and they can sit in an initialized state without disconnecting. Not all of the phones were up to date from motorola so we performed the system updates. The moto e4s still disconnect while initialized in autonomous. We downloaded a fresh driver station app, and robot controller app and essentially used just the pushbot drive by time sample code and they still disconnected (our original code was using dogecv, so our testing seems to have eliminated that). Through networking, it seems we have found at least one other team out there who is having the same experience. I hope this helps uncover the problem. Thank you.

    Leave a comment:


  • Tom Eng
    replied
    Hi FTC11180

    Could you elaborate on how they are disconnecting? Is it the wifi that is disconnecting or is the USB connection to your REV Robotics Expansion Hub?

    Tom

    Leave a comment:


  • FTC11180
    started a topic Moto E4 Phones Disconnecting

    Moto E4 Phones Disconnecting

    We have 3 pair of Verizon moto E4
Working...
X