Arduino Simulide 1001. slow

SIMULIDE 1001 for Arduino. Many intersting improvements, but very very very very ... SLOW.

In general it should be faster, but depens on the case.

Can you provide an example that runs so slow?

OK, Let me prepare it for You.

I attach the project files. In rality everything works. In the program *.ino it includes the RTC DS3231, so for Simulide only the menu part or setting the time works, enough to see the slowness. This same program is not slow in simulide 04159 for Arduino.

Thanks.

For me the simulation runs at 100%, so the problem is not slow simulation.
Must be some problem whith the Arduino.
I will have a look.

The problem is about I2C.

Probably the fact that RTC DS3231 is not connected is blocking I2C communication.
Not sure if this is a bug or it is how it should work.

Do you have the real harware working?

Nice project btw.

Yes, REAL HARD woks OK, and this same program WORKS FINE TOO in Simulide 04159 for Arduino Nano and UNO. Tray it You in order to test it. I sended to You the total information: Schematic, pictures, etc. I do not think that the RTC affects because it does not woek even during the setting menu.

The fact that the project works faster in 0.4.15 does not necessarily means that 0.4.15 simulation is correct.

I already tested it, and as I said in the previous post, the problem happens at I2C communication with RTC.
Most probably is a bug, but could happen that not having an RTC connected creates some delay.

So the question would be if the real hardware works the same without the RTC connected.

The real hard works FAST with the RTC DICONNECTED from the moment of connection to the power supply.

If I remove the subrutine of RTC in the program, it continues run slow.
It makes sense, because the program only accesses to the RTC when exiting the time setting menu loop and the slowness can be senn in the loop without the presence or the subrutine of the RTC.

The real hard works FAST with the RTC DICONNECTED from the moment of connection to the power supply

Nice to know.
This is definetly some issue with I2C simulation.

If I remove the subrutine of RTC in the program, it continues run slow.

If I remove all calls to RTC, including GetTemperature(), then the program run fast.

It makes sense, because the program only accesses to the RTC when exiting the time setting menu loop and the slowness can be senn in the loop without the presence or the subrutine of the RTC.

In void setup() function there is a call to GetTemperature() which accesses to the RTC.
In void loop() function, switch (systemState), case 0: there is a call to GetRtc() and another to GetTemperature().
Looks like systemState keeps at 0 until you press "Menu" button.

If I compile and run the sketch and don't touch any button:
It is doind a call to GetRtc() aproximately every 500 ms.
And continuous calls to GetTemperature().

That's what made me think about a delay caused by RTC not present.

The funy thing is that it slows down even accessing the RTC just once in setup function.
So when I2C is activated it slows down the execution of the firmware, but not the simulation itself.

Well, If You finaly belive that the slowness is due to the RTC DS3231, I am waiting for it to be included as componnet as soon as posible and thak You very much for your attention. I keep encouraging you to improve such a good simulation tool as is Simulide, Thank you.

Well, If You finaly belive that the slowness is due to the RTC DS3231, I am waiting for it to be included as componnet as soon as posible

After you tested it in hardware and working ok, this hipotesis is discarded.
And that it slows down even accessing the RTC just once confirm that the problem is not the lack of the RTC.
This is definetly some issue with I2C simulation.

Anyway There is DS1307 already in development, and DS3231 probably will come soon as it is very similar.

RTC3231 Is the one with the most accuracy, that is why I use this one. DS1307 is outdated. Also the RTC3231 offers more physical options of size and connectivity.

And finally......... Issue solved at Rev 732.

Fine, Muchas Gracias.