Is Picbasic good enough??

[Melanie]

If you read the DATASHEET you will discover that the PIC requires use of TMR2 for timing PWM functions. If you used Assembler with Hardware PWM you would still need to use TMR2 - there's no escaping it. There are no secrets regarding what PBP does or doesn't do to registers behind the scenes - it's all in the DATASHEET if only people bothered to look at them for anything more than the pinout diagram.

[rastan]

ok, were not having a dig here, i just wanted to find out whether it was worth with sticking with learning C for pic or just stick with the nice and simple picbasic.

cheers everyone

phil

[Twasnow]

I agree though, people should understand the processor they are using at a level deeper than the basic programming langauge, we aren't programming away on glorified 3 million man hour operating systems that we can take comfert in knowing it will stop us from doing things too stupid. But that is just lazyness and doesn't really answer the question "is picbasic good enough", in a word or so the answer is forty-two. The important thing here is the question. No not 7 times 6, "is picbasic good enough for what?". You decide, depends on your programming ability, and your task. as a defence for C, in my opinion it is just as easy to write in as Basic, and I have yet to meet a C compiler that doesn't have a slew of I/O functions. or a useable debugger, but that said I wouldn't want to plop someone infront of a C compiler that doesnt' know A) anything about the chip and B) C language. where as basic, I could get my unborn nefew to write me up a simple program, (well in a few years, when he learns a little bit of english.)

- my only suggestion, would be to include a little more code optimization at complie time (I am not even sure if there is any)

Twasnow

[Bruce]

Like riding a bike your first time - it's only hard or intimidating until you learn it. C is similar to BASIC in many ways, but it does have a much longer learning curve.

I recommend you learn assembly at some point also since you can drop-in .asm routines that will speed things up where canned functions aren't an option.

C is a lot of fun, and a good C compiler offers a lot of built-in goodies you just won't find in any BASIC compiler, but the BASIC language is hands-down the easiest to start with & see immediate results.

The BASIC Stamp is a good indicator. Lots of folks get started with the Stamp then migrate to more powerful (and much less expensive) alternatives like the PIC & BASIC compilers.

Part of my job is evaluating compilers. PBP & Proton+ are the best (IMO) at present. CCS & Hi-Tech in the C category - with CCS being the best for beginners. Tons of examples with CCS to get you started.

[Luciano]

The Parallax Inc."Basic Stamp" is a wonderful product for beginners.
The Parallax Stamps in Class™ Education materials is great.
The large majority of the new Micro Engineering Labs customers are
also Parallax Inc. customers. The success of the PicBasic compiler is
directly related to the success of the Basic Stamp module.
If one day a Basic Stamp user will not feel at home immediately with
the PicBasic compiler, then that day will be the end of the easy
customers acquisition for Micro Engineering Labs. The PicBasic
compiler will never lose its ties with the Parallax PBasic language.

The PicBasic compiler is a great tool for the hobbyist, experimenter
and professional. This compiler greatly reduces the software
development time and the learning curve.

Yes, Picbasic is good enough!

Luciano

[Twasnow]

Here is an example where you wouldn't want to use picbasic. at least I wouldn't.
1) I am currently controlling DC 2 motors via an H-Bridge, each motor requires 3 outputs from the pic, Enable and two direction (both directions are needed for quick stop) I have to output two PWM's each are dynamic in pulse-width, depending on a speed selection for each motor, and an encoder feedback to ensure they go at the required speed, or to compare the two motors to ensure they rotate the same amount. The encoders are each pulsing up to an average of 2 KHz. The PWM pulses are output at a frequency of approx 4Khz. Every 200 pulses I recieve from the encoders (100 ms), I update the PWM. I get the commands (speed/direction for each motor) from another PIC via a 4bit bus that is also read every 100ms, I also output a status pulse when a task is complete.

now maybe you could do this with basic, but I wasn't even going to try, I wrote this in ASM, but hey if I am wrong plesae correct me.

[toalan]

Okay here is an example that something that happened to me in Picbasic.

For some reason Tmr2 was triggering an interrupt, even when disable the intterupt apparently some of the picbasic code was enabling it. I had no idea what part of the code was doing that, so I copied and pasted line by line into a new program and for some reason that stopped the tmr2 intterupt from being triggered.

My point is that, I read the datasheet, but I do not know how exactly picbasic handles many of the registers.Honeslty previously i never read the datasheet and just plugged code into Picbasic, but now I read the datasheet I know exactly which registers I need to set, but sometimes Picbasic just overwrites my settings. I guess I could dump the Compiled program into ASM, but debuggin ASM based on someone else's interpretation on how to do things in ASM is just too much of a headache.

Neccessity is the mother of all invention, I guess Picbasic in some of its shortcoming has forced me to learn much more about the MCU than I wanted to, which is a good thing in the long run but a pain in the short run.

The PicBasic guys need to beef up their manual to show more advanced users what it is doing in ASM.

[Dwayne]

Hummm.

PBP has been ok for me. It is powerful, yet somewhat easy to use. I am a professional programmer, using C/C++ with Borland Compilers. About the only complaint I have with PBP, is syntax of the functions. But I also realize that this is a difference between the compilers too!
I prefer the following:

for(c=0;c<10;c++)
{
if(c==5) then printf("Number is equal to %2d", C);
}

Opposed to something like this:
For c=0 to 10
if(c=5) then print("Number is equal to ",c);
next c

Then the added "endif" and "wend". when a finishing bracket in C takes care of it all.

I have also noticed that some statements will show errors if they are on the same line. But if you put the exact statement on a second line..presto!

in reality, it is not a "limitation" of PBP, but more of a Syntax difference. A difference that is harder for me to get used to, after programming 25 years in another language. Thus, it is not a fault of PBP, but a fault of the user (meaning me).

I will say that pbp has done a wonderful job, and i clap my hands to the programmer.

Dwayne