Google Hangout – FTC New Technology Demo

[Tom Eng]

Hi Folks,

We plan on releasing the apps and the SDK soon. You can configure the robot to have a null hardware configuration (no hardware modules attached) and if you have the SDK, even though you don't have the hardware yet, you can still write some basic op modes and test things like the telemetry function (you can send data back from the robot controller to the driver station) and learn how to select and run an op mode.

Tom

[CraigRochester]

I haven't read in any of the posts about how App Inventor will work with the new hardware/software systems...

[Philbot]

Hi Craig.

I got to participate in a good demo of App Inventor at Worlds. They have taken the Scratch-like programming interface of App Inventor, and added some FTC robot-centric control "blocks". The graphical design method seems to essentially encapsulate the same logic that would be used in Android Studios, but without the user having to learn Java Syntax. For Teleop, the "code" will be pretty simple. For any sort of autonomous above a simple sequence of steps, I think the App Inventor Graphical style will get pretty cumbersome.

So... Great for rookie and intermediate teams, but probably not the best choice for teams that like to do extensive auto programming (JMHO).

To deploy the code, the APP Inventor compiles online and then can present a QR code that shows the phone where to download the newly created app from.
It's pretty clever, but I'm not sure if it will work in an actual live competition environment.

At Worlds, they were running it over a Cellular Hotspot, that was OK, but fraught with the usual cellular access issues (power downs, dropouts, low batteries etc)
As a general App development too for learning App Inventor also seemed pretty cool. Applicable to summer tech camps etc.

Phil.

[CraigRochester]

Hi Phil,

Thank you for the thoughtful post. I'm working with a rookie team this year that struggled with RobotC configuring/programming last season. I'd like to have both platforms figured out so I can assist them on setting up one that works best for them. I am more comfortable with text based line programming as it's what I know, but the graphical App Inventor might be more approachable for beginner programmers. I understand what an SDK is for Java programming, but not sure what the equivalent is for App Inventor. Will there be "visual objects" made for talking to the controls electronics, and when/where will we find out about it?

Thanks again,

Craig

[Philbot]

Craig.

As an experienced programmer the 'Jigsaw style" syntax block of App Inventor will seem pretty natural to you. No significant learning curve.
In some respects it's a good primer for the kids. The blocks will only accept certain configurations (based on syntax).. eg you can only put a condition on an IF block...

Configuring motors etc with both platforms will be done by referring to the devices by name in your code, and then running a configuration app on the phone to assign those same names to the devices.
These Names are "checked" at run time, but currently there isn't a tool to link the code development process to the Phone configuration process, so we'll need to be good about being consistent in how we name things

I think the real issue with both the App inventor, and Android Studio is going to be autonomous modes that go beyond simple drive sequences. In both cases you will need to implement some kind of state machine to remember the auto sequence through multiple "loop" calls. I fear that the complexity of this may stretch what App Inventor was intended for.

Phil.

[Philbot]

BTW, I should have mentioned... you can download App Inventor NOW, and play with it without the FTC add ons.
It will creat apps, it just won't drive a robot

http://appinventor.mit.edu/explore/get-started.html

Phil.

[CraigRochester]

Thanks Phil,

Yes I've worked through setting up Android Studio & App Inventor. I've followed "hello world" tutorials for both and tested on the ZTE. My next step is to use ADB with Android Studio and try to get 2 phones talking through WiFi Direct. I've also gotten the Logitech F310 talking to the ZTE through the USB-OTG cable and now need to figure out the Android Studio programming stuff.

Your help much appreciated!

Craig

[Philbot]

Tom...

Thanks for doing the Google Hangout... There was some cool new info there.

Clearly some people could get questions through, but for the life of me I couldn't see how to do it.
On my Google Hangout page there was no chat box, and I couldn't see where to ask questions on the You-tube channel.

In anticipation of the next one, can some-one tell me how they asked a question?

Phil.

[JimInNJ]

Tom...

Thanks for doing the Google Hangout... There was some cool new info there.

Clearly some people could get questions through, but for the life of me I couldn't see how to do it.
On my Google Hangout page there was no chat box, and I couldn't see where to ask questions on the You-tube channel.

In anticipation of the next one, can some-one tell me how they asked a question?

Phil.

Yes, thanks Tom! I had the same problem with no chat box. Maybe next time!

[hexafraction]

Yes, thanks Tom! I had the same problem with no chat box. Maybe next time!

I think one needed to be signed into youtube and be on the youtube page (not the Google+ page) to post a question.