Announcement

Collapse
No announcement yet.

Moto E4 Phones Disconnecting

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

  • Tom Eng
    replied
    Hi Folks - Note that this problem is not limited to the Motorola E4 phone. The same behavior occurs for the Moto G5 and G5 Plus phones. If these phones are used as a Driver Station and are in the waitForStart state for a period of time (which has been observed in as little as 30 seconds, or as long as 3 minutes) the Driver Station phone can disconnect momentarily from the Robot Controller.

    The workaround prescribed for the E4 phone also works for the G5 or G5 Plus phones.

    Leave a comment:


  • Tom Eng
    replied
    Thank you everyone for the feedback and troubleshooting. This specific issue was not revealed when we tested the phones this past summer. The workaround appears to be sending telemetry messages while waiting for a start command.

    I've updated the Troubleshooting section of the GitHub ftc_app Wiki to include details on how to avoid this problem for Blocks and Java programmers:

    https://github.com/ftctechnh/ftc_app...eported-102018

    Tom
    Last edited by Tom Eng; 11-26-2018, 08:38 AM.

    Leave a comment:


  • thensley
    replied
    We were using "while !isStarted()" but not sending any telemetry back to the phone so we replaced the while !isStarted() with "
    while (!opModeIsActive()&&!isStopRequested()) { telemetry.addData("Status", "Waiting in Init"); telemetry.update(); }" and it seems to be working fine. Thanks for the help guys! Cheer4FTC

    Leave a comment:


  • Cheer4FTC
    replied
    thensley The workaround is to add a telemetry message during init_loop (or while waiting after init in a LinearOpMode). This seems to prevent it from disconnecting.

    Leave a comment:


  • thensley
    replied
    Tom Eng has there been an update?

    Leave a comment:


  • thensley
    replied
    We checked the sleep timer and it is set at 30 mins but we lose connection between 30 and 45 seconds. Is FIRST still working on this?

    Leave a comment:


  • Philbot
    replied
    Huh... if it is a screen inactivity timeout, can you check to see if the sleep timer is set to a really short time eg: 1 min.
    If so, can you extend the sleep time out, and test again.

    Leave a comment:


  • Philbot
    replied
    Originally posted by Cheer4FTC View Post
    but if I comment out the 2 telemetry lines, it disconnects after 30-60 seconds. So this does seem to point towards some timeout issue in the Moto E4 driver station if it doesn't get any messages for a while
    Sorry, I edited my last post badly...

    I was asking if you could send a Driver Station log file showing the disconnect.

    It's probably doing it all the time when app is sitting idle, but you just don't notice it until you init the opmode.

    Leave a comment:


  • Philbot
    replied
    [QUOTE=Cheer4FTC;n67270]Good thinking, gorpong ! If I run a basic linear opMode with the following code replacing waitForStart(), it seems to sit in init just fine.
    Code:
    while (!opModeIsActive()&&!isStopRequested()) { telemetry.addData("Status", "Waiting in Init"); telemetry.update(); }
    but if I comment out the 2 telemetry lines, it disconnects after 30-60 seconds. So this does seem to point towards some timeout issue in the Moto E4 driver station if it doesn't get any messages for a while.

    Any chance of getting a Driver Station log with the fail in it.
    Seems like the smoking gun would be in there...

    Leave a comment:


  • Tom Eng
    replied
    Thanks all for the detailed info. We'll check this out. I wonder if this is some type of power save issue (just thinking out loud - I do not have any evidence that it is).

    Leave a comment:


  • Cheer4FTC
    replied
    Good thinking, gorpong ! If I run a basic linear opMode with the following code replacing waitForStart(), it seems to sit in init just fine.
    Code:
      
     while (!opModeIsActive()&&!isStopRequested()) {     telemetry.addData("Status", "Waiting in Init");     telemetry.update(); }
    but if I comment out the 2 telemetry lines, it disconnects after 30-60 seconds. So this does seem to point towards some timeout issue in the Moto E4 driver station if it doesn't get any messages for a while.

    FTC11180 , try replacing your waitForStart() with the above code and see if that possible workaround addresses your issues until the real bug can be found and fixed.

    Leave a comment:


  • gorpong
    replied
    Are you running a LinearOpMode for your Autonomous? If not, ignore the rest of this post as it only is relevant if you're running a LinearOpMode.

    If you are doing LinearOpMode then when you have the disconnects, are you calling waitForStart(); or are you doing a while (!isStarted() && !isStopRequested()) { telemetry-stuff; }?

    If you are using waitForStart(), what about trying the while !isStarted() and sending telemetry back to the driver station.

    One of the comments in this thread mentioned using the E4's as the DS and RC didn't have the problem when the OpMode was passing back telemetry while waiting, so I'm wondering if there's possibly some timeout on the E4 that might be in the DS when it's not getting anything back from the robotController (there's supposed to be a keepalive, but who knows), and if you can actively make the DS do something while waiting, it might not disconnect.

    I hope this helps.

    -- Gordon.

    Leave a comment:


  • FTC3491
    replied
    We're having problems with our E4 phones, but haven't been able to track it down yet. We've been following the thread, but didn't have any answers to offer.

    The problems we're having seem random and we haven't identified any patterns yet.

    The phones are new, so we've been trying to get the settings right. Our first thought was that the problem might have been coming from all of the preinstalled Apps. It seemed like there were random messages asking for updates, or that some app didn't have access to the internet. We've been disabling apps and blocking notifications, which has helped a bit.

    At the moment, our main challenge is tele-op. It will work for a short period of time (10-15 minutes), and then the robot starts behaving strangely. One time the right side of the drive system stays on at full power even when no one is touching the controller. (Watching the robot do donuts is cute, but not effective.)

    Sometimes a complete power cycle will work, other times not. Last night, driver practice ended without the team being able to restart the robot.

    The log files hinted at some possible things to check, but we're a long way from solving the issue.

    We've ran autonomous, but only for program testing. Our robot hasn't spent time waiting for start, so no data to add to that discussion yet.

    Leave a comment:


  • Cheer4FTC
    replied
    I'm guessing only a few teams have competed so far (where this issue shows up) and a small percentage are using E4s, so the overlap is not a lot of teams at this time.

    Leave a comment:


  • FTC11180
    replied
    Cheer4FTC we just tried a similar setup, using the E4 as the RC and a G4 as the DS. We have left it initialized for quite a long time and no disconnect. It does seems that the issue is occuring when the E4 is the DS. Im just surprised more teams aren't reporting an issue.

    Leave a comment:

Working...
X