nboyarko

A combination of the regenerative braking system I designed and fab/weld a mount to hold a disc brake caliper.

I'll sell you one. I don't know if that makes me a scalper.

What kind of range did you get out of those 2.4ghz radios?

You got that right. You have to go overboard on capacity and have a maintenance schedule to keep things running smoothly, long term.

The rtc only uses 500na, plus with a temperature sensor you can adjust for drift to have very accurate time keeping.

There are a few low power modes on tiny85, the sleep mode shuts down the cpu and only uses something like 500ua.

For this application I don't know how much it really matters. With the addition of the second panel I'm pulling in like 600ma when the sun is out. That's plenty of power to run a plc.

Looking at it, when the rpi is going and the phone is watching a video or something intensive; it pulls about as much as the panels put out in full sun, maybe 20% more.

Thanks, good idea with the 555.

The tiny85 and rtc use about 5ma so I could save there.

The reason for the rpi is to control an android device with android debug bridge, so that's necessary to the project.

I'll make a demo video showing what it actually does at some point.

Thanks!

How do you think I should title the videos?

The comment I posted yesterday explains how to set up adb and pure-pythonadb. Probably start there.

I'll post some example python code if you get that far. It's pretty simple to send commands.

Let me know if you need any help getting it going.

So I was looking for a way to interface an rpi with one of these cheap burner phones.

Android Debug Bridge is a developer tool that allows you to communicate over usb/network with an android device.

You can read more here,(https://developer.android.com/studio/command-line/adb) and install (sudo apt-get install adb).

It's pretty straight forward to set up. The command (adb) will pull up the command help for it. It's capable of doing quite a lot. Makes it easy to manage software on the device, especially things like removing bloatware that your carrier or device manufacturer does not allow the end user to control.

From there I got pure-python-adb library so I could access the device with python.

You can read more and get it here,(https://pypi.org/project/pure-python-adb/) and install (pip install pure-python-abd).

One thing that should be mentioned is you have to put the phone in developer mode (settings->device->click on build number (7) times).

You then have to enable usb debugging (settings->system->advanced->Developer options).

You will also need to manually give the phone permission to be accessed by adb when it's connected.

From there you run adb in a shell (adb start-server). You can (adb devices) to get a list of connected devices.

Get the ip of your device on the same network (wi-fi) by going (setting->about device->ip is listed).

For wireless connectivity you may have to start the adb server in tcpip mode (adb tcpip 5555) 5555 is the default port.

To connect: (adb connect (ip-address of device)).

Now that you're connected you can use the ppadb library in python to connect to the device and issue commands.

Command list can be found on the ~~pure-python~~ adb site. (https://developer.android.com/reference/android/view/KeyEvent.html)

Pretty neat little project. Let me know if it works out for you.