Request verification if UART interrupts are simulated...?

[chicoDaMan]

Hi all -

Using the Human Interface Injector and an 18F2620 internal UART I can poll the UART and receive the data as entered from the Injector on the keyboard, so I know data is getting to the chip in Flowcode and the chip UART is functioning.

But I can't get the Flowcode simulation to generate an interrupt on the injected data.

Can someone verify that this is a functional feature within Flowcode V7 or not?

Thanks...

[QMESAR]

Hi
As far as I know Interrupts are not simulated use hardware to test your Interrupts

[chicoDaMan]

OK thanks. It wasn't working so what you say makes sense.

I redirect my Flowcode C code output to MPLABX and simulate with Proteus...the UART interrupts work fine with those tools.

[QMESAR]

I redirect my Flowcode C code output to MPLABX and simulate with Proteus...the UART interrupts work fine with those tools.

Proteus is a very good simulator it also has things that does not work 100% but in general it is a very good simulator

[chicoDaMan]

I redirect my Flowcode C code output to MPLABX and simulate with Proteus...the UART interrupts work fine with those tools.

Proteus is a very good simulator it also has things that does not work 100% but in general it is a very good simulator

Yes. I'm amazed at how useful and accurate Proteus is and surprised on the rare occasions when it doesn't simulate correctly. For me it's far more efficient to first design and tweak with Flowcode and Proteus than with Flowcode and prototype hardware that I build...the inevitable design revisions and test jigs and rewiring can all be done in a fraction of the time that the prototype fabrication takes. It's nice to have the actual prototype work 100% when it's built...something that rarely happens without prior simulation.

Flowcode is an impressive tool as well. My designs are better thought out from the beginning due to the visual flowcharting, and coming back to an older project is so much easier because the Flowchart provides accurate and useful documentation of the code. I'm an accomplished C coder but use Flowcode often.

[QMESAR]

For me it's far more efficient to first design and tweak with Flowcode and Proteus than with Flowcode and prototype hardware that I build...the inevitable design revisions and test jigs and rewiring can all be done in a fraction of the time that the prototype fabrication takes.

I agree we have reduced development time by at least 40% by using mixed mode simulation in conjunction with the Analog simulator in Proteus the first proto-types run and then we build upon that to the production releases