Author Topic: SOR community project? (Read 49349 times)

SmAsH · « **Reply #120 on:** June 01, 2009, 02:51:53 PM »

i guess your right chelmi $:-\$
ill take a look at some of those libraries sometime...

dellagd · « **Reply #121 on:** June 01, 2009, 03:16:37 PM »

I agree with chemli, but I also like the idea of having the ability to just hook up a servo to a master for easy control

chelmi · « **Reply #122 on:** June 01, 2009, 03:41:07 PM »

Quote from: dellagd on June 01, 2009, 03:16:37 PM

I agree with chemli, but I also like the idea of having the ability to just hook up a servo to a master for easy control

Yes, but you don't need OSCAR to do that :p

SmAsH · « **Reply #123 on:** June 01, 2009, 09:02:43 PM »

lol, that confused me...

dellagd · « **Reply #124 on:** June 02, 2009, 06:07:14 AM »

no I liked the idea of it mostly being a I2C system, but we dont take away the ability to just straight hook up a lightsensor. if you want 1 simple light sensor there is really no point in making a whole module for it! its just impractical

SmAsH · « **Reply #125 on:** June 02, 2009, 06:52:50 AM »

but for most of the I2C systems we want them to be more than just a "simple" design that a normal
I/O pin can handle otherwise it defeats the purpose of I2C.
for example... a simple motor driver will take up 2 I/O pins, add an encoder to that, that's another 1/2 pins.
with I2C this "over" usage of pins can be avoided.
but with the axon i don't think many people would run out of I/O but still...

hazzer123 · « **Reply #126 on:** June 02, 2009, 07:45:56 AM »

It's not just about IO pins. Having the main controller send out PWM to a H-bridge would use up a timer, or some processing time. Outsourcing this job means the master has more time to ''concentrate' on the higher-level processing,

dellagd · « **Reply #127 on:** June 02, 2009, 01:53:43 PM »

the point of this I2C system is like the master can say to the motor-comtroller, get me here. the motor controller Will figure out how to do that not the master. the master is the conductor of a I2C slave orchestra

spykid99 · « **Reply #128 on:** June 04, 2009, 05:17:14 AM »

Hi Guys
As far as i can see from reading the first 2 or 3 pages of the original thread we are trying to create a system of "modules" that interconnect with each other like a plug-and-play system on computers.

Also because i live in Australia and i don't think anyone else does i cant help with building but i would be willing to help with high-level(C/C++) programming (I think you guys are talking about assembly, sorry if i'm wrong) i also think we should concentrate on a wide range of MCUs (I have not seen one post on the forum relating to OOPic for example and thats a good MCU (I think) plus im good at programming that.

What do you think, please tell me if im wrong (Im a noob)
Spykid99

SmAsH · « **Reply #129 on:** June 04, 2009, 05:29:00 AM »

Quote

Also because i live in Australia and i don't think anyone else does

er hem... i believe somebody forgot to view smash's profile?
you can still build a module, no matter where you live.

Ro-Bot-X · « **Reply #130 on:** June 04, 2009, 06:07:08 AM »

Quote from: spykid99 on June 04, 2009, 05:17:14 AM

Hi Guys
As far as i can see from reading the first 2 or 3 pages of the original thread we are trying to create a system of "modules" that interconnect with each other like a plug-and-play system on computers.

Also because i live in Australia and i don't think anyone else does i cant help with building but i would be willing to help with high-level(C/C++) programming (I think you guys are talking about assembly, sorry if i'm wrong) i also think we should concentrate on a wide range of MCUs (I have not seen one post on the forum relating to OOPic for example and thats a good MCU (I think) plus im good at programming that.

What do you think, please tell me if im wrong (Im a noob)
Spykid99

All the embeded programming is done in C. Assembly is used rarely, for tight functions that are time sensitive (I think, I never use it). So, if you like to help with the programming you're wellcome. Many of the electronists are not that good programmers (especially me

)

About microcontrollers used, we are using AVRs and PICs. OOPic is an augumented PIC that has a firmware installed that interprets the commands stored in EEPROM at the time of execution. This slows things up pretty much, plus you don't have too much space in the EEPROM for user data. I have an OOPic-R board and I coudn't use it to read the Ping))) sensors that require a 5us trigger pulse, because the OOPic takes too much time to do things.

I sugest you take a look at Arduino, since it uses C/C++ programming, uses an AVR ATmega8/168/368 and has a bootloader that allows you to program it just like the OOPic. I am going to use this language to program my modules, at least until someone translates the programs in "real" C.

dellagd · « **Reply #131 on:** June 04, 2009, 02:59:22 PM »

I'm a good c++ programmer too. here's a sample.
also, "real" c?

PS actually I have seen a good few Australians here

oh and quick question, I want to add a pic in my signature, what is the code to do that?

SmAsH · « **Reply #132 on:** June 04, 2009, 03:37:38 PM »

i think you get the link for the pic then add [img] and [img] around it.
not sure but ill try it

kpmcgurk · « **Reply #133 on:** June 04, 2009, 03:43:24 PM »

hrm... I know its off topic, but when your program asks for a product name, And I type it in, It throws me into an Infinite loop... Am I not meant to type in a string? or did you forget to add this at the top

Quote

#include string.h

Thats my Idea... remember that strings are not part of C++, they need to be initialized first before use...

could I see the code for your program?

dellagd · « **Reply #134 on:** June 04, 2009, 07:35:11 PM »

where are you getting this from

hazzer123 · « **Reply #135 on:** June 05, 2009, 01:15:30 AM »

Please make a new thread for this stuff guys....

Regarding our choice of MCU, this wasn't really a conscious decision (sort of). We are using PICs and AVRs because that's what we and most people in robotics use. If you like OOpic then feel free to port our libraries to work on those, we'd be super-happy if anything increased the flexibility of the platform.

Of course there is no code to port yet... but i think there are a couple of guys who will get the ball rolling soon. And as soon as i finish exams (next friday) ill get to work on my module and see if we can start making real progress with this thing.

spykid99 · « **Reply #136 on:** June 05, 2009, 01:50:40 AM »

Quote from: hazzer123 on June 05, 2009, 01:15:30 AM

Please make a new thread for this stuff guys....

Regarding our choice of MCU, this wasn't really a conscious decision (sort of). We are using PICs and AVRs because that's what we and most people in robotics use. If you like OOpic then feel free to port our libraries to work on those, we'd be super-happy if anything increased the flexibility of the platform.

Of course there is no code to port yet... but i think there are a couple of guys who will get the ball rolling soon. And as soon as i finish exams (next friday) ill get to work on my module and see if we can start making real progress with this thing.

I agree that we should make a new thread +ask admin for a new subforum (which would be great) and that its great that we will soon have libraries so people who can understand AVR language (NOT ME) can do that porting and also where is a good website to learn about PIC programming with C

Thanks
Spykid99

hazzer123 · « **Reply #137 on:** June 05, 2009, 02:02:28 AM »

Well there are 2 main tools for PIC programming in C. Microchip C18 (for PIC18s) and Hi-Tech C PRO Lite mode (for all PICs).

C18 - Getting started user guide - http://www.kevin.org/frc/C18_3.0_getting_started.pdf
Lots of code examples - http://www.kevin.org/frc/

C PRO Lite mode - Vendor's site here - http://www.htsoft.com/products/compilers/piccpro-modes.php
They have a forum and there'll be plenty of manuals and example code in google.

spykid99 · « **Reply #138 on:** June 05, 2009, 02:13:32 AM »

Do we have a freewebs thingy or does someone need to make it

Thanks
Spykid99

SmAsH · « **Reply #139 on:** June 05, 2009, 02:26:22 AM »

i have a freewebs page that has info on it...
i can make a page specifically devoted to ALL modules if you guys want?

spykid99 · « **Reply #140 on:** June 05, 2009, 02:29:51 AM »

I think that if we have a site that everyone could edit and it contained a page for each module +about project etc.

Thanks
Spykid99

SmAsH · « **Reply #141 on:** June 05, 2009, 02:38:07 AM »

ok, we need to not post anymore in this thread about this stuff...
we don't want another 8 page thread

if you have any suggestions you can pm me.

kpmcgurk · « **Reply #142 on:** June 05, 2009, 05:23:39 AM »

If you guys want, I can make a website...maby with a blog and forum on it? along with just a general home page so onlookers can get a feel for what the project is like before they decide to take part in it?

EDIT: Nevermind, I just saw the other thread...

dellagd · « **Reply #143 on:** June 05, 2009, 05:35:46 AM »

why dont we just make a free webs page and pm everyone working on the project the username and password?
like www.sorproject.freewebs.com

spykid99 · « **Reply #144 on:** June 05, 2009, 05:46:46 AM »

You just missed out on the fun, i did it LOL
Go to the chat

Spykid99

Asellith · « **Reply #145 on:** June 05, 2009, 08:00:16 AM »

I am working on a sourceforge page for the project. That was we have forums and news and the ability to mass contribute in an established system. Should be up and running enough to go public next week. I can start working on it again later today or tomorrow still not able to sit in a chair for long after my surgery yesterday.

SmAsH · « **Reply #146 on:** June 05, 2009, 03:25:28 PM »

well, asellith.
its great to hear the surgery is over, but don't strain yourself, theres no rush...

News:

Author Topic: SOR community project? (Read 49349 times)