Dimitris Platis

Hi, you'll need at least one.

Looks awesome! :)

Sure, why not!

I guess you can but you might need adjustments since it has been a long time since and you'll have to use a stronger power source.

It has been a while since I wrote this, so it's possible that things have changed in the meanwhile. What do you mean by not clearing wpa_supplicant.conf? Have you not commented it out in the interfaces file?

What report are you talking about?

Then it might be possible, yes.

Hi,You would need to debug this and figure out what might be failing. The error message does not give much to go on.

Hi,Any recent version will do. Your problem is most definitely NOT with the version. What have you made exactly? What is your setup?Please try to explained with as many details (pictures, print screens etc) as possible, otherwise it is impossible for me to understand what can be going wrong.Also, as I mention in the instructable, this is not an application that I personally made, so I am not 100% familiar with the code.

I haven't used the MIT App Inventor a lot, but unless there is a way to "draw" stuff on the screen and be able to process the drawn path, no.

Hi,Which part of the app are you referring to?

Maybe something has changed in the API for the GPIOs since then. Try just turning the light on however they do this nowadays and then it will be a piece of cake modifying the script. :)

Are you trying to run exactly the same code?

Its path following features cannot work out of the box, as every car will be different. Can you describe what doesn't work?

Thanks! :)

:)

This error unfortunately does not give much to go on. I would suggest that you try to compile the application yourself and see what is the error exactly!

There can be too many reasons for an error. I'd need more information, such as, is the Bluetooth turned on and has it paired with the device already (outside the app)?

Nice! Does it work as expected too? :D

I've tried this with iPhones as well. They work just as fine. So now you know how to do this! :)

I'm glad that I helped! :)

Well, whatever works... Try also different IR transmitters. Maybe some other are more consistent. By the way, you can decrease the size of your "cases" by doing this: (for the right arrow)<pre>case 16607383:case 21871754:case 975146095:case 2246090081:case 2292190138:case 2321333080:case 2844203703: Keyboard.press(KEY_RIGHT_ARROW); break;</pre>

Well, whatever works... Try also different IR transmitters. Maybe some other are more consistent.By the way, you can drastically decrease the lines of your code by doing this: (in this case for the right arrow and similarly for the rest)case 16607383:case 21871754:case 975146095:case 2246090081:case 2292190138:case 2321333080:case 2844203703:Keyboard.press(KEY_RIGHT_ARROW);break;Also, I'd also suggest adding some small delays (e.g. 20 ms) between sending the keystroke, releasing it and continuing, so to give the system some "breathing" time. Hopefully the consistency might get improved that way as well.

Your problem seems sort of irrelevant to the specific project indeed. Can you do a sanity check and verify you can receive strings from the Arduino? Are you using the same code as the one posted here?

Hi, I am glad you got it (kinda) working!Regarding the "rolling" values, I don't think I had that problem myself, even though I don't always get a 100% consistent value. However using the "most common one" like you did, works well enough.I have not noticed the "drifting" after you stop sending an IR signal. It sounds really strange. This could always be a hardware issue, so try it with a different remote control if possible.However, this sounds awfully lot like a code bug. Have you verified that you are actually receiving the same value over and over instead of just forgetting to release the key/mouse after you are done with it? To put it simply, are you using the resume() and the releaseAll() functions in the appropriate section of your code?

You can pledge for it on Kickstarter!

Hi Drougni,From what I see, the new motorshield from Adafruit works via I2C. You could in theory edit my (old) libraries, but I would suggest that you use Adafruit's library for moving the car.For the rest (rotating with the gyroscope and traveling specific distances with the speed encoders) I would suggest my newest library (Smartcar shield), which works in a very similar (and improved) way.

Hmmm, as the speed encoder measures distances it is crucial for the general functionality of the vehicle.A work around would be to experimentally determine how much time the car needs to move X centimeters. Therefore when the car needs to move 50 centimeters, instead of using the encoder to get the travelled distance you would move the car for a specified amount of time.

It is used to calculate the distance that is travelled by the vehicle.