View Full Version : New PBP version - Gold version - Is it really worth it?
financecatalyst
- 30th July 2011, 23:49
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
rsocor01
- 31st July 2011, 03:48
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
HenrikOlsson
- 31st July 2011, 09:14
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:
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
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.
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.
mister_e
- 31st July 2011, 09:33
Only for the new
#CONFIG
#ENDCONFIG
option it worth it. BTW 50$ is nothing too keep the development alive.
In addition, the PM assembler is no longer supported
It's about time :D There's NO advantage to use PM over MPASM anyways.
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.
cncmachineguy
- 31st July 2011, 10:57
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!!!
ScaleRobotics
- 31st July 2011, 15:30
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
Heckler
- 31st July 2011, 16:25
Configuration settings listed for each supported deviceWhat do you mean by this? Where do I find this configuration settings listing?
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??
HenrikOlsson
- 31st July 2011, 16:44
In the Migration notes (http://pbp3.com/downloads/Migrating%20existing%20programs%20to%20PBP3.pdf) 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!
Darrel Taylor
- 31st July 2011, 18:01
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
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.
It may even be possible for 3rd party programmers to write new commands and make some money.
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.
financecatalyst
- 1st August 2011, 00:22
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)
HarryPow
- 8th August 2011, 07:55
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
pedja089
- 8th August 2011, 13:03
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.
mister_e
- 9th August 2011, 17:54
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:
mister_e
- 10th August 2011, 00:23
Something is slick now... I did it manually before but...
TMR1 VAR WORD EXT ; Joined SFR, BANK0
TMR1L VAR BYTE EXT ; BANK0
TMR1H VAR BYTE EXT ; BANK0
Cool, no longer need to do it manually :D
prstein
- 10th August 2011, 05:27
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
Ioannis
- 10th August 2011, 10:55
I did not got it. Wasn't this available to the previous versions?
Something is slick now... I did it manually before but...
TMR1 VAR WORD EXT ; Joined SFR, BANK0
TMR1L VAR BYTE EXT ; BANK0
TMR1H VAR BYTE EXT ; BANK0
Cool, no longer need to do it manually :D
Ioannis
mister_e
- 10th August 2011, 11:42
Indded, but you needed to manually enter the TMR1 line... big deal...
Ioannis
- 10th August 2011, 12:00
Oh, yes you are right.
And some others too.
Ioannis
Ruben Pena
- 15th August 2011, 03:13
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.
enauman
- 8th October 2011, 00:44
What exactly is a conditional config/compilation?
Heckler
- 8th October 2011, 01:34
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.
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
#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...
#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
An example of clearing the interrupt flag register for two different PICs...
#IF __PROCESSOR__ = "16F1828"
IOCAF = 0
#ELSE
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.
Powered by vBulletin® Version 4.1.7 Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.