Reddit user creates multi boot images to simplify trying out various combinations of installs targeted for RPi. Bookmarking for future. Link http://www.multibootpi.com/
Via Reddit >>
Have been struggling a lot with unreliable WiFi and more recently not being able to reconnect to router even after rebooting. Since the Octopi runs purely in headless mode I always suspected WiFi signal strength issues to be the cause for OctoPi going off my network and not being able to reconnect.
This is after trying to resolve signal coverage and strength issues by getting a signal extender which improved coverage and signal quality.
Connected to a monitor to troubleshoot.
Got a warning
fsck: Warning... fsck.vfat for device /dev/mmcblk0p1 exited with signal 6. fsck died with exit status 8
Went into a rabbit hole of googling sd card errors and recovery procedures till I came across a forum posting where someone just mounted the sdcard on a windows machine and fixed the problem automagically. Guess what I do have a Win 8.1 machine. No harm in trying. As soon as the sd card was mounted windows detected that there was something wrong with it and graciously offered to fix it. Took the fixed card back to RPi and waited with a bated breath for it to boot up. To my surprise it booted up perfectly with no errors. So here is another anecdotal evidence supporting the automagical sd card healing properties of Windows.
But the elation was short lived. Got the omnius Rainbow Square on top right. Not steady but pulsating.
The warnings could be triggered both by power supply and usb cable.
So if you are running headless (which is usual with Octoprint) you have no way of knowing about the under voltage issue. Mike Redrobe has a solution to monitor this remotely.
I am suspecting the microUSB cable (microcenter) which works well for charging my umpteen other devices but somehow fails here. The only other device connected is the Edimax wireless dongle and RaspberryPi Camera.
Flaky WiFi issues still persist. Trying this to see if it would remedy the issue.
ssh into your pi (or use a monitor and keyboard :-))
then type the following (or copy paste it):mv /etc/ifplugd/action.d/ifupdown /etc/ifplugd/action.d/ifupdown.original ln -s /etc/wpa_supplicant/ifupdown.sh /etc/ifplugd/action.d/ifupdown
1. SSH to your RPi using either Terminal or an utility like Cyberduck with username of “pi” (if you haven’t changed the default username) and your password.
2. Then enter following commands:
cd /root/bin sudo nano webcamd
3. Then look for the following entry
4. Comment out the existing line in case you would like to revert back the
changes. x & y options give the resolution. The RPi camera can do 1080p30
but 720p is good enough for me.
camera_raspi_options="-fps 10 -x 1280 -y 720"
5. Press Ctrl + O, Enter to save and then Ctrl + X to exit
6. Reboot with:
The Wifi disconnect issue continues to despite the earlier fix to prevent power management from shutting down the adapter. The issue seems to be more around signal strength rather than either power supply issue since it is powered by a 2A brick. Others have handled it by running a job in the background every so often checking of the WLAN connection is up or if the Pi can access Internet. If not then they bring down the Wlan interface and bring it up again. This reestablishes the WiFI connection. This is kludgy workaround since the the system should reconnect automatically.
Since this is how others have fixed this, will attempt to use this solution with my Octopi.
The OctoPi install does not keep WiFi connection. Tried multiple times with different placements. The issue seems to be signal strength with the Pi adapter shutting down if there is not enough signal strength. I suspected lack of activity based on other users reporting similar issues. The other reason cited seems to be insufficient power supply issues. But that was ruled out by trying different wall warts with same disconnection issue persisting. Only time the Pi kept the connection for a length of time is when it was close to the router.
Printing workflow works well with PrintrBot connected to the laptop but the laptop gets tied up for the duration. Also the printing stops if the laptop goes to sleep.
You can print untethered with PrintrBot by using the sdcard but it is an hassle to switch sdcards and copying the sliced files. KeepingYouAwake, a Caffeine clone works very well in a pinch to prevent the laptop from sleeping.
While not exactly untethered since it will still be connected to Raspberry Pi, want to explore Octoprint on Raspberry Pi. Have one RPi2’s lying around. Should be perfect for this.
OctoPrint developed by @foosel is a complete 3D Printing host solution. Open sourced and extensible it has matured very well. There are many guides to setup OctoPrint on RPi so I would not go in detail here.
There is also AstroPrint forked from Octoprint but moving most of the functionality to the web including slicing. The workflow setup works in conjunction with AstroBox which connects to their cloud service which acts as a remote host. This would work very well for multiple printer setups (one can dream!). The AstroBox can be self configured on a RPi.
Setting up RPi for OctoPrint.
PrintrBot upgrades for OctoPI.
While RPi setup goes on search for PrintrBot addons for OctoPrint.
Customizing the OctoPi:
There are lot of plugins available for OctoPrint.
Customizing the RPi installation.
Install webmin, a web based Linux system administration utility that provides for most of the system adminitartion tasks via web interface.
Microsoft announces end of support for Intel Galileo. I still have to open the box and it is already obsolete !!
Raspberry Pi seems to be platform of choice going forward.
Support for Windows on Intel Galileo Gen 1 and Gen 2 will end on November 30, 2015
As we continue to focus on providing a great experience for Makers with Windows 10 IoT Core, we’ve made the difficult decision to discontinue Windows support on the Galileo platform. We’ve seen some fantastic innovation with the platform, but unfortunately, it does not meet the minimum hardware requirements for Windows 10 IoT Core. Please click here to learn more.
Source: Windows IoT – Home
For anything more than simple tasks on Linux and Unix based systems you frequently have to dip into shell scripting especially if they are repetitive and need careful attention to detail to ensure the commands are executed in right sequence and with right options.
For RPi, every time I have a new project to try or trying new packages, it is essential to create repeatable environments which mainly rely on execution of certain commands. I find that you end up with multiple shell scripts that float around and after a few months you don’t remember why they were created in first place.
Was looking for a solution to organize my shell scripts that are easy to create and can use templates.
Searching ended up with this list compiled by Donnie Berholtz.
Of the list I think rerun is the best. It is easily understandable and creates docs on the fly. Has built-in testing framework that facilitates building of unit tests right from the start. Whats not to like?. Surprised that it does not have more followers.
This post is a great intro on using rerun in a non trivial environment and demonstrates conceptual thinking and workflow behind using the framework.
More info on rerun here >> Source: rerun: Dance your way through standard operating procedure