Simulator

[jellis00]

Proteus assumes that anything with a .BAS extension is a PROTON program.
So use .PBP instead for PicBasic Pro programs.

Then you need to tell proteus how to compile a PicBasic Pro program... (Note: this assumes you have PBP 2.60A)

In ISIS, go to the Source > Define Code Generation Tools... menu and click the New button.
Point it to the c:\pbp\PBPMPLAB.BAT file. It will create a PBPMPLAB "tool".
Enter the following fields.

Source Extn: PBP
Obj. Extn: COF
Command Line: %1 -ampasmwin -oq -k#
List File Extn: LST
Then click OK

Attachment 4957

After drawing your circuit with a PIC chip in it ... Save it to a new folder first.
Then go to Source > Add/Remove Source files...
Under "Code Generation Tool", drop-down the box and select PBPMPLAB
Click the New button and either select the .PBP file, or give it a new name and it will create a new file.
AFTER giving it a Source Code Filename ... enter the PIC's part number in the Flags field -p12F683.
Then press OK.

Attachment 4958

To edit the source code, go to Source menu and select the file you specified previously at the bottom.
When you try to start the simulation, it will automatically compile the program if you have changed it.
Or you can select "Source > Build All" and it will compile it even if you haven't changed it.

If the compile succeeds, it will begin running the simulation.
If you selected "Build All" it will show the results of the compile process.

Darrel, I am trying to start using Proteus ISIS with simulator. Followed these instructions of yours and when I do a Build ALL I get the following error:
Processing ..\..\..\PBP26\Ellis_Codes\Temperature\0DisplayLM3 4temp.pbp...
PBPMPLAB ..\..\..\PBP26\Ellis_Codes\Temperature\0DisplayLM3 4temp.pbp -ampasmwin -oq -k# %1 -ampasmwin -oq -k#
\Microchip\MPASM was unexpected at this time.
ERROR: PBPMPLAB.BAT reported error code (255L).
Build FAILED with 1 error(s).

Looked at PBPMPLAB.BAT statements and can't figure out what error 255L is telling me. Can you advise??

[Darrel Taylor]

Normally, you get those kind of paths when you haven't saved the .DSN yet.

Each .dsn should be saved in it's own folder, and the source code should be in the same foler.

[jellis00]

Normally, you get those kind of paths when you haven't saved the .DSN yet.

Each .dsn should be saved in it's own folder, and the source code should be in the same foler.

Double checked that and .dsn file and source code are in the same folder. Still get same errors.
Maybe I should clarify, I am attempting to use Proteus Lite 6.7 to evaluate whether I want to buy VSM Startup Kit or not. I was under impression that I could simulate running my PBP v2.6A code on an 18F2620 model of CPU with Proteus Lite 6.7....not true?? I do notice that BUILD ALL is only option not grayed out...the Debug options are all grayed out, so maybe that means I can't simulate with Proteus Lite 6.7.

[Darrel Taylor]

It's been a few years since I had the Demo version.
So I installed it on another machine.

I do not see any example design files that use an 18F2620.
Which means you would have drawn a new schematic with an 18F2620.

The demo version does not allow you to save new designs, so I think your "Double checked that" may not have included the "save the file first" part.
But it won't let you simulate a new design either.

You can use any of the existing demo designs (without changing the design), and change the .hex file that it executes.
But most of them are 18F452's, and the designs are limited.

[jellis00]

Thanks for that reply, Darrel. I see from your comments now why it wasn't working.
Since I was running Proteus Lite 6.7 and Labcenter doesn't support it anymore, they sold me the Proteus VSM Starter Design Kit (SDK) for their special price of $125. This will at least let me thoroughly evaluate ISIS for all my schematic work and will also at least let me do some simulations for the three MCUs that the SDK supports. I already have it running and have been running and looking at some of the samples to see how the VSM works. Looks like it may be a big help if I later decide to spend the $ and upgrade to the full 18F version of VSM. Since they credit the $125 towards the 18F version it makes is almost affordable.
Which Proteus versions do you use? I tend to use 18F version MCUs so I hope that if I do upgrade that the 18F version is all I would need....your opinion as to whether it would be worth it?
John