Post by thread:MPLAB/MPSIM oddity

I am using MPLAB (now V5) and I often RUN the simulator through many I2C and timing subroutines etc. to get to my breakpoint. I noticed that the simulation runs 3-4 times faster when I'm constantly moving the mouse. Now, I' m paddling with the mouse like crazy and it IS faster. Why is that? How can I fix it/maximize the speed? Djula

Keep your mouse still, there is a software called SPEED! that do this for you. I just don't have the URL but I can send it to you if you want. Friendly Regards Octavio Nogueira =================================================== spam_OUTnogueiraTakeThisOuTpropic2.com ICQ# 19841898 ProPic tools - low cost PIC programmer and emulator http://www.propic2.com =================================================== {Original Message removed}

You can get it from http://www.myke.com/PICMicro/speed.zip -Randy Glenn .....PICxpertKILLspam@spam@techie.com - http://i.am/PICxpert "Is this a wretched demi-bee, half asleep upon my knee, Some freak, from a menagerie? NO! It's Eric, the half a bee!" - Monty Python =========== To unsubscribe, send a message containing the text "unsubscribe PICLIST" to LISTSERVKILLspamMITVMA.MIT.EDU Any questions about the list? http://www.piclist.com/ {Original Message removed}

Djula Djarmati wrote: > > I am using MPLAB (now V5) and I often RUN the simulator > through many I2C and timing subroutines etc. to get to > my breakpoint. I noticed that the simulation runs 3-4 times > faster when I'm constantly moving the mouse. Now, I' m > paddling with the mouse like crazy and it IS faster. Why is > that? How can I fix it/maximize the speed? > > Djula I too, have noticed this bizzare behaviour, in version 4.12.xx as well. If I use the hotkeys to run/halt I HAVE to move the mouse to get the command to take effect in less than a second. Go figure. My guess would be that MPSIM has code that waits on a Winblows message queue with an 'on event blah...' construct. Improperly coded, this wait gets short circuited by ANY event, mouse, keyboard, timer, etc. You're generating lots of 'events' so the background screen updater functions are then not waiting for every step of the simulation, and so you effectively simulate faster. Yeah, it sucks that the simulation runs slower than it needs to. Wouldn't it be nice if your 750Mhz PIII ran the 20Mhz PIC code 100 times faster in simulation than the real processor did, rather than running slower because of the screen updates and flawed coding? -- Robert.Rolf-AT-UAlberta.ca

On Mon, 24 Apr 2000, Robert Rolf wrote: > Djula Djarmati wrote: > > > > Yeah, it sucks that the simulation runs slower than it needs to. > Wouldn't it be nice if your 750Mhz PIII ran the 20Mhz PIC code 100 times > faster in simulation than the real processor did, rather than running > slower because of the screen updates and flawed coding? Do you mean like it does in gpsim? Well, not 100 times unfortunately. But depending on the simulation environment, gpsim can simulate a 20Mhz PIC on a 400 Mhz PII. I could only guess that it's twice as fast on a 750Mhz PIII. http://www.dattalo.com/gnupic/gpsim.html Scott

Hello Djula & PIC.ers, Scott Newell wrote a program a while back to tackle this. It's shareware, and definitely works. To his readme.txt file I can add the following personal comment:- <js comment 20.2.99> The speedup program won't work if asynchronous pin stimulation is ever invoked in the current mplab session. To fix - exit mplab & cycle back to the project again Also.. It doesn't seem to operate if speedup is run before mplab Those who'd like the 15KB zipped file can ask me for it, or try Scott at .....newellKILLspam.....cei.net {Quote hidden}>Date: Mon, 24 Apr 2000 19:18:00 +0200 >From: Djula Djarmati <EraseMEjulianspam_OUTTakeThisOuTEUNET.YU> >Subject: >I am using MPLAB (now V5) and I often RUN the simulator >through many I2C and timing subroutines etc. to get to >my breakpoint. I noticed that the simulation runs 3-4 times >faster when I'm constantly moving the mouse. Now, I' m >paddling with the mouse like crazy and it IS faster. Why is >that? How can I fix it/maximize the speed? > >Djula best regards, John e-mail from the desk of John Sanderson, JS Controls. Snailmail: PO Box 1887, Boksburg 1460, Rep. of South Africa. Tel/fax: Johannesburg 893 4154 Cellphone no: 082 469 0446 email: jsandspam_OUTpixie.co.za Manufacturer & purveyor of laboratory force testing apparatus, and related products and services.

I guees then, I'm a "me too" for the zip file. TIA, Walt... -----Original Message----- From: John [@spam@jsandKILLspamPIXIE.CO.ZA] Sent: Monday, May 01, 2000 9:38 AM To: KILLspamPICLISTKILLspamMITVMA.MIT.EDU Subject: MPLAB/MPSIM oddity Hello Djula & PIC.ers, Scott Newell wrote a program a while back to tackle this. It's shareware, and definitely works. To his readme.txt file I can add the following personal comment:- <js comment 20.2.99> The speedup program won't work if asynchronous pin stimulation is ever invoked in the current mplab session. To fix - exit mplab & cycle back to the project again Also.. It doesn't seem to operate if speedup is run before mplab Those who'd like the 15KB zipped file can ask me for it, or try Scott at RemoveMEnewellTakeThisOuTcei.net {Quote hidden}>Date: Mon, 24 Apr 2000 19:18:00 +0200 >From: Djula Djarmati <spamBeGonejulianspamBeGoneEUNET.YU> >Subject: >I am using MPLAB (now V5) and I often RUN the simulator >through many I2C and timing subroutines etc. to get to >my breakpoint. I noticed that the simulation runs 3-4 times >faster when I'm constantly moving the mouse. Now, I' m >paddling with the mouse like crazy and it IS faster. Why is >that? How can I fix it/maximize the speed? > >Djula best regards, John e-mail from the desk of John Sanderson, JS Controls. Snailmail: PO Box 1887, Boksburg 1460, Rep. of South Africa. Tel/fax: Johannesburg 893 4154 Cellphone no: 082 469 0446 email: TakeThisOuTjsandEraseMEspam_OUTpixie.co.za Manufacturer & purveyor of laboratory force testing apparatus, and related products and services.