Category Archives: rpi

Kill Switch Pictures/Update

Hello All,

For those following along, I have moved Kill Switch, my sons e-vehicle project. To a permanent page.  I have also added a gallery for the work as I go.  Keep an eye…

You can also subscribe to my RSS if you like.

Thanks,
-M


P.S.

Thanks to TJUMP7 for the donated 4gb SD card, and help with the motor controllers!  I can’t wait to get all the parts and get it going!

Updates on Kill-Switch (E-Vehichle for son).

During my latest testing phase, there was an accident with the motor controller.  This has put a small speed bump in my little project.

However, this may be a blessing in disguise.  I wanted to put in my own motor controller before, but I was trying to do this build without purchasing much.  So, I was using the built-in controller within the old hover board housing.  This came with many obstacles; for one, the circuit was very sensitive to change.  If I wanted it to work; the LEDs and everything had to be perfect. Otherwise it would throw errors. Keeping in mind that I do not have any manual, documentation, etc on the hardware here.

Once I replace their motor controller with mine, it will be even better for my automation.  I actually do have RPI motor controller HATs; however nothing rated for 500w.  So I am going to be using the following per side. http://a.co/eHzWM2i

This will allow me to control the speed with the battery, and hub motors I already have. Just add a potentiometer per side, and were in business. Those pots will be controlled via very small servo.  This will allow the user to control them, but the servos will put them back to zero (stop) after use.  This also enables the control via RPI3, as I mentioned before.

On another note; I am considering using casters in the front since you will be able to steer via the controls.  Alternatively, I get one controller and use it as a throttle only.  This would work, but then I would have to have front steering.

 

Thanks for all the support,

Matt Curry

Handy One-Liners – Full Debian Update

This one is great for a “Full Update” on debian / ubuntu machines.

It calls the script without ever installing anything (assuming curl is installed).  Be sure to run as root, either with sudo or as root directly.

As you can see in the snippet; it uses a script that is remotely hosted (in a github gist).  This is great because you  can see exactly what it does by looking at the script.  It just calls system commands, so it can’t do anything malicious.  Just run sudo, then the above command and it will run the below script:

Another trick you can do with something like this, is copy it to  /usr/bin/fullupdate (as root of course), and ensure its executable “sudo chmod +x /usr/bin/fullupdate”.  Then you can call “sudo fullupdate”, from anywhere and use it when needed. Alternatively, you can use it on a cron to run on a schedule!  If you don’t want all the options, just download the script and change it for your liking.

 

Welcome to open source.

Got an Idea? Need Help? Raspberry PI prototyping!

Just another thing that I helping with lately.  If anyone need help with a new idea for a Raspberry PI, or IoT device message me.  I have been  through several POC’s (proof of concepts).

Keep in mind, if you are working on a new product; or sensitive information I keep all client info secret, and have no issues with an NDA.

  • Home Automation
  • Voice Recognition
  • Several TTS/STT Options
  • Custom Hardware
    • Integration with existing hardware
  • Custom Software
    • Custom Plugins/Adjustments
    • Coding
  • R&D on Subject Matter
    • Build
    • Test
    • Design
  • … and whatever else is needed …

Happy to just answer questions; or see what I can do to help.  Just contact me.

Building E-Vehicle/Robot for Son!

I am building a robot (named aptly: Kill Switch) from old parts I had laying around, and it is powered by hub motors from a ‘hover-board’.  The stats were pretty strong for small kids; so I am building a lot of safety into it.

This will include software, and hardware measures to ‘take over’ the device, and even limit speed.  Eventually I will be able to return him back to a certain spot with playtime is over.  I hope to automated charging as well eventually.  There are a lot of features I have ready; however I am still building out the hardware.

This can be difficult to do and keep extremely safe.  So for starters I am testing it only; and I have 2 kill switches I am putting in to ensure safety.  One the person will have to keep his foot on constantly for the buggy to run.  The other is a simple quick kill switch.  (Eventually these will be automated).

The Device already has an RPI3 with a small motor-controller for future automation’s.  This will control other aspects of the vehicle via software.  Such as speed limitations, power usage, GPS, WIFI, BT.  I will also be using a pico router to establish a LAN around the device.  This is for media, as the vehicle will have speakers/screen to watch/host media on the LAN.

Hardware Safety Features:

  • Dash Kill Switch
  • Foot Kill Switch
  • Flip/Tilt Sensor
  • Lights
  • Front
  • Rear

Once testing is completed, and it works; I will go through how I set it up.  However, this will be piece by piece as I do it.  I have even considered some youtube videos.  However, that will depend on my success in doing this on a budget.  I am also using completely reclaimed parts, minus a couple bolts I bought.  So its been free so far.

On that note, I have been building the chassis, but if anyone in the Dallas, TX area has an old go-cart frame that rolls/steers, I am looking.  I think it would make it a lot lighter.  Shoot me a message, info is on my contact me page.

 

MUCH More to come… Please keep an eye on the series…

-M

Don’t forget! Linux Learning Resources

This is kept under the Linux Learning Project and Learning Resources section of the site, and is updated occasionally with new links.  Feel free to suggest one by contacting me directly.


LEARNING RESOURCES

Help/Chat:

Resources:

The Eagle Has landed….

All,

I have made it…. the move is complete!   I just wanted to say thank you for everyone that has been waiting on me.  I know I have taken a while on a few things, and I am finally in a position to run with everything again.  I finally have a decent internet connection [330mbps/330mbps]; so I will also be able to host things at high speed for us now as well.

As far as the installer goes, I hope to be done very soon with it ;  I am putting my final touches on it for the Pixel desktop.  If I get time I might be able to get Bluetooth working!  However, I have to get caught up first.

For those waiting on hardware, most has been shipped with a few exceptions.  I have notified those people.  I have a true ‘shop’ area again, and this will allow me to be much more efficient.  Meaning shorter wait times/etc…

 

Sincerely,

-M

Thank you to all… Jasper v1.6 Image News!

First, I would like to say thank you to the community members for helping out. I have gotten a lot of input on the new image.  This has also given me better feel for what the community wanted in an image. Which leads me to the next bit of news.


Some of you are undoubtedly wondering why I have not released my Jasper v1.6 image as of yet.  Well, I can assure you there are very good reasons.

Firstly,  I have had some severe family/health issues come up as of late which take priority.  I am also in the middle of moving a family of 5.  Combine that with the other reasons below, and I feel that most will feel the wait to be worth it.

This leads me to the next bit of news, however shocking it may be.

  1.  There will be no version 1.6 image.
    1. There will be no image at all…
  2.  Instead, there will be a full installer.
    1. This is one of the reasons for the delay.
  3.   The installer will work with a full GUI, and on the desktop.
    1. Examples:
      1. Full ubuntu Install.
      2. Fresh RPI install with GUI.
  4. The installer will be iterated on by feature going forward.
    1. We can add community approved features one at a time.
      1. Example:
        1. Change Jaspers Name
        2. Change STT after setup
        3. Etc.

FAQ (COMING SOON)

  • So whats that mean for me?
  • What do I do if I am running Jasper v.15?
  • Where do I get the installer?
  • Do I need to upgrade?

 

Jasper Polling Results for Image v1.6

  • Results of the Polls:
  • Presetup profile.yml enabled
  • GUI packages will be left on the devices
    • Increasing Size Dramatically
    • Increasing Update Time Dramatically
  • Jasper will not be pre-installed
    • There will be an installer with options
    • Daemon off by default
  • Home Assistant will be pre-installed
    • Daemon off by default
    • Mosquito MQTT Server installed with it

 


Would you prefer to have the profile.yml presetup as in v1.5?
  • Yes: 9
  • No: 0
Do you want GUI option, even though its not suggested?
  • Yes: 5
  • No, it will break: 2
Should v1.6 Have Jasper Already Installed?
  • Yes:  2
  • No:  1
  • I want installer:  7
Should HomeAssistant be included in v1.6?
  • Yes:  4
  • No:  1
  • Whats that?:  1

A few BASH tips from an old Linux admin.

Everyone has seen these “Top 50 commands” blah blah blah….. #clickbait….

I am writing this just to make BASH a much more pleasant experience for people new and old to Linux.  It is also for any sysadmin that has simply not been introduced to some of them.

I could list tons of them, but that’s going to get a simple TL;DR for most people.  Then they will move on.  So I will list a few and lets let those digest.  Keep in mind all commands are in Linux, and may vary by distribution.

First BASH tips (Simple, but time savers):

  1.  Type ‘cd’ and you will go to your home directory for the user you are logged into.
    1. Similar to “cd” ~, however ~ can sometimes rely on the environment.
  2. To return to the previous directory you can type ” cd -“.
    1. This will return you to your previous location, not home.
  3. Type “tailf”, instead of “tail f” for the same results.
    1. Also, “tail -200” can be used instead of “tail -n 200”
  4. Use a custom “PS1” for root, and regular users.
    1. A “PS1” is the text in the login prompt. See Example to the right:
      1. Notice it is yellow
      2. Do the same but in red for root.
    2. Examples:
      1. Debian PS1 for a normal user (as seen to the right)
      2. Debian PS1 for a ROOT user.
        1. These will need to be added to the bottom of “.bashrc” in your home directory
        2. Keep in mind files starting with a . are hidden in Linux, but there.
          1. I also have MAC PS1’s public in my gists.

 

I think that is enough for today, I hope this helps make BASH your friend.

 

-M