A header wizard

[mackrackit]

Leave it to Darrel to be a couple steps ahead of us.
Time wise I probably would not get much done before Darrel's (??) program comes out. So I will wait some.
Who know, maybe it will be open for tweaks. Or not have everything we have talked about. If not then.... We fill the gaps.

What else could we do like this? I like the idea of an open community project.

[cncmachineguy]

Thanks Darrel!?!?!? -lol really that is good news. I don't know if I understand from the breif description if it does all we want, missing seems to be initial I/O pin setup. But alas, we will have to wait and see.

As for the community project, that was my 1 big idea. But I am open to any others. another big question for me will be to pay or not to pay, that is the question. Darrel clearly provides us with GREAT code to use as we see fit. So if he IS going to be the author, I would feel compelled to pay some amt for it. Now if he just has a heads up on an update from the PBP folks, well I just bought mine, I would hate to have to give it up for an update this soon.

Guess we wait. In the meantime, I still get to learn python, and that by itself is awesome for me. I may still persue daves efforts as a realtime puzzle to practice with.

[mackrackit]

Here is another one to practice with
http://www.picbasic.co.uk/forum/showthread.php?t=10381
It has some problems the way it is written. Pointed out in the thread. I just never got around to fixing it.

It would be a good stand alone program, command line or GUI, to practice with.

[malc-c]

Here is another one to practice with
http://www.picbasic.co.uk/forum/showthread.php?t=10381
It has some problems the way it is written. Pointed out in the thread. I just never got around to fixing it.

It would be a good stand alone program, command line or GUI, to practice with.

Nice - just tested it with the latest version of my thermostat project -



Very useful app - thanks Dave

[ScaleRobotics]

The *.dev files come with MpLab IDE. I believe the only way to get Mpasm is to download the Mplab IDE. So, everyone that selects Mpasm should have one version or another of Mplab Ide, and the associated files. There are also some other usefull (depending on how complex you want to go) info. This area has pin # information: C:\Program Files\Microchip\MPLAB IDE\VDI\XML\PIC16 . Images could be "mapped" to show labels for pins, etc. Images are here: C:\Program Files\Microchip\MPLAB IDE\VDI\Images

I guess it is both good and bad to have it dependent on Microchip. If they end support, then your work needs to be re-worked. However, the updates being dependent on what mpasm has to work with seems like a good idea. You immediately see if the mplab ide version you have does not support your chip, does not require programmer intervention to add chips. But of course there are many ways to do it, all with advantages, and disadvantages.

Walter

[cncmachineguy]

Back when I played with VDI, I thought I had found a goldmine for pic setup. I was sad to discover they didn't support 16f818 or 16f676. I then figured out it just didn't support smaller chips. It seemed it was developed to help with larger more powerful stuff.

That said, its nice to know there is still support stuff shipping with mplab. I would be concerned how long that will continue. Like when the install won't fit on a CD anymore, what will they chop to squeeze in on.

As for general support of MPLAB, I can't imagine they would stop that. After all, thats what allows new customers to try their product out, and allows the seasoned vets to continue. Not to mention, all the third party folks who depend on it.

Now if the *.dev files are only required for VDI, then maybe they will cease at some point. But my vote is, for now, we take full advantage of what they offer.

[mackrackit]

I use this when I do ASM on Linux.
http://piklab.sourceforge.net/index.php
I do not see where it uses the *.dev files but it does use the *.inc files. Maybe MicroChip does not care? As long as we give credit where do.

I suppose when MicroChip quits supporting the files and/or does not like what we are doing it will be time to move on to another chip.