With Instructables you can share what you make with the world, and tap into an ever-growing community of creative experts.
Strange, I just looked at the code and the default units were already metric. On 62 you should have: disp_units = "metric" This should take care of displaying the degree C symbol for you.To display degree C or degree F I'm using a single unichar character. So, for example, the degree F one character that is both the little open dot plus the F character. It was a cute programming trick, using unichar, that I now regret. Makes it hard to understand the code.Anyway, if you set the "disp_unit" variable to the string "metric" then near lines 60 to 78 should take care of setting up the correct unichar symbol for metric. Hope that helps,Jim
At one point I added a push button to cause the Pi to go into shutdown mode. The idea was to shutdown before yanking the power so the SDCard doesn't get corrupted. Well, I stop using the switch long ago and the power gets yanked all the time with any trouble.So, I'm guessing your GPIO is causing the Pi to think you want to shutdown. Simple answer is to just hack the Python code to disable that feature.
Hometownnerd, thanks for your comments. Yeah, sounds like pygame is getting confused as to the screen resolution. Setting xmax and ymax to different values should have an effect. Try different values until thing look right.Good Luck,Jim
Should not be too hard. There is already a way to flip the default units to metric. Look near the top of the source code. There are comments that describe how to change the units. For all the rest, just search through the source code file to find all the English words and replace them with your preferred language. Should be really easy. You can't hurt anything so just go for it and make the changes. Worst case, the new language might not fit. However, with enough effort you should be able to abbreviate or otherwise shorten things to make them fit. Good Luck, Jim
Can you copy the actual error messages and copy them into a reply to your message? Honestly, I have no idea what a "failed to add edge detection line 710" means. Basically, we need the actual complete error message to be able to provide any help.
Well, I'm still seeing lock ups at times. Seems like the display will run for days and days - weeks and weeks sometimes. Then, I get into cycles where I have to cycle the power once a day. And that will go on for days. Then I'll be good again. Super hard to diagnose as a standalone app. I guess some kinda file system logging could be done.But I'm pretty sure the problem relates to the weather api call. I think it gets stuck on the line that calls the weather api.That call should be wrapped in a separate task so the main task can continue even if the weather api code dies. But alas, no time no time. Seems easier to cycle the power for now. Well, until the Pi file system goes corrupt again with all the power cycles, that is.What we need here is a fresh volunteer python wiz.
Raspberry Pi Internet Weather Station
How to Build your Everything Really Really Fast
Design & Print Wind Turbine Blades.
Creating Illuminated 3D Objects with a Laser Cutter
Simple Guide to Making Sprockets
Accelerometer & Gyro Tutorial
Universal lamp shade polygon building kit
How to build a self navigating Robot
How to reverse engineer a schematic from a circuit board
The "Reverse Joule Thief" Battery Charger
Easy to Build Desk Top 3 Axis CNC Milling Machine
Color Changing Digital PC Fan Controller
LED-Paper Craft Lamps
10 $ WIFI 16dBi Super Antenna Pictorial
Solarize your backpack and power all your gizmos
Let your inbox help you discover our best projects, classes, and contests. Instructables will help you learn how to make anything!
© 2016 Autodesk, Inc.