If this is your first visit, be sure to check out the FAQ. You may have to register
before you can post: click the register link above to proceed. Please email info@fightingrobots.co.uk if you have any questions.
original prodigy chassis that finished 3rd at uk champs has been stripped and binned.
new spinner is currently being converted 2 single tooth with robochallenge, a friend is having that,
Clusterbot and Kahn will probably live on the shelf in the garage incase i want to bring them out one day in 2009.
will be having a sort out mind, got some sabertooth 25a controllers, psu, pro peak chargers x 2, will b on ebay one day, when i get round to sorting it all out (sold as job lot). (no emails please, havent got time at the mo), will post on for sale section.
set up a company supplying promotional robots, for advertising and educational purposes (bit of fun and if i can earn a little then great) also used for fundraising etc... we have 1 suit, 1 fully working robot, 1 being stripped and started again (should be finished in 4 weeks), currently awaiting some cnc work to be completed. once we are fully up and running will put on some pics and stuff, more details.
With regards to the tech check day I have made a website that is password protected, and it can form an online tech check reports database for all event organisers.
The intention of this database is to provide all event organisers and their technical crew in particular with information on previous tech check reports from different event organisers. This way tech checkers will know what to look out for when a particular robot attends their event when it hasnt been to one of yours before. All information is shared in strict confidence and is for use of the FRA Event organisers only.
Basically you can look up robots in the database, add reports to it, or create new robot entries. If there has been a historie of to be improved or failed techchecks, they will be easy to spot.
It has an export function, so you can take the data with you to the venue before you leave.
Of course I will not force anyone to use it, but I can see the value of a system like that and I hope others will do too. The big benefit is that normally you would not see the tech check results of other EOs and they might find something you missed or vice versa.
Those that I havent spoken to about this, you can contact me via email at leo@computerclub.nl so I can provide you with a username and password. If only just to take a look.
You dont need permission as there is no personal data - The comment made was false.
This is purely for event organisers - it also states on our signup pages and most others that to signup you must agree to be used for advertisment or websites.
I completely read over this this morning. Although I do not believe that the Data Protection Act is applicable directly, I still agree that asking permission is the right thing to do. You are placing information about an item someone can be traced back to online, even if it is behind a password protected site.
Also in accordance with the Data Protection Act if someone wants to see if his/her robot is in the database, all they need to do is contact me and I will provide that info of course. If someone refuses to have their robot in that database for whatever reason that we will abide by as well. This database is a tool to be used by the event organisers to improve overall safety, not a point for legal issues to derive from.
Iknow, but my point was that roboteers agree to be used in things like this when they sign up for the events. They tick the box(s) in the signup page - this then gives permission to use just their robot in databases such as this and the robot database on RR/Tony booths and others websites.
Given this is strictly for no other reasons other than safety at events, i wouldnt be happy to allow a team to run unless they were willing to be on the database. It should be part of the FRA membership maybe?
cant see anyone having a problem with this, if people are offended then they should get there robot to fit in with the rules
wouldnt mind seeing a screen shot of what the database looks like and what information is in there? just to be nosey :P
also i think if there are robots which have problems then i think they should be contacted and reminded of the problems as when were not at events the robots hardly get touched as theres not enough time to sort them and sometimes forget to sort some problems out
@lj: Well thats up to the event organisers of course. If someone registers for their event, a simple lookup will show if there was a problem in the past and a friendly reminder could be sent.
I dont think it is a problem, Ive so far not had a single question about what is put into it.
So no email addresses, phone numbers, adresses, names of persons whatsoever. I would have left out teamnames and countries if I could but I know some robotnames are double, 1 in a country, 1 in another country for instance.
i cant see a problem as there is now a massive database under construction on the roaming robots site. if your robots on there then why not the tech checkers. personally i think its a good idea.
i wouldnt be happy to allow a team to run unless they were willing to be on the database.
That is the start of the slippery slope James. If this is something that you intend to introduce as a condition of attendance I think you will be asking for trouble from some very respected roboteers who, like me, believe very strongly in our freedom of choice.
Im sorry but I could never ask the FRA to even think about making it a condition of membership.
I fully appreciate that this DB is a good idea and may be a good contribution towards safety, well done to Leo for producing it.
But dont try to force it on people, especialy by using what I concider to be a back door route I.E. As put by Grant earlier it also states on our signup pages and most others that to signup you must agree to be used for advertisment or websites
That is not on!
To make this acceptable you will have to sell the idea on its benifits (which are many) also in the end you must have an opt in policy.
Comment