Printable View
Hello, I have PBP 2.5b.
I was considering to upgrade it to PBP3 - Gold version. Can someone please advise what is better in PBP3.
- Can DT_INT be used with them without limitation?
- What are the major enhancements compared to PBP2.5b?
Any other relevant info is welcome. Thanks
Wow, now there is a new version of PBP. I was just getting confortable with PBP 2.60 :eek:. What are the improvements and changes of PBP3 Gold version?
Robert
Wow indeed, $64 for the upgrade from 2.6, including new version of MCSP - ordered! I have no doubt it's worth it.
Here are a couple of items from the feature list that drew my attention:Only thing I don't like (but do understand) are the dreaded online activation keys... They do allow installation on three machines though which is nice.
- Parsing and Formatting of ASCII Strings
- Conditional Compilation with Command-Line Constants
- Configuration settings listed for each supported device
- New #CONFIG directive eliminates the need to edit header files
I really hope the new version (5.0) of MCSP contains loader files for the newer PICs or better yet (if possible) a generator like they say is available for the MCSP ICD.
/Henrik.
Only for the new
#CONFIG
#ENDCONFIG
option it worth it. BTW 50$ is nothing too keep the development alive.
It's about time :D There's NO advantage to use PM over MPASM anyways.Quote:
In addition, the PM assembler is no longer supported
Again MELABS get my vote, sure they done it well as usual. I use it since 99 (or so), and from the whole set of other compiler I bought/tried for this specific range of PIC, it's the best. Period.
I agree with Steve about the conditional configs, for that alone it is worth it to me. But they also got rid of the 64 character path limit- that's icing on the cake!!!
I think it is worth it. But it depends on your situation.
Perhaps it is worth more that $50?
PBP GOLD 1 year maintenance/upgrades $50.00
CCSINFO.com 1 year maintenance/upgrades $200.00
HITech C 1 year maintenance/upgrades $275.00
What do you mean by this? Where do I find this configuration settings listing?Quote:
Configuration settings listed for each supported device
Thanks
Dwight
PS. I all ready jumped in for the upgrade...
When I went over to the MELabs web site I was a bit disappointed by the LACK of fan fair!!
Come on MELabs TOOT that horn. Hype it up a bit!!
Did I miss the major announcement here on this forum?? or is this Thread the only hint that the new version is out??
In the Migration notes they mention a new file structure and the introduction of .INFO files - it's in these files that the CONFIG directive options are listed - atleast that's MY understanding. Short of that the info is available in the MPASM header files anyway so I'm not sure exactly what the difference is - time will tell.
I didn't know about the upgrade either untill I saw this thread, it's got to be brand new since there's not even any info regarding it in the version history. I've also signed up for their e-mail list but haven't received any news thru that channel either. So, like I said, it's probably juuust released, I'm sure we'll hear more about it in the weeks to come!
PBP3 was just made available in the on-line store on Friday.
It has not been officially announced, but it didn't take long for people to notice and start talking about it.
With the changes in the way PBP3 is purchased and downloaded, we hoped there wouldn't be a flood this weekend, in case a problem popped up with the new systems.
PBP3 installs with a 15-day trial that gives the FULL compiler with ALL available chips.
The trial is not limited to 31 lines like the previous demo version.
Feel free to download and try it at http://www.PBP3.com
It may even be possible for 3rd party programmers to write new commands and make some money.
- Yes, DT_INTS is compatible with PBP3.
- The #CONFIG block is awesome.
- The conditional compiling is more usefull than I ever imagined.
- The ability to add new commands to the language without modifying the compiler means you will be seeing a lot more capabilities at a faster pace.
But that part is only one of our wishes at this point.
HI2C, HSPI, CRC etc. is all possible now, the framework is there, but the code isn't, yet.
With easy updates from downloads, those pesky patches that won't run because you modified an .inc file are a thing of the past. Just download and install the new version and away you go.
Alain will finally be happy.
In fact, there is no reason to modify the .inc files at all anymore because the #CONFIG block eliminates the need to comment default configs. You can also use the new style CONFIG directives on the 18F's. (Much easier)
PBP3 is compatible with Microchips MPLABX IDE.
Get the 15-day trial at http://www.PBP3.com
It installs seperately from your PBP 2.60 and prior versions of PBP, so you can have it installed at the same time.
It includes the new version of MicroCode Studio which also co-exits with previous versions of MCS.
There are many more things to talk about, but I can't do it all in this post.
Get the Trial, give it a try, and Read The Manual.
Ordered already! Will wait till tomm to get the new version. :)
Best part is that the old version does not get affected, any problems, I will still be able to carry on with my old version (if I understood the last 4 lines of the post above)
Gold Version is fantastic, conditional compiles take me back to my 'C' days.
With the new #config I have one include file for the several PICs I use which sets the configuration fuses according to
which PIC I'm using at the time.
Regards
I also like pbp3. I'll move on it anytime soon.
But function still missing. And maybe MCS5it would be nice "Optional Command Line" for certain tab.
Bought it yesterday, waiting for melabs e-mail. PBP Proof of purchase on hand, but not MCSP one... dunno where I've put that one :eek:
Something is slick now... I did it manually before but...
Cool, no longer need to do it manually :DCode:TMR1 VAR WORD EXT ; Joined SFR, BANK0
TMR1L VAR BYTE EXT ; BANK0
TMR1H VAR BYTE EXT ; BANK0
I think the new Version 3 PBP compiler came at the right time and for the right price. Reading the manual (I'm the type that will do that several times before I dive in) I can see features that will make my life easier and more that I never even knew I was missing. I like the layout and style of the v3 manual.
Perhaps 15% of my work time is spent writing and debugging uC code, but when I'm at that stage in a project it proceeds with single-minded intensity. PBP has always been there for me. My first PBP install disk is a 3.5" floppy. I know several other programming languages but I've never done micros with anything other than BASIC. I'd hate to be forced to go that route.
I am happy MELabs has captured Darrel Taylor and that they apparently have a plan to maintain or increase their success into the future. I would have paid full price if they made me (although I would have complained some about that...) to keep the product going.
So for those reasons (and several others) I think it is totally worth it.
Best Regards,
Paul
I did not got it. Wasn't this available to the previous versions?
IoannisQuote:
Originally Posted by mister_e
Indded, but you needed to manually enter the TMR1 line... big deal...
Oh, yes you are right.
And some others too.
Ioannis
YES... it really worth it...
I got the new Gold version one week ago. The easy of configuration and the new arrays possibilities...
I did found that the new version of MCSP 5.0 was edited and now do not have the option to turn off
the border crossing alerts.Well ... we always had "@ ERRORLEVEL -306".
By the way... where can I find a list of the supported PICS for the Loader ?
I went to Mecanique and I did not found information on that.
Also... the ICD model creator works,but only for the PIC18 family.
Greetings...
Ruben de la Pena Valdes.
What exactly is a conditional config/compilation?
You can write code that will easily compile for different PIC processors and not have to maintain and update separate program files for each processor... since different PIC's often name their registers differently, even though they do the same thing.Quote:
What exactly is a conditional config/compilation?
Here are a couple(3) of examples... This code allows me to use either the 16F690 or the 16F1828.
The first is an example of conditional config... meaning seting the configuration registers
Code:#IF __PROCESSOR__ = "16F1828"
#CONFIG
__CONFIG _CONFIG1, _FOSC_INTOSC & _WDTE_ON & _PWRTE_OFF & _MCLRE_OFF & _CP_ON & _CPD_OFF & _BOREN_OFF & _CLKOUTEN_OFF & _IESO_OFF & _FCMEN_OFF
__CONFIG _CONFIG2, _WRT_OFF & _PLLEN_OFF & _STVREN_OFF & _BORV_25 & _LVP_OFF
#endconfig
#else
#IF __PROCESSOR__ = "16F690"
#CONFIG
__CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_OFF & _MCLRE_OFF & _CP_ON & _CPD_OFF & _BOD_OFF & _IESO_OFF & _FCMEN_OFF
#endconfig
#ELSE
#ERROR "Program does not support " + __PROCESSOR__
#ENDIF
#endif
#msg "compiling for target " + __PROCESSOR__
an example of setting up registers...
An example of clearing the interrupt flag register for two different PICs...Code:#IF __PROCESSOR__ = "16F1828"
AnselA = 0 'and turn off analog
AnselB = 0
AnselC = 0
IOCAF = 0 'clear interrupt flag register
WDTCON=010100 'SET WDT PRESCALER
#ELSE
Ansel = 0 'and turn off analog
AnselH = 0
INTCON.0 = 0 'clear interrupt flag register
#ENDIF
At compile time, only the code that fits your selected processor is actually included in the final compiled code.Code:#IF __PROCESSOR__ = "16F1828"
IOCAF = 0
#ELSE
INTCON.0 = 0 'clear interrupt flag register
#ENDIF