| great, i dont expect anything that "works" just a first attempt ... we wont be running any of the code ... Do good, Be Well, Michael --- On Fri, 4/23/10, Scott Williams <lswill...@gmail.com> wrote: |
Just a summary of what you did during the semester would be good too. We can have detail since its documentation but dont kill yourself. I would just contrast the charger designs ... talk a little about the one that didnt work, just talk about what you spent time on.
Ultimatley we need all the documentation done to turn in by next friday, but thats in duc's hands, but of course duc cant put it all together until he has it. If you get it done early enough duc i can look it over and see if i can improve on the documentation anywhere. |
Do good, Be Well, Michael |
--- On Sat, 4/24/10, Joseph Lopez <jolo...@gmail.com> wrote: |
| Ok Joseph Good Job, so far we have Trent, Joseph and Me done with their documentation. Duc has a template and is ready to fill it in. Everyone look at this diagram, this is what our "robot" is going to "do" this is its purpose. We basically want to be able to control the robot through the internet to demostrate how a human workforce could be automated through the internet( outsourcing anyone? ) Duc, tues-thurs is not really good enough. I would really prefer to look over the documentation before we submit it. I dont want stuff in there that is erronious, like old diagrams and such that dont really have anything to do with what we are doing. Its not that I dont trust you its just that I have a clear picture in my head of what the project is about and it changes quickly. For example this is what our current goals are http://uhclseniorproj010.googlegroups.com/web/jinx_overview.png?hl=en&gsc=qnzfiwsAAACmDSW8YMMQIvcFKbXxqLSk I know you will prob do it all right I just want to doctor it up to make sure It reflects what we want to do next semester. Just do your best and have it done by wed night so i can finish it off and upload it thursday. Call me if you have any questions. you should be able to start now and just leave a space for Scotts contribution. I'm pretty sure Scott is almost done also, he said he just needed to write up some documentation, he has already submitted the code. |
Do good, Be Well, Michael |
| --- On Sat, 4/24/10, Joseph Lopez <jolo...@gmail.com> wrote: |
| This was in the latest version of the code .... // sensors.h /* this just has some examples duc you really just need to map the sensorNumber that the user requests to the set_acd_channel(channel) then take the reading and return it. So you will need to make a list of the sensors and what number they would be. Lets just assume you have channels 0 to 7 for now. */ //these are just examples you dont need these since you are using channels // not pins #define ls0 PIN_A0 #define ls1 PIN_A1 #define ls2 PIN_A3 #define vref 5 // variables to use int16 adc_value; // adc read from AN0 0-1023 float volts; // volts 0-5v // todo: documentation // you could use ifstatements or a switch case .. i recommend switch case float getSensor(int sensorNumber){ set_adc_channel(0); // here you set the channel to 0, ra0 adc_value = read_adc(); volts = (float)(adc_value * vref)/1023.0; return volts; // return your result }// end function // AND MOTORS.H // motors.h file // motor array of bits int8 lmotor=0; int8 rmotor=0; // this is just one way you could do it however you want void setMotorSpeed(char side, int speed){ int8 speedvar=0; if(speed == 10){speedvar=0b11111111;} // or 0xff or 255 if(speed == 5){speedvar=0b00001111;} // or 0xf or 15 if(side == 'l'){lmotor=speedvar;} if(side == 'r'){rmotor=speedvar;} |
| } Do good, Be Well, Michael |
| --- On Sat, 4/24/10, zonemikel.com <zonetej...@yahoo.com> wrote: |
| No sleep on tuesday ? You have plenty of time, it should take you no longer than 2 hours to do the documentation, if you feel that you cannot let us know now before it gets too late. The sensors function looks fine, so did the other one. What we need is ... well we really dont know what we need but that function gives us options for each sensor which is great. See you all on monday. |
Do good, Be Well, Michael |
| --- On Sat, 4/24/10, Duc Tran <dtra...@gmail.com> wrote: |