Spread sheet is looking healthy now guys
So I’ve been thinking of a way to organise this and have come up with a plausible way of contributing for each person, my rough proposal is:
1) We all discuss, design, thrash out the ideas for the rover online, shared folders, drop box etc to all share work and designs (will take a few weeks)
2) After a few weeks of everyone’s input on the design (how everything will work with each other) we will have an agreed final product – my key proposal is – make the rover modular, in that each person’s expertise area is utilised to the best in that they will make their particular module of the vehicle (much like Nasa contracts out different parts of their space vehicles)
3) Once all completed, all ship the parts to OCUK Rover Tech HQ for construction of the final product (I’m am happy to invite all who are interested to come to HQ for a day of fun construction and a few beers of course!)
4) The next idea I came up with is vehicle testing stage one – ill mount the physically finished rover on a stand in a spare room, hook up all the required computers to run it and create a VPN/Remote desktop to the systems, in addition the ‘master server’ I will hook up a HD IP camera with full and clear view of the rover from various angles. This way all the software guys can log into the system 24 hours a day and fine tune the rovers operational software (create, debug, experiment)……also they can control the rover of course starting its wheels turning, steering abilities, lower/raise masts and cameras on the rover and so on…….basically a live, real life online access zone for EVERYONE to be able to access.
5) Ill be happy to do any physical ‘real world’ changes to the rover….such as if a programmer requests to move from mains powered electric sources to the onboard power systems, happy to provide a environmentally controlled env, i.e. a fancy way of saying ill put a large fan in the room to try out wind turbines or ill install high watt lighting to test the solar panals.
6) Once this has been done (will take as long as it takes), I will make an indoor test environment in my garage, i.e. sand and rocks all over the floor so again everyone can remote log in and test the rover, try out the parts they constructed, of course ill make the rover accasable via the net/wifi for speed and also give options of engaging UHF / mobile phone connections. (im also happy to get a couple of mobile smart phones of everyones request, android, win phones etc, ill also take out a 3 mobile unlimited data contract and also pay for that)
7) For fun im also happy to ‘mount’ the rover on a stand as mentioned in point 4, but in a chest freezer with controllable water spray nozzels, i.e. a harsh environment to test in
8) Stage 3 of testing is putting the rover ‘in the field’ (literally
) in Snowdonia on private land (as mentioned I know the owner, it will be ok) – this will then be an operational long distance controlled rover if it all works.
9) We can either stop there or put it in a highly remote place in Snowdonia for a few days once we know it wont get stolen, I have some friends that regularly go into Snowdonia on a daily basis and will know of locations where no one really gets to.
How does all this sound? It gives an excellent testing environment through progressive stages of development and also allows everyone to get hands on, even if there 100’s of miles away.
EDIT: Also for the software (this is not my area of expertise so im sure you guys will think of a much better way of doing this!), but we could program it nice and simple perhaps, and enable minimal text msgs to be sent to the rover in addition to a 3G data connection. For example we could make commands such as
TR30,MF5
Which the rover could read as Turn Right 30 degrees Move Forward 5cm
Or
TL20,MB1
Which would make it turn left 20 degrees then move back 1cm
Or
MF3
Move forward 3 cm
How does that sound? Simple small commands, I suggest we make it with just one speed, not varying speeds, i.e. a low range motor with high torque and make it move say 1 mph at all times, so when it executes commands we know how fast it goes, or we could program in 2 speeds, L and H, low and high and code it,
What you guys think?