PBP Book

[bbarney]

Hey Luciano
I'am curious where you got the picture of Bill Gates bathroom
and believe it or not Donald Trump has one too

[mister_e]

PDfs are great but can be copied and distribute too easy. I prefer paper touch. Usually this how most PDF ends up here.... let's see a PIC datasheet.

[Scampy]

Three and a half years on... is the book anywhere near completion ?

Thing is that since it's conception PBP has probably been released with 3 or 4 revisions....

[circuitpro]

PLEASE make it in the form of a PRINTED book, (or a PDF that WE can print)! Some of us old timers still prefer an open book on the table, with a highlighter, to anything else!

I'm in for a copy.

[Kenjones1935]

Bruce,

I too like the feel of paper. I find that scanning the printed page is easier than "FIND NEXT".

Please include an INDEX. That is a big issue for me.

Please include a technical description of the path from BASIC to ASSEMBLER to HEX. Please tell us what is an INCLUDE file. What is a MACRO. What is an EXTENSION.

Your good book combined with MikroElektonika's PIC "MICROCONTROLLERS with examples in Assembly Language" would make all this much easier.

Ken

[david1800]

I have recently retired and although I have been wishing to get to grips with PIC programming for a number of years, previous work commitments meant there was never enough free time. I have dabbled in electronics so have a rudimentary understanding of the hardware aspects but am now finding it difficult to find publications pitched at the right level to get started with PBPro.

What I would like to see in the book is a section for those who know nothing. For example, I see a code such as ADCON = 7 and it's not apparent to a complete beginner what this means (I know now). I imagine that there may be many like me, who given the base information in a clear and concise form, can work forward, but without it will struggle, not start or may give up.

Clearly any technical publication is always a balance between being oversimplified and overcomplex. In my experience in other fields they can fail to meet their audiences needs by leaving holes between the simple introduction then leaping into the complexities. You feel as though you are getting to grips, then are left floundering. This can be difficult for an expert to put together and can benefit by testing on novices. (Happy to help)

I don't think this introduction needs to be overly long, but it does need to be carefully constructed to provide a sound understanding.

Others are much better placed to comment on other aspects of what should be included based on their actual experiences, however I would look for plenty of worked examples to help me construct my own programs.

I hope this is helpful

regards

David

[Bill Legge]

Bruce,

I think you were intending to write a PIC book some time ago?

If you are still going to do it, I'd be pleased to provide some input, not because of any technical skills on my part but I started learning about PICs three years ago and the difficulties/mysteries are still fairly fresh in my mind.

Let me know if you want some input.

The 'two stepper' code is working very well and I've posted it on this site. The plotter scanner is great fun and the mechanics are pretty smooth - courtesy of cheap Chinese linear bearing that appeared on eBay a few month ago (About $10 each instead of $+++ for the 'proper' ones).

Regards Bill Legge

[Ioannis]

Also a good idea would be, if Darrel permits of course, to include the DT-INTS as they are better that the ON INTS of the lanquage itself.

Ioannis

[Megahertz]

Is the book out yet?

[CuriousOne]

Why this thread popped up as a "recent" ?

[Ioannis]

Who knows? Maybe someone did edit a post? Or delete?

Ioannis