I am impressed too. By the price also!
It seems that they do not support PBP. I know hex files can be imported. But not Basic files, right?
Ioannis
I am impressed too. By the price also!
It seems that they do not support PBP. I know hex files can be imported. But not Basic files, right?
Ioannis
Hi, Ioannis
COFF files also can be imported ... I was told it was better for debugging tools use ...
BUT I never could make the RTC chips work in their simulations ... always read "0" ( despite screen shows good data ) ... but the " live " circuit runs perfectly well ...
ISIS do not like mixing analog and digital circuitry nor ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Nice find, but would be nice if it had loads of more components were available. I too experienced issues even after installing the J# update (I already have up to date .Net etc) in that when adding a link the layout area went black and Vista reverted to basic colours. The program then became non-responsive.
On the subject of breadboarding, anyone know of an application that can take an Eagle schematic and lay it out automatically on stripboard. I've used DIY Layout creator, which is a manual process, but this leads to human error creeping in a when mixing 240V with 5V dc there could be nasty consequences...
hello
As I am not super fluent in english, could you check my affirmations ?
1/ Isis ask for HEX file, we can't feed the simulator with PBP files ?
2/ we can see datas from PIC registers (trisa , etc ..) but it is not possible to see the datas from our VARIABLES
lest say TOTO var BYTE and the big application like TOTO = TOTO + 1 !
for hardware simulation, it is super nice (voltmeter, oscillo, LED, relays, etc ..) but in my case (sending in serial mode
21 bits with clock and enable line ... using Three outputs pins from a PIC) is it not so easy to see if everything is OK
and in front of that, I have some Bitwise operation on the datas line , that why I try to see my TOTO variable !
that's all folks
Francois
for the moment I will continue with my breadboard ...using debug, or LCDOUT or serout ... but normally the PIC
is a 8 pins ... so I must devellop on a big one first ... that why I try to get a Software simulator.
best regards,
If you have PBP 2.60A, then you can use .pbp files directly in Proteus.
Or you can use Proteus inside of MPLAB with more debugging options.
With previous version of PBP, you can only simulate the .HEX files.
DT
OK darrel
you know everything !
and we got answer as soon as the enter key is done !
about this sentence
"Or you can use Proteus inside of MPLAB with more debugging options."
Mplab is too complicated for me ... may be I'm too old now "$3E" years old ! hi ...
best regards,
francois
just one question (off topic) what about Mélanie ?
She is still in the support group ?
I always appreciated her support way of life.
hello 23h35
I spent hours with the big BLINK application (bas and pbp under Pic Basic PRO 2.60A)
with ISIS version 7.7 SP2 without succes !
he didn't accept pbp extension
simulation is working (LED blinking), but I can't see any Basic line to put breakpoint and display my variable (compteur)
nb: I got this INFO message at start time ! (speaking about PROTON ???)
here is my big application :
' Example program from manual to blink an LED connected to PORTB.3 about once a second
compteur var byte
cont: High PORTB.3 ' Turn on LED connected to PORTB.3
Pause 500 ' Delay for .5 seconds
Low PORTB.3 ' Turn off LED connected to PORTB.3
Pause 500 ' Delay for .5 seconds
compteur = compteur + 1
Goto cont ' Go back to loop and blink LED forever
End
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
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.
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.
On Sunday I will try to make a video of the process.
Going Kart racing tomorrow at Unser's in Denver.![]()
Need some sleep first. And some Advil after ... OK, several Advil.
DT
Darrel, I have Proteus VSM SDK working now. However, when I run a simulation in the debug step mode I don't see variables listed in the Variables Window. In checking the VSM help files it says that most COF files from compilers will support the Variables Window. Does the PBP 2.6C compiler create a COF file that will let Proteus VSM show the variables in the program in the Variables Window??
John
Yes, unfortunately the variables don't show when simulating directly in ISIS.
But if you run Proteus as a debugger in MPLAB 8 the watch window will show the variables.
MPLAB uses the same .cof file, so it's not currently known why they work in MPLAB and not ISIS.
Since you can have as many serial lcd's or virtual terminals as you want, it easier to just put a few statements in your program to spit out the variables at key points.
I don't really miss the variable window too much.
Last edited by Darrel Taylor; - 29th March 2012 at 01:21.
DT
Bookmarks