So I bought one of these.
What do I do now? I'm a guy without any imagination, so I need some help deciding what I should do with it.
>Small computer to just dick around
I sent mine into stratosphere using a High-altitude balloon. Since you cannot use GSM and GPS above certain altitudes, it made things a lot harder.
long story short - I sent 500$ into space to never see or hear of them again.
also raspi is shit. its too slow for errything so hf
Try out a XBMC media center.
It's super easy to install, get a remote app as well, use it for some time to see if you like it.
Since the raspberry is pretty weak, use a minimal theme or keep in mind that a decent htpc will be much faster. Then decide if you like it, buy an htpc and set up a proper media center.
Then move on to the next thing.
This is what I'm doing with my raspberry, seeing if I like something, then if I do buy a proper machine to run it on. It's great, because it can try a dedicated machine for something before buying one and possibly wasting money. Without trying xbmc on my rpi, I would never have bought an actual htpc.
>What do I do now?
Write a shitposting bot that responds to certain keywords (for example "Linux" without "GNU+" in front of it) and leave it running until you can think of a real use for it
because blogs. fucking internet shills telling you how great and revolutionary some piece of hardware is and writing tutorials that look good on 1st reading, but actually suck when you have already bought the hardware and are tryin to do something useful.
i have a lot of friends who are asking me if they should buy a raspberry pi...some already have and ask me what to do with them...
its difficult for me to hold back my laughter when people tell me how excited they are about the 'future' of computing with the rpi.
You throw it away
Then you get a Launchpad
Then you enroll in a real embedded systems class instead of using what's supposed to be an embedded platform as an underpowered desktop.
Ah, that's the revised version that will begin in the coming January.
Looks like the old version was deleted from the database. I'm being told they're offering a bit more introduction into C, but can't verify.
Anyway, to give a rough idea, here's a youtube video demonstrating all the projects you will build as part of the class.
Conveniently, all the video lectures from the edx class are on that youtube account as well.
Here's the HTML Formatted book used for the class. The cable of contents should give you an idea what you'll be learning about:
why for not supporting the raspberry pi? the platform is more a social movement than technological movement, and everybody knows it. the fact that it even sells for under $50 is because it is relentlessly advertised and blogged about, driving techie types to buy one. in reality it is just an old SoC in a small package with a community (see, social movement) of people to support it.
the sales of the fucking thing is driven my hopes and dreams of a prefect htpc, or emulation platforms, drawn up by bloggers and vloggers hoping to cash in on the fad. the sad reality is that people are drawn to the low price and pay in, only to realize the the linux CLI is difficult, or linux DE are different, or the emulation of chrono trigger isn't quiet 100%, more like 90% and the whole experience is just a let down.
i can count on two hands the friends of mine who have fallen for this stupid overrated platform and now have an unused rpi sitting in a box somewhere.
Without knowing how familiar you are with electronics design, that's actually a very difficult question to answer.
After some thought, I figure the best way I can answer this is in a tl;dr fashion is: "Can you read and intimately understand a datasheet? If so, then use whatever microcontroller you like!"
So, in the interest of full disclosure:
I have not taken the UT6.01x edX class.
I am an ECE student at UTexas Austin, and took EE319k (Introduction to Embedded Systems) under Dr. Valvano two years ago.
A cursory glance at the labs video and ebook chapter names indicates that UT6.01x and UT6.02x are largely the same material as UTexas Austin's EE319k. I made a B in 319k with a Lab partner that did quite literally none of the work, he switched majors to Computer Science the next semester.
I've never even seen a microcontroller in my life but whole area is interesting and i would like to go into that
I have no idea what datasheet is, is that some manual how to connect stuff to that breadboard?
Here's my own rpi.
Currently running as a NAS server but soon it will be owncloud server.
Anyway mostly used it to download porn. Where it's pretty good at.
Yes, technically you can use any microcontroller you like, but I would highly suggest you be intimately aware of what the differences are.
For example, I'm going to assume you're asking that question because you've got an Arduino somewhere you'd like to use instead of the TI ARM Launchpad.
I'd highly suggest against any non-Due models of Arduino:
-Arduino uses 5V signalling, Launchpad (any ARM chip, really) uses 3.3V, if you don't know what this means for circuit building, you can cause explosions (Small ones, but you can destroy or melt components).
-Arduino uses an AVR architecture-based chip, Launchpad uses ARM. I call this relevant because when I took EE319k, they started by teaching us how to program in ARM assembly language, instead of C, and eventually transitioned into C.
I would say depending on your experience level, you could go about your microcontroller choice for the class three ways:
Beginner: Just get the Tiva Launchpad.
Intermediate: Any microcontroller with an ARM Cortex M4 core should be viable. (TI Tiva Launchpad, Arduino DUE (and ONLY THE DUE), STM Nucleo)
Advanced: Pick your favorite...but then why do you need an intro to embedded course?
>I have no idea what a datasheet is.
A datasheet is pretty much an engineer's bible when it comes to working with a component. It will tell you quite literally everything you will ever need to know about a given component. (cont)
To continue talking about datasheets, please don't let what I'm about to post scare you away from getting into embedded. But...
For example, here's the datasheet for the chip used in the TI Tiva Launchpad:
One look at the page number should tell you how much information there is.
By comparison here is the datasheet for the ATMega328, the chip used in the Arduino UNO.
even things as weirdly innocuous as your average through-hole resistor has a datasheet in case you REALLY need to know the actual electrical properties down to the most minute detail
what? I bought 3 raspis, one of them is a $35 xbmc machine that performs perfectly (AFAIK the chip is quite good at 2d video), one for an emu machine in work which its well capable of and one for screwing around with servos and stuff. it does sound like plenty of buyer's remorse here from people with zero imagination in which case feel free to send them to me
I bought one, then returned it because they're fucking worthless if you need to use the GPU. They have zero driver support, meaning you cannot even really use the GPU for anything. If all you need is CPU and RAM, then sure I guess, go ahead.
Even compiling VLC was a huge pain in the ass. I was excited to potentially be able to play a bunch of games that the rpi couldn't handle, but fuckin nope, no video works whatsoever.
There's also a common issue where if you have it plugged into a TV (via HDMI or RCA), the image gets cut off (overscan). So you end up with a bunch of stuff offscreen. The Rpi has a fix for this, but the Bananapi does not.
As the other guy said, the processing power is great on it, but God forbid you try to use it for anything else.
Small-scale building automation system
Use Ethernet or RS485 as a bus
I'm pretty sure that the Chinese made GPS which advertised to have no limitations for hobbyist aerospace use worked pretty fine.
Which didn't work out was communication. GPS data is useless if I don't know where my balloon is because I can't receive anything.
I put a failsafe mechanism there so the preloaded SIM card would be put in roaming mode and would try to phone home(ayyy lmao) when it landed or got into coverage.
Entirely self-sustainable is a little outside the scope, but basically we're competing in the Solar Decathlon run by the Department of Energy.
Here's the rubrick by which our house will be judged.
I'm on the hardware design team for all the smart home/home automation systems.
Without going too far into details, since I'm not sure how much I want to give away for the sake of competition, it will be built on a BeagleBone Black as a server communicating to a network of MSP430 Launchpads.
We actually got a pretty big sponsorship recently who said they will match the results of our fundraising campaign, and I just checked my emails and noticed I have an open job application with them.
hm, that seems interesting
is there any limit how big the house can/should be?
any power limit that the house will use?
can you reveal what sources of renewable energy you plan to use? solar/wind?
>is there any limit how big the house can/should be?
I don't _think_ so.
I just checked the contest categories that would seem to cover that as a rule, but didn't find any mention, but that's a question better posed to one of the people on our architectural team, and I'm not aware if any of them are anons.
>any power limit that the house will use?
tl;dr, we get 50 points for _producing_ more energy than we _consume_, another 50 points for keeping total energy consumption under 175kWh during the judging process.
>can you reveal what sources of renewable energy you plan to use? solar/wind?
I'm not part of the power team, and I'm not sure I can reveal that even if I could.
Though I think the contest limits us to solar only.
>Why MSP430? Why limit yourself to old underpowered architecture?
See: Energy consumption contest.
>is there any money limit for each team?
tl;dr we get 100 points for keeping the total construction cost under $250k
Note the use of the word construction cost. I don't think that applies to design phase, could be wrong.
That's initial designs, admittedly.
If it comes down to it, I've got both Tiva and MSP430 Launchpads and a multimeter. Nothing keeping me from just measuring current draw during prototyping.
>how big is your team? i guess it's huge, at least 20 people?
Do you mean the whole NexusHaus project, the Smart Home Team, or hardware/circuit/embedded design?
The team is still acquiring members and some are rotating in/out.
I don't know if I can give out actual numbers, but if 20 is your definition of "huge" we are tiny.
>how long have you been working on this, any progress so far?
I've been involved since the beginning of the Fall semester. We've knocked out basic system architecture (BeagleBone + MSP430's) and server/client communications as well as a good number of hardware/component choices.
I've got a few KiCAD pages of circuit designs for key structures, but haven't had a chance to acquire prototyping equipment.
That's a power team question. It sounds like a reasonable assumption. Though I will be working in the systems to measure our power draw, which will be provided by one of our sponsors.
>If it comes down to it, I've got both Tiva and MSP430 Launchpads and a multimeter. Nothing keeping me from just measuring current draw during prototyping.
But the point is that ARM can sleep more time, it draws more current when it's awake. Also, it's a lot more fun to hack every single bit of performance from highly functional controller with lots of memory. On the other hand, I don't know your design, maybe MSP430 is really more suitable, I haven't coded for it, only studied a bit and it looked too unsophisticated and boring like AVR.
I despise Pi and similar boards though, I think they are overly complicated for embedding, they are fun for what they're intended to be used though, i.e. showing people that small board with reasonable power consumption can easily beat the shit out of old desktop computers.
>But the point is that ARM can sleep more time, it draws more current when it's awake.
Pic related disagrees with that statement. Though I'd rather do my own testing for power consumption. When it comes down to it it'll be testing and prototyping that determines which architecture I really go with.
Sourced from http://www.embedded.com/electronics-blogs/industry-comment/4026838/TI-s-MSP430-vs-ST-Microelectronics-ARM-Cortex-based-processor-for-battery-powered-apps
>I despise Pi and similar boards though, I think they are overly complicated for embedding
I dunno, I think it's fine for something properly complex like if you want to get into robotics, or for what I'm doing, which is essentially acting as the central server hub for the whole network.
I remember overhearing this one guy telling another about his senior design project where he made some sort of uav. a few weeks before showcasing he did a final test and the uav went out of range and flew straight for miles. he ended up losing his entire project because he forgot to implement a failsafe.
You know what? I owe you an apology.
It's early, and I think I misread your statement.
Though when you mentioned that the ARM can sleep for "more time" do you mean for more clock cycles or time measured in actual time? Because that sounds weird to me.
I guess what you might be saying is that since the ARM Cortex Mx's are faster processors, they spend less time in awake mode, thus allowing them to get back to sleep mode much quicker. This makes a certain amount of sense. Let me do some quick and public math.
Assuming that we can measure task completion speed via the system clock (we really can't, but good enough for gov't work) then the STM32F10 is 4.5x faster than the MSP430F26[...]
sometimes you need a failsafe for a failsafe. if I had an amateur radio operator license, I would have been able to implement a beacon of sort that could be picked up by other hobbyists... but where I live, in order to obtain an amateur radio operator license, you have to pass an exam consisting of excessive theory and Morse code. there is NO way I would spend time to teach myself how to read 40wpm using Morse for a little hobby project.
failsafe mechanisms need to be super simple and stupid. if it was invented after 1950, it's not a failsafe mechanism
>Pic related disagrees with that statement.
I didn't imply that it draws same or less current in sleep mode, I've just said that it can sleep more time because the same task would be executed way faster and it's nicer to code for. Also they have better performance per current drawn (pic related, though I'd take it with a grain of salt)
Assuming a task takes one hour (work with me) on the MSP430, then that means it should only take 0.22 hours on the ARM.
Assuming then that the ARM can spend the rest of that hour in sleep mode...
So: 365uA * 1hr = 0.365 mAh (MSP430)
8000uA * 0.22hr + 2.8uA * 0.78hr = 1.762 mAh (ARM)
Though I'm open to suggestions about better algorithms for estimating power consumption, I am a little tired and I'm not quite functioning at 100%.
I think the time it takes to formulate a reasonable argument is causing us both to argue past each other a bit, ha!
Yeah, I apologized for misreading your argument, see >>45279395 and >>45279463
Also, have we effectively hijacked a "NEED RASPI PROJEKT!" thread and turned it into a proper /embed/ thread? Fuck yeah for that!
Well, let's assume that ST has 4 times more performance per current drawn than MSP, then if it draws 8 mA vs 0.365 mA it performs a task 4*8000/365=88 times faster than MSP.
If ST is 22 times faster then it will draw the same power as MSP per hour.
I think it is quite reasonable to assume that ST has at least as much performance per current drawn in real practice in which case it's 22 times faster. Interesting...
Well, that is another way to look at it.
Thanks for the info, will definitely take it into consideration here pretty soon once things start ramping up and I need to start prototyping.
Hate to dash during the conversation, but I've got another senior design project I'm working on, and we do our open house presentation on Monday, so this weekend is going to be real busy for us.
(If you happen to be a UT Austin student, we're the Biopsy Needle Tracker team).
I have two questions about configuring the /etc/network/interfaces
1. How can you give rPi a fixed LAN address ? I have to borrow a monitor next door, do something, plug it back in my room router then use ssh from my personal computer.
2. My dorm uses a PEAP network from university. How can I made it automatically connect wired to a router when booting up, with all the shits about authentication be dealt with ?
I'm setting up a torrent box + NAS if that helps.
Also I tried looking up rPi IP using nmap/NetCut but they return the whole dormitory's IP.
Get into home automation. I'm gonna 3d print some solenoids housings that I can attach to some of the light switches and the heating control in my apartment. I'm going to power those solenoids with long ethernet cords that are all connected to the gpio pins on my pi. It's a super fun project, I just hate waiting for everything in the mail.
dual-core 1GHz CPU, 1GB RAM, 100Mbit Ethernet, about $60-$70.
If thats too weak, take a look at some of the WandBoards. The WandBoard Quad has quad-core CPU, 2GB RAM, SATA, and gigabit Ethernet, but is like $140; worth it in my opinion
Are you suggesting something like this ?
( PC + rPI) -> ownrouter -> dorm router
I thought about that but prefer not to spend more money if I can, if no good+cheap router available I might better get an adafruit screen.
I think the network would still require PEAP authentication, and that's what I want to avoid doing on a headless rPi.
>Is one π enough for these three tasks?
>And can it handle an external harddrive without its own power supply?
I bought a PI, used it for quite some time, realized that its shit setup an old pc as a dedicated server box. can do so much more now.