Letter to Mecanique (MicroCode Studio)

I just thought I'd share something I sent to them:

Quote:

---

Beginner entry PIC in free version of MicroCode Studio‏

Hi,

Would it be possible to include the PIC 16F886 please?

This would make things so much easier for beginners. The entry level version of Pic Basic Pro (Experimenter) does not support the PIC 16F887.

I wouldn't ask you to remove the 16F887, 'cause then that would leave those that are using that PIC behind.

I know there's the PIC 18F25K20 that is common, but that's an 18F model with the more complicated configs. The 16F models are so much less intimidating to new users.

Thank you for your time, and have a nice day!

Demon,
and everyone on the Crownhill PBP forums!


(this issue came up as I was describing the minimum software and hardware requirements to get into PIC programming to a clerk at a local electronic store)

---

I know this doesn't affect most of us, but I'm sure a few of the new folk that have come on board since the 18F came out would have found it a bit easier to get going.

With the popularity of the Arduino products, it wouldn't hurt to make things as easy and cheap as possible for people to try out PICs.

Robert
:)

HUH?

The PIC's supported by the different versions of PBP3 are controlled by PBP3, not MicroCode Studio.
MicroCode Studio simply puts a list of the supported devices in the drop-down box.
For the Experimenter version, that list is supplied by the 2.DEVICES file in the PBP3 folder.

The Experimenter version has always supported the 16F886, and the 16F887 has never been included.

As of yesterday, PBP3 is now at version 3.0.5.x
Several chips have been added to the EXP. version.

Download the latest version from ...
http://pbp3.com/downloadtrial

LOL You understood it the other way around like Mecanique did. :D Of course I'm not asking them to change PBP, that's out of their hands. Or is my wording wrong and I can't see the forest?

My title was: Beginner entry PIC in free version of MicroCode Studio‏
And my opening request was: Would it be possible to include the PIC 16F886 please?

I was asking if they could change their own product to help new folk that want to get in at minimal cost.

This MeLabs page
http://pbp3.com/devicelist?source=menubarDevice
lists 16F886, 18F2550, 18F25K20 and 18F25K22 for Experimenter.

This Mecanique page
http://www.mecanique.co.uk/code-stud...ICDModels.html
lists 16F877A, 18F25K20, 16F887, 18F452 and 18F4520 for the free version of MCS.

The only common PIC is the 18F25K20, and we see plenty of posts here of new people that are a bit lost in CONFIGs. Shoot, even some regulars got confused. Of course it's possible that the web information is obsolete, but I had nothing else to show him while googling on my phone while at the store.

Robert


EDIT: Oh wait:

Quote:

---

MicroCode Studio simply puts a list of the supported devices in the drop-down box.

---

Are you saying PBP decides what the free version of Microcode Studio can support?

Robert,
The page you link to on the Mecanique website lists the available ICD models for MCS - not for which devices you can compile.

/Henrik.

Quote:

---

Are you saying PBP decides what the free version of Microcode Studio can support?

---

MCS is just an editor as is notepad. Has nothing to do with the way PBP works or what parts can be used... just like notepad.

While we are on the subject of MCS...

Does anybody know how to make the program labels (ie. "Main:", "Routine1:" ect.) a different color??

I have always wanted to make my program labels stand out better but have not been able to figure out a way.

thanks

Tool bar
View
Editor Options
Highlighter (tab)

Yea... I had found the "highlighter" section...

I just wish Mecanique would make it so the program labels could be made their own separate color.

thanks though.

D'oh, I just noticed Microcode Studio Plus v2 has a PIC.INI file that we can add whatever PIC we want from our MPASM folder. argh...

Robert

EDIT: Thanks Steve for pointing me in the right direction:
http://www.picbasic.co.uk/forum/show...2923#post22923

yes ...

but microcode example for program labels still is ... " LOOP:" ... Booooooo !

still no way to make it like we can with MPLAB Editor ...

Alain