My Official Introduction, and What Role to PIC MCUs Play in Your Lives?

[rxforspeed]

Enjoy
http://www.picbasic.co.uk/forum/showthread.php?t=5988

Once again, Dave to the rescue! I didn't even think about searching for this topic before posting it. After reading that topic, I feel like "part of the family" now, or at least I have a better idea of the backgrounds of those that have and are providing the help I'm seeking...

Hi Adam

A bit off topic, but not really, in the End ...

Answering your question about Easypic5 on "another Forum" ... compatibility is 100% when using Microcode Studio as an IDE.

Using MPLAB allows compatibility too ... as you just have to transfer your Hex to the Easy5 onboard progammer ( one mouse click ! )

I've also appeciated your RX8 "Engine stories" ... I just can tell, Here, on this forum, you will meet VERY highly PbP and Pics Qualified users ...

so, listening to their advices will be ... the least to do.

Welcome here and have fun in theses columns.

Alain

PS: as Humour must be Keyword ...

you've forgotten to write that :

Thanks Alain-I've since purchased the EasyPIC5 along with the 128x64 GLCD and touch screen, the 2x16 blue backlit LCD and DS1820, along with an additional 4x20 blue backlit LCD and additional touch screen connector. I will get microBasic in the near future, but I really need to familiarize myself with PBP a bit more to avoid confusion between the two at this time. I've found it VERY easy to use compiled PBP programs on the EasyPIC5, just in my case I still have to remember to change the oscillator setting to "HS" when I use it. I'm hoping to see an upgrade to PBP in the near future that allows the use of GLCD commands so I can take advantage of the extra touch screen connector I've purchased, but I'm sure I can use microBasic for that once that need arises...

As for the RX7club forum, I really should send a "thanks" to members like Aaron Cake and others for literally laying the foundation for my current interest in electronics. He, and others, had introduced me to the Megasquirt engine management system (the DIY EFI "computer"), helped me learn what I needed to about the rotary engines, and instilled a thriving thirst for knowledge about custom electronics, which I've slowly been quenching for last year or so...

I'll try to ease up on the long-winded posts and "cut to the chase" here. I'm bad for that, but I'll make sure to type the least amount possible while still including all the necessary information...

Thanks to all for the warm welcome; I won't act as a typical "noob", posting the same topic in multiple parts of the forum, asking for info that's clearly listed in either the datasheets or PBP manuals, etc. I do my best to do my homework and make sure the answer to my question doesn't lie right in front of me before I ask. In most cases, I probably have the answer in a book I own (or one checked out from my local library) and will attempt to find it there or by searching this and other forums before disturbing others with it...

All the help, cooperation, and direction is greatly appreciated!
Sincerely,
-Adam Collins

[rmteo]

You can download the demo version of mikroBASIC for free. It has a very generous limit of 2K of compiled code - enough to do just about any beginner project. Plus you get the advantage of structured programming (true functions and procedures with parameter passing), GLCD, SD/MMC, RS-485, etc. Also, the PICFlash programmer (of your EasyPIC5) is fully integrated and you can also do hardware ICD (in-circuit debugging) - single-stepping, breakpoints, read register values and much more.

[rxforspeed]

You can download the demo version of mikroBASIC for free. It has a very generous limit of 2K of compiled code - enough to do just about any beginner project. Plus you get the advantage of structured programming (true functions and procedures with parameter passing), GLCD, SD/MMC, RS-485, etc. Also, the PICFlash programmer (of your EasyPIC5) is fully integrated and you can also do hardware ICD (in-circuit debugging) - single-stepping, breakpoints, read register values and much more.

I've noticed some of the features offered by microBasic that aren't incorporated in PBP, so I have downloaded the demo version but have only used it to compile the included sample programs. I'm going to add it to my toolbox eventually, but I'd like to get a better grip on PBP first. I've studied a few lessons on Assembly, but the two languages are really too different to confuse me. I figured that if I started trying to learn microBasic before I've mastered PBP then I would just confuse myself due to all the similarities and minor variations between it and PBP. If nothing else, I feel the cost of microBasic is worth it just for the GLCD purposes...

I've packed my brain with WAY too much info on everything I'm trying to learn here lately to start in on mB. PBP has done everything I've needed for the time being, but I still need to reference the manual and certain books when writing code for even simple projects. Once I get it down, I'll jump into mB.

Here's a useful document for comparing and converting code from mB to PBP or vice versa: http://www.mikroe.com/pdf/mikrobasic/migration_path.pdf

It's really just a general overview of the two languages, but it provides a little bit of info regarding the differences between the two...

I have since purchased the PICkit2 from Microchip, but I haven't played around with the ICD capabilities of it yet. I'm working on it, but there's still a LOT more learning I need to do before I'm ready to tackle microBasic and their ICD...

-Adam Collins

[Acetronics2]

Here's a useful document for comparing and converting code from mB to PBP or vice versa: http://www.mikroe.com/pdf/mikrobasic/migration_path.pdf


-Adam Collins

WARNING !!!

This document is probably VERY old , or the writer never used PBP ...

of course it is to prove that MKBasic is the best ..., but LOTS of arguments are totally FALSE ... and LOTS of infos are OUT of DATE !!!

So, ... this piece of paper only use is for ... toilets !!!


I'm not partial here, use both compilers, and know enough of both to prove what I've written ...

Alain

[rmteo]

Alain, since you use both compilers, would it be possible for you to highlight the Pros and Cons of the two?

[mister_e]

I guess it depend of what you've done 'till now with PBP. It also depend how much you trust in hidden compiler feature.

Having already spending a lot of my time to build many routines to interface many different type of hardware, I now understand how things work and how to solve a problem, to migrate some routine to suit another hardware (let's say different GLCD controller type). But yeah... i spent time on it. What if I haven't time? MAYBE i would use a tool who give me the feature i need... but more than likely, I would go in a different way, so I'll use something I'm comfortable with... hence PBP.

You can't tell which is better.. if so what's your own definition of better?

I'll stop here for now.

[Acetronics2]

Alain, since you use both compilers, would it be possible for you to highlight the Pros and Cons of the two?

Hi, Rmteo

As you also use both compilers ( lol )... you know PBP has no big dedicated libraries like GLCD, Nor direct support for floating arithmetics.

The main point between, I think ... is the PBP extensive use of "soft written functions" where MKB widely use Hard resources ...

Major impact on flexibility and portability ...

I'd also add PBP existing libraries are MUCH easier to use Than MKE's ...


Now, I was speaking about TRUE , FALSE , and OUT of DATE arguments ... just points that are easy to verify and do not imply any subjective appreciation.


The translations from MKB ( or C ! ) I've done to the day just showed me PBP "way of thinking" and syntax was easier FOR ME ...



As a "solid" comparison example ...

I posted here a "translation" of Warren Schroeder "RC Pulse and duty meter" ( MKB )...

http://www.picbasic.co.uk/forum/showthread.php?t=9709

As you'll see ... it's far from a "line per line" translation ... but, to me , is a good way to show how same question can be solved both ways ...


Which is "better" ... lol !!! everyone has it's own criteria ...

Alain

[rmteo]

Thanks for your comments, Alain. I have mkB and mkB for dsPIC plus 2 other BASIC compilers - but I do not use PBP - not yet.

The question was NOT which is better. I was asking your opinions on the Pros & Cons of PBP vs. mkB which you and mister E have answered.

[rxforspeed]

WARNING !!!

This document is probably VERY old , or the writer never used PBP ...

of course it is to prove that MKBasic is the best ..., but LOTS of arguments are totally FALSE ... and LOTS of infos are OUT of DATE !!!

So, ... this piece of paper only use is for ... toilets !!!


I'm not partial here, use both compilers, and know enough of both to prove what I've written ...

Alain

My initial impression of that document was that it was a comparison of an earlier version of PBP and not the current V2.50b that I own. The first few lines of the page do help in understanding a few of the major differences between mB and PBP, though. I agree with you, Alain-the rest is pretty biased towards mB. Of course, that link was sent to me from a mikroElektronika employee after a barrage of questions regarding the use of the EasyPIC5 with PBP...

I would very much like to see some "GLCD" commands incorporated into PBP, but like I said, I'll eventually get mB if for no other reason than that. Unless MELabs introduces a new upgrade to PBP with "GLCD" commands in the next few months...

I also plan on learning Assembly, "C", and other programming languages in the coming years to eventually migrate to some more sophisticated 16-bit MCUs and to expand the tools in my toolbox. I'll upgrade PBP as long as the upgrades contain features that are useful to me, but I don't want to be limited to a single language years down the road when or IF these 8-bit PICs become obsolete. BUT-I've still got a decent journey to fully comprehend the abilities and limitations of PBP ahead of me first, so I'm not looking to migrate until I become independent of the manual and certain books I need to reference at the current time...

-Adam Collins

P.S.-Sorry to post that biased link, I shouldn't have included it.
Disclaimer: Adam Collins is in no way affiliated with either mikroElektronika or microEngineering Labs, Inc. All thoughts, ideas, suggestions, and information posted is only the ideals and views of Mr. Collins, and do not reflect the views of either the owners/Administrators of this forum, mikroElektronika, or microEngineering Labs Inc. Download and read the referenced link at your own risk, and remember that it was written to highlight the so-called "benefits" of mikroElektronika's mikroBasic.