one wish
Re: one wish
Wouldn't it be better to have a book?
I think what he's saying is that there is a wealth of practical information on this forum, but somehow, it needs to be organized by type of problem, etc. so that it can be used as a reference. I don't see a way to do that that doesn't require a lot of work.
If you know what you're doing, you're not learning anything.
Re: one wish
if the book can tell me how to communicte with a dallas 1302 like the information in the lost post could have then yes a book would be greatzristic wrote:Wouldn't it be better to have a book?
dont get me wrong i love books and i found the books here helpfull but at the end of the day a book is edited some info goes in some dont, who decides whats valuble, information to one person is rubish to another
the only way is to save all info and let people decide them selves, some times even the tinyest detail can lead to a solution even from an unrealated subject, why is the piclist so popular ? it has a massive archive
not to mention the advantages of new mikro users being able to draw on years of other mikro users research and projects and mistakes and differnt methods
there are 10 types of people Those that understand binary and those that dont
Re: one wish
I don't know how the SPI or I2C MB functions might solve your problem, but bit-banging might give you some results till you find something faster. It's only 3 PIC pins or 4 PIC pins (if you want to separate In-Out Data). This is not intended to make it sound simple....but possibly solvable.p3t3rv wrote:if the book can tell me how to communicte with a dallas 1302 like the information in the lost post could have then yes a book would be great
[color=darkred][b]xor[/b][/color]
[url=http://circuit-ed.com]CircuitED -[/url]
[url=http://circuit-ed.com]CircuitED -[/url]
A code repository would be really nice. Like the projects section on the mB web site, but split into categories (serial, glcd, i2c, spi etc etc) where any registered member can post their program/module/routine for others to use.
Having hundreds of pre-built routines available would make life easier for just about everyone here and reduce the workload of mE...
Having hundreds of pre-built routines available would make life easier for just about everyone here and reduce the workload of mE...
- Projects can be submitted by anyone who uses mB. Of course, they have to pass the scrutiny of the mE group.
I personally think it would be great to create libraries based on interface IC's which can be created out of successful programs using those IC's. For instance, the MCP4921 D/A converter. Create two simple instructions:For the 2 Channel MCP4922:Code: Select all
4921_INIT(Vref) 4921_OUT(milliVolts)
Code: Select all
4922_INIT(Vref) 4922_OUT(Channel, milliVolts)
[color=darkred][b]xor[/b][/color]
[url=http://circuit-ed.com]CircuitED -[/url]
[url=http://circuit-ed.com]CircuitED -[/url]
Hi xor
The projects section on the web site is a showcase of advanced projects to show off what mB can do. My suggestion was for "normal" routines/basic code. mE would only have to moderate the submissions just like they do on this forum
Your suggestion for the additional libraries is exactly what I was trying to describe. Like SHT11_Read_Temperature(port). Routines that have already been written many times, but just need to be put somewhere for everyone to use.
The projects section on the web site is a showcase of advanced projects to show off what mB can do. My suggestion was for "normal" routines/basic code. mE would only have to moderate the submissions just like they do on this forum
Your suggestion for the additional libraries is exactly what I was trying to describe. Like SHT11_Read_Temperature(port). Routines that have already been written many times, but just need to be put somewhere for everyone to use.