List of Feature Requests.

I think it is a good idea to keep a list of feature requests, so everybody can see if a request is already done or not.

I will update the list in this post and do a poll time to time so Patrons can vote and choose which features should be implemented first.

Components:
* Incandescent lamp.
- 16-segment display.
- Digital Potentiometer
*- Digital Thermometer (DS18B20 1-Wire ).
- Real Time Clock (RTC DS3231).
- Rechargeable battery.
* Transformer.
- Solar panel.
- Optocoupler.
- Rotary switch
- Nokia 1616, 6100 lcd.
*- I2C IO Expander interrupt pin.
- DC motor with encoder
* Controlled Voltage and Current Sources (vcvs, vccs, ccvs, cccs).
- xpt2046 touch controller.
- Diode bridge.

- Wattmeter.
- Cos(phi)meter.
- Simple spectrum analyzer (via FFT).
- Induction motor.

Features:
- Projects.
- Point Grid.
* Hotkeys to create components.
- Function truth table.
- Oscope: XY composition mode.
- Wave Generator: phase parameters.
- Logic Analizer protocol decoder.
- Group Components and group graphical transformations.
- Automate Tunnels from wires.
- Visualize Component current and power at mouse hover.
- Wires configurable (thickness & color).
- 4 wire joints.

Please add 8051 family of microcontrollers as well.

asmitahase wrote:Please add 8051 family of microcontrollers as well.

This would be great, but a huge task.

I'm open to implement it, but my knowledge about this subject is not enought.
Maybe if someone is interested we could collaborate.

First we need an existing open source multiplatform simulator for 8051 devices... any suggestion?

I'm very interested in new components to use in my remote classroom. Things like rotary encoder, dc motor, joystick and TFT display.

I think I can start programming some of those. The rotary encoder, for example, could be a QDial with 2 output pins.

But I have a few questions:

• Would you like some contribution? Should I fork the project and make a pull request?
  
• Is there a chance we can implement them in 1 or 2 months?
  
• Should the rotary encoder be in the Switch category, and then be connected to power rail and ground? Or is it better to put it as an Active component, with its own source?
  

Hi.

I think I can start programming some of those. The rotary encoder, for example, could be a QDial with 2 output pins.
You can just copy some other component with dial and 2 pins, like variable resistor and add the encoding functionality.

Would you like some contribution? Should I fork the project and make a pull request?
Of course any contribution is very wellcome.
I think you can just implement a component and send me the files (just the new files).

Is there a chance we can implement them in 1 or 2 months?
Dc motor is already implemented in version 0.4.14
Rotary encoder and joystick are not too difficult.
TFT display depends on how complex it is, but implementing these devices ussually require a lot of work, even for a very simplified version maybe something like 100 to 200 hours.
As an example: ssd1306 oled (only spi) took me more than 100 hours of work. And i guess most tft displays are way more complex.
Do you have a model number or datasheet?

"Should the rotary encoder be in the Switch category, and then be connected to power rail and ground? Or is it better to put it as an Active component, with its own source?"
That's a decission to make...
Will the power voltages change?
If yes then better having power pins or a property to change those values (or both).

Dc motor is already implemented in version 0.4.14

Great! Thank you!

I think you can just implement a component and send me the files (just the new files).

Alright! I'll start working on the rotary encoder and the joystick, and will send you the files when I'm done.

TFT display depends on how complex it is, but implementing these devices ussually require a lot of work, even for a very simplified version maybe something like 100 to 200 hours.

Yeah, that is tough. And you've done a great job so far – there are not many good Arduino simulators out there. So I've just created a Patreon account and subscribed to your $10 plan. But no pressure, take your time. A simplified version might be good enough for my students.

As an example: ssd1306 oled (only spi) took me more than 100 hours of work. And i guess most tft displays are way more complex.

Maybe they have some similarities that help the next implementation? Both ILI9341 and SSD1306 have Adafruit libraries that use SPI commands. ILI9341 could use the same QImage, but with variable colours for each pixel.

Do you have a model number or datasheet?

• Here is the product page.
  
• Here is a datasheet PDF.
  
• And here is the Adafruit_ILI9341.h, as a quick guide to SPI addresses. You can compare it to Adafruit_SSD1306.h.
  

Thank you very much for your support!
I'm having a look at ILI9341.

Maybe they have some similarities that help the next implementation? Both ILI9341 and SSD1306 have Adafruit libraries that use SPI commands. ILI9341 could use the same QImage, but with variable colours for each pixel.

I made a mistake in my last post: SS1306 implementation in simulide is only I2C.
I can reuse some parts of SS1306, but the hard part is implementing all the commands.
ILI9341 has more that 70 commands, some of them are not really needed, but at least 40 or 50 will be needed.

can we have rechargeable battery ? its very help full for small projects , we can indicate battery is charging or discharging

can we have rechargeable battery ? its very help full for small projects , we can indicate battery is charging or discharging

Added to the list.

First of all, thank you for this awesome simulator!
I'm a teacher and I'm amazed by the complete MCU list!
I have electrical engineering students as well and it would be of interest for them and colleagues to have some more meters as follow:
in order of relevance
- Wattmeter
- Cos(phi)meter
- Multitrack scope with XY composition (lissajous)
- a simple spectrum analyzer (via FFT)

as well as some more power stuffs:

- a sine generator, with amplitude, frequency and phase parameters (I know we have the wave, but is more like a function generator than a supply source)
- a simple transformer model (mono and three-phase)
- an induction motor model
I saw that dc motor will appear in the new release!

Thanks again for your great work, and I'll be happy to help in someways!

Hi. Thanks for your kind words.

Yes, simulide has not very much about AC by now, it it more oriented to basic electronics and microcontrollers.

Thre are some features that could be included in current components, like scope XY composition mode or phase parameters for wave generator.
The rest would be far away in the list of priorities, but could be implemented with some collaboration.

If someone is willing to implement the functionality (even is pseudocode) i could bring it into simulide.

As for collaboration:
- At the moment I'm translating the simulide.ts file into the Italian language (I'm on my way...).
- I could involve my Institute as "Patreon" for the project
- I could Unleash some of my students-gargoyles for the creation of some new components. In order to make them effective faster, beyond the examples, there exist a quick reference guide about it? (Not the language but the structure/parts needed)

about the second point, I must get the agreement of the Director before...

- At the moment I'm translating the simulide.ts file into the Italian language (I'm on my way...).

That's great, i was missing Italian in the list of laguages.

I could involve my Institute as "Patreon" for the project.
about the second point, I must get the agreement of the Director before...

That would be great too, but there is no problem if it doesn't happen.

- I could Unleash some of my students-gargoyles for the creation of some new components. In order to make them effective faster, beyond the examples, there exist a quick reference guide about it? (Not the language but the structure/parts needed)

There is not reference guide.
Simulide is evolving quite fast, any guide would probably become obsolete in a few months.
Indeed many components made for last release will not work in the version i'm working right now.

I think the first step would be a basic design:
- Type of device: digtal/analog, etc.
- Number and type of pins.
- An idea of how should it work:
   Read voltages from which pins.
   What calculations should be done with that.
   What kind of output.
   Does it need some timing? etc.
- Also how it should look.

Then we can talk about the best solution for that case.
Maybe i can provide the basic structure of the component to start working and later discuss any issue that can arise.

Hi SimulIDE support,

First I would like to thank you for developing a free Arduino simulator of high quality, I have been using it for some time now and I was wondering if you know a way to add an Arduino Due to your Arduino library or if I can use this post to request if you can add an Arduino Due in future versions. thank you!

Hi.

I was wondering if you know a way to add an Arduino Due to your Arduino library

The only way that comes to my mind is writting a simulator for the Cortex  -M3 CPU.
Then writting models for all the perifericals and controllers: Timers, ADC, DAC, CAN, USB, MCI, RTC, RTT, HSMCI, SMC, DMAC, SDRAMC, PWM, PIO, PMC, PDC, EMAC, TRNG, USART, SPI, TWI...
Then make all work together.

It would be great, but these microcontrollers are complex.
For now there are no plans to add this Arduino.

Hello, Thank you for this exciting simulator!
Perhaps it would be useful for the application:
Reversible cyclical player (1..16)-bit digital sequence saved in text file or VCD files. It will be convenient to simulate a signal from an external physical device. Based on it, create other elements, such as an rotary encoder.

Excuse my Google translation.

Reversible cyclical player (1..16)-bit digital sequence saved in text file or VCD files. It will be convenient to simulate a signal from an external physical device.

I have something like this in mind.
But still thinking about the best solution.

Such a device can be easily made in the form of a subcircuit. I'll try to implement it. I have been thinking about creating such a device for a long time.

Спасибо Вам большое за этот список моделей. Кое что у вас уже работает в последней сборки  R779 что вы дали.
Я хотел бы конечно в первую очередь видеть такие модели :
SCR,DIAC, симистор
Оптопары - с логическим выходом, c выходным биполярным транзистором, c выходом на высоковольтный динистор.
Цифровой термометр DS18B20
Лампа накаливания - с сопротивлением холодной спирали и горячей.
Двигатель коллекторный однофазный с внутренним датчиком ХОЛЛА  - работа как на переменном так и постоянном токе. ( такие которые стоят на эл. инструменте ) с якорной катушкой и катушкой возбуждения с редактированием всех параметров.

И конечно хорошо все делать не сразу. Постепенно вводить эти модели.
Пожелаю ВАМ успехов по модели ATmega 8. Наверное все таки она заработает в следующей сборке.
За модель трансформатора сразу не советую браться. Их много типов. Очень много параметров надо вводить что бы имитировать реальный в железе. Как низкочастотных так и импульсных.

Пожелаю ВАМ успехов по модели ATmega 8. Наверное все таки она заработает в следующей сборке.

Atmega8 was implemented recently, most periferical only the basic implementation.
Some things are working, some other things are not working.

Now what we need is good testing:
- Create test units for each functionality one by one, as explained in this post:
https://simulide.forumotion.com/t378-testers-for-microcontrllers-simulation-needed

By now the only one that can do the C++ part efficiently is me.
Creating test units many people can do.

So I'm focused in the coding part and hopefully someone will contribute more test units.
Fizic_S and you have contributed some firmwares that don't work, but by now I couldn't find the cause of the problems.

Since I just have seen, that the digital potentiometer is already on the list, I want to "add some requirements" based on my wish list:
- number of steps as a parameter
- min / max resistance as a parameter
- linear / log as a parameter
- memory function for wiper position (activatable)
- Controllable via I2C (SCL, SDA, A0.. A2) or incrementally (pins: Up/Down, CLocK, ChipSelect). Would be better to have individual components for each interface..

Real live examples are available e.g.

TI:
https://www.ti.com/de-de/data-converters/digital-potentiometer/products.html

Microchip:
https://www.microchip.com/en-us/products/data-converters/digital-potentiometers

Since my student already needed such a circuit, me and my colleague tried our best to create a discrete one and ended up with the following circuit:
https://wiki.mexle.org/_media/microcontrollertechnik/digitalpotivarrz_02.sim1

Since I just have seen, that the digital potentiometer is already on the list, I want to "add some requirements" based on my wish list:
- number of steps as a parameter
- min / max resistance as a parameter
- linear / log as a parameter
- memory function for wiper position (activatable)
- Controllable via I2C (SCL, SDA, A0.. A2) or incrementally (pins: Up/Down, CLocK, ChipSelect). Would be better to have individual components for each interface..

Ok, that will be useful.

I think that the first implementation will be a simple generic digipot with "parallel" interface (bcd) with the first 4 features in your list.
Then creating subcircuits to add a communication interface.
It would de nice to add some features to "I2C to Parallel" component that allow to implement different behaviors.

Since my student already needed such a circuit, me and my colleague tried our best to create a discrete one and ended up with the following circuit:

nice, that's an smart solution with minimum number of components.

I have created a simple digital potentiometer with a parallel interface TPL8002-25. You can download it here:

https://simulide.forumotion.com/t131-new-subcircuits-for-simulide-v-0-4-15-and-higher#2369

arcachofo wrote:

asmitahase wrote:Please add 8051 family of microcontrollers as well.

This would be great, but a huge task.

I'm open to implement it, but my knowledge about this subject is not enought.
Maybe if someone is interested we could collaborate.

First we need an existing open source multiplatform simulator for 8051 devices... any suggestion?

There are many freeware 8051 simulators, but they are not open source   .
The ones I've found open source are gSim51 (http://gsim51.sourceforge.net/) and emu8051 (https://github.com/jarikomppa/emu8051), but they are not multplatform.

I hope someone can help more.

There are many freeware 8051 simulators, but they are not open source  Sad .
The ones I've found open source are gSim51 (http://gsim51.sourceforge.net/) and emu8051 (https://github.com/jarikomppa/emu8051), but they are not multplatform.

I hope someone can help more.

8051 is already implemented in simulide (for more than 1 year).
But a bit abandoned for some time, currently I don't even know what is working after many changes in MCU simulation.
It needs someone to test it...