search

ftctechnh / ftc_app

FTC Android Studio project to create FTC Robot Controller app.
761 stars 3.16k forks source link

Robot Controller 3.1 not finding any Modern Robotics Devices #355

Open positronemitter opened 7 years ago

positronemitter commented 7 years ago

When RC and DS apos updated to 3.1, they no linger would find and thereby not setup any of the Modern Robotics controllers. Downgrade to Ver 2.4 fixes issue.

bqrichards commented 7 years ago

Have you looked at the closed issue #350? Your issue and symptoms sound similar, I would try that and let us know what happens!

positronemitter commented 7 years ago

Nearly identical problem but RC app Ver 3.1 works fine with Rev Robotics controller but not Modern Robotics. The instant run fix didn't seem to alter.

positronemitter commented 7 years ago

Will retry the 3.1 again and see if fresh start now might work.

positronemitter commented 7 years ago

Also, works fine with Instant Run deployed using ver 2.4.

bqrichards commented 7 years ago

Darn, that fixes some issues such as this. Are you able to supply us with an attachment of the robot log from your RC with v3.1 on it? This way we can analyze and see if something is crashing the scanning process. If possible, please provide a fresh one by deleting one if it exists and then running v3.1 RC, scanning for hardware and then uploading that .txt log?

positronemitter commented 7 years ago

Brandon, Deleted all and reloaded again with latest update 3.1. This time we ran it with Instant Run and Extended Logs and submitted the logs to Google as they request. Then we again uninstalled and reloaded with 3.1 but again turned of Instant Run. This time its working like a champ. Can't thank you enough. We probably would not have committed the time to trying it over if it wasn't for your advice. Stay Awesome!

On Mon, Jul 17, 2017 at 9:52 PM, Brandon notifications@github.com wrote:

Darn, that fixes most sporadic / uncommon issues such as this. Are you able to supply us with a copy the robot log from your RC with v3.1 on it? This way we can analyze and see if something is crashing the scanning process. If possible, please provide a fresh one by deleting one if it exists and then running 3.1, scanning for hardware and then uploading that .txt log?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ftctechnh/ftc_app/issues/355#issuecomment-315934979, or mute the thread https://github.com/notifications/unsubscribe-auth/AX1YpsCHKUnYTdXkU9dTs95Vt_edMZfzks5sPA_fgaJpZM4Oaths .

bqrichards commented 7 years ago

I'm glad I could help, @positronemitter! Also don't forget to mark the issue as closed if the problem is no longer persisting.