Hrrmm…
You aren’t going to be seeing too many programming examples for the biped and extra sensors for a while, since it just came out a little while ago.
GPS programming would be very tricky with a biped.
I’m pretty sure that most GPS systems would be way too heavy for a biped to carry, but you may be able to find a small one.
As to programming examples for GPS’s, I haven’t stumbled across any.
For the basic sensors (i.e. thermocouples, Ping sensors, photoresistors), you can find them quite easily.
The only problem is, all the ones that I’ve seen have been written for microcontrollers’ specific programming languages.
So, before you go looking for examples, you’ll need to decide how you’ll control your bot (the SSC-32 is only a servo controller, not a microcontroller; you need a microcontroller (or computer) to have autonomous behavior).
If you search these forums, you’ll find our discussions on the pros and cons of each microcontroller.
In brief, go with the Parallax Stamps if you want simplicity and lots of help, go with the BasicX microcontrollers if you want sheer processing speed, or go with the Atom Pro if you want a bit of both.
The other two options are to either put a small CPU on the bot itself, or to put a wireless network module (Bluetooth, Wiport [wibotics.com], etc.) and use a PC as the brain (a.k.a. telemetry).
The precursor has weight and power consumption issues, and the latter has network latency (wireless communication is slow, compared to CPU’s and microcontrollers) and slight power consumption issues.
Once you’ve decided that, you can go to the respective site and download their user manuals (I know that Parallax let’s you download their code examples and their manuals for free, but I’m not sure about the others).
If you go the microcontroller route, you’ll have a much easier time programming, as there are many examples and many people to ask questions from.
If you go the network/CPU route, you’ll find that it’s less so.
Personally, I’m going to be using an SSC-32 to move the servos, a Basic Stamp 2px to control that movement and to correct the balance with the pressure sensor data, a WiPort module to tell my laptop (and myself, of course) what’s going on, and my laptop to give overall directions to the microcontroller (i.e. “move foreward” and “go fetch me a beer, slave!”).
Keep in mind that more sensors will mean more current drawn, which will mean bigger and heavier batteries.
Typically, the smaller the piece of electronics and the less work that it does, the less current it will normally draw.
So, you can expect an onboard CPU to draw much more current than, say, a temperature sensor.
Instead of using NiCad batteries, you can go with the lighter NiMh, or the even lighter Lithiums.
Of course, that’ll mean more expense, but it’ll be necessary if you want your biped to survive a recon mission (let’s say two hours?).
To give you an idea, I was going through a pack of 6-cell NiMh’s every 45 minutes on my Biped Scout (the Humanoid has 5-6 more servos than the Scout’s 12 servos).
In all honesty, I’d seriously think about not using a biped for the kind of “missions” that you’ve described, if I were you.
You can get much better speed, survival time, GPS accuracy, yadda yadda yadda, with a rover.
If you’re thinking that a biped could successfully navigate over things that a rover can’t step over, you may be right.
However, you can easily modify a rover to be able to climb stairs, even, without nearly the hassle that you’ll have making a biped do it.
Hope this helps.