Author Topic: SoR comunity project: serial LCD (Read 4889 times)

hazzer123 · « **Reply #30 on:** May 05, 2009, 04:19:31 PM »

We should make an SMD version and a non-SMD for each module (and maybe even a stripboard version). More flexibility is good

SmAsH · « **Reply #31 on:** May 06, 2009, 12:29:53 AM »

yea, that would be great and not too hard at all, thru-hole as a kit and open source design, smd for sale and stripboard designs up... although... some boards would be wayyy too hard to make on stripboard... actually most would $:-\$

TrickyNekro · « **Reply #32 on:** May 06, 2009, 04:56:19 AM »

I basically design my boards on what I can buy...

And they don't use ATMEGA32-AU here a lot... bad bad bad....
Also smd pin headers will be avoided cause of practical use..... (they unstuck with the copper layer in hard use....)
I'll try to make a version 1.1

Fixing some AXON incompatibilities.... Get a holda!!!

SmAsH · « **Reply #33 on:** May 06, 2009, 05:03:41 AM »

haha nice, are smd more easy to get over there than thru-holes?

Quote from: TrickyNekro on May 06, 2009, 04:56:19 AM

Also smd pin headers will be avoided cause of practical use..... (they unstuck with the copper layer in hard use....)

is this because they are just stuck on the copper with solder?

TrickyNekro · « **Reply #34 on:** May 06, 2009, 11:18:44 AM »

It depends on what you are asking for....
I know the supplier here...
So if there are smd parts in a big order...
He tells them to include some exclusive parts for me...
Thing is that, if they don't have something and EBV has it...
I get it in 2 - 7 days, based on when the big order was placed and such...
If I don't want to wait for the for an order then I can have the parts in 2 days but
pay some ~17$ US more.... still no big deal...

Thing is that I do this only for some very rare parts that no one uses them...
So from resistors to microcontrollers (here the use more AVRs so I get plenty of them....)
to anything I want I got it....
Plus modules, development boards etc etc etc

Quote from: SmAsH on May 06, 2009, 05:03:41 AM

is this because they are just stuck on the copper with solder?

yup....
Come on... I love smd parts.... much less development time.... Yeah!!!
( I do want to avoid drilling as hell....)

SmAsH · « **Reply #35 on:** May 06, 2009, 02:23:04 PM »

Quote from: TrickyNekro on May 06, 2009, 11:18:44 AM

Quote from: SmAsH on May 06, 2009, 05:03:41 AM
is this because they are just stuck on the copper with solder?

yup....
Come on... I love smd parts.... much less development time.... Yeah!!!
( I do want to avoid drilling as hell....)

oh god, tell me about it... 6 broken 1mm bits in one hour $:-\$ damn i was frustrated!

Ro-Bot-X · « **Reply #36 on:** May 06, 2009, 04:40:08 PM »

I guess my post didn't get through last night... I was having problems with the net.

So, I guess none of my previous questions were answered... I will make them more obvious, just keep in mind the LCD module should be mounted on top of all boards or to the side, to be visible:

1. Do we want the board to be like an Arduino shield (that means a plug in board, not just a stackable board connected with wires)?
2. Do we want the board to have polarised Molex connectors (0.1" pin space) for both UART(3 pins) and TWI(4 pins)?
3. Do we want the board to be full size or half size?
4. Do we want the board to have right angle connectors on the sides so it can connect to another half size board (if the board will be half size)?

Now I know TrickyNekro is working on a similar board, but he is using a big mega32 and I'm using a tiny2313. The more, the merrier. The software should be compatible up to the point of setting the proper registers, so I guess it should not be too complicated to port the code from one micro to the other.

dellagd · « **Reply #37 on:** May 06, 2009, 05:14:44 PM »

1. I think no (wires but still stackable), as yes would make it less flexible, also we can make them ribbon wire things for no tangled wires
2. no also, because since it is already on top of a board there is really no need to make things chain off of the display (assuming it already has connecters so it can act as a TWI divice)
3. half size because you will probably need to be able to get to the stuff underneath the display (outputs on the side not covered).
4.uhhhhh... no, because it defeats the purpose of having a half size board.

bear in mind that half size will be a very small space to work with though

Razor Concepts · « **Reply #38 on:** May 06, 2009, 06:55:58 PM »

For number 4, he means you can connect two half sized boards to take the space of a full sized board.
*facepalm*

dellagd · « **Reply #39 on:** May 06, 2009, 07:02:59 PM »

I know that
but if you connect 2 half size boards whot is the pont of making it half size?
why not just make it full size

Razor Concepts · « **Reply #40 on:** May 06, 2009, 07:29:03 PM »

Because then you have TWO boards instead of one.

dellagd · « **Reply #41 on:** May 06, 2009, 07:46:51 PM »

Oh

now I see what you mean
sry guys

TrickyNekro · « **Reply #42 on:** May 07, 2009, 01:08:53 AM »

Quote from: Ro-Bot-X on May 06, 2009, 04:40:08 PM

Now I know TrickyNekro is working on a similar board, but he is using a big mega32 and I'm using a tiny2313. The more, the merrier. The software should be compatible up to the point of setting the proper registers, so I guess it should not be too complicated to port the code from one micro to the other.

Hey.... I'll rebuild it as a development board.... I'm just used to mega32...
And no problem should exist at all... It's all about port setting...

And something more... hey guys...
try to make a OSCAR library for eagle if you have something in mind... So we can base our designs there...
Don't just nag, if it isn't compatible with anything you know...
We have different thoughts about many things...
So let's just start clearing them out...

I personally have ALL the good will to help out... But, tell me where my feet are....
I could easily say, hey I did a board, I put effort and time into it... And hey these guys, only say there
are problems without even helping with the basics (the OSCAR CAD library......

)
But, f@ck the effort, I enjoy what I do...
And f@ck the time... Although I don't have plenty....

Help out a little.... Don't just comment... aimlessly without doing something practical...

I tell this to everyone... Cause this is the meaning of a community... help each other...

It's just like the communistic political parties over here...
Fight for your rights, fight for your rights, fight for your rights...
And everything turns up to be a a noisy mess with a lot of arguments, and no job done...
You gotta work to have rights to speak... that's the truth...
You gotta offer first, not only your thought, and then comment...

I just hope... that we can do a community project everyone will be proud of...
Both from inside and outside this community...

Amen, guys...... amen....

SmAsH · « **Reply #43 on:** May 07, 2009, 01:16:12 AM »

tricky, i don't want to sound mean... but we are open to everyone's thoughts.
we have about 3-5 modules going right now which makes me happy...

to ro-bot-x:
it does not matter what mcu he designs it on as we can probably switch it over later easily...
he is probably going by what he has available/can get easily.

and tricky, by eagle library what do you mean? like a library with all of our board designs in it?

Ro-Bot-X · « **Reply #44 on:** May 08, 2009, 06:51:50 AM »

Quote from: SmAsH on May 07, 2009, 01:16:12 AM

to ro-bot-x:
it does not matter what mcu he designs it on as we can probably switch it over later easily...
he is probably going by what he has available/can get easily.

and tricky, by eagle library what do you mean? like a library with all of our board designs in it?

I'll answer the last question first. He means a library with parts that we are going to use in all modules schematics and boards and of course, a board template for each board size, allready made with mounting holes and side connectors for I2C interface. That way, anyone can use a template to built his own module and if he adds a new part to the schematic he needs to update the library and upload it on SoR.

Now to the first matter. You see, to me it's easier to use ATmega8/168/328 for any module, make it standard size, program it in Arduino and use a hardware programmer to upload the code. But for some modules I feel a mega8 is a waste of space, pins, program space. That's why I tailor the microcontroller to the job and not use whatever I feel confortable with. But it has to be a widelly available microcontroller so almost anyone can get it and build the module. And I like to build the module as small as possible to make room for other modules and the robot does not get too bulky. I'm sorry if I get on other people's nerves, I just try to design something that I would be proud off. And instead of letting TrickyNekro go ahead and build his module then work it out to a smaller version in secret and present it afterwards, I'm inviting him to join efforts to build a module that will suit all needs.

TrickyNekro · « **Reply #45 on:** May 08, 2009, 09:24:16 AM »

Hehe... I'm always here.....

Don't worry...

Ro-Bot-X · « **Reply #46 on:** May 25, 2009, 01:52:40 PM »

I think an update is in order.

After the tiny84/85 compatibility with Arduino software has been released by LumiNet developer, I have decided to build my small modules using tiny84, a 14 pin DIP micro. I intend to build for my robot a serial LCD and a dual DC motor driver with encoders. I will work on the boards and order them through Batch PCB so anyone here can also get them. This way people can have at least something to begin with, easy to program using Arduino software or AVR GCC. I'll make updates in the proper topic for the motor controller soon, since that one is the first I'm going to work on, because I allready have a different serial LCD (I need a second one, that is the reason for taking on the project).

emmannuel · « **Reply #47 on:** May 26, 2009, 08:04:40 PM »

I actually started this same project in the begging of my previous semester

I got a bit frustrated and switched to the attiny26 and then gave it up and worked on something else.

My goal was to make it an I2C LCD driver with all options being passed through the I2C bus.

The challenge I gave up on was removing the potentiometer for VO.
I wanted it to be full SMD with the controls being read from another microcontroller and the values passed through the I2C bus to the tiny26.
From searching around I found that the pot should be able to be replaced by a PWM signal with a low pass filter. Are my low pass filter values (R=10k, C=1uF) right? I couldn't find anyone that could confirm them

I still would like to get it done so here's where I left at:

Razor Concepts · « **Reply #48 on:** May 26, 2009, 08:20:55 PM »

Digital potentiometer maybe?
http://www.maxim-ic.com/products/digi_pot/

News:

Author Topic: SoR comunity project: serial LCD (Read 4889 times)

Related Topics