Flipping the Oscilloscope Horizontally and About its 5th Pin

SimulIDE_1.0.1-R1374_Win32

There is a minor bug about the appearance of the oscilloscope when it is flipped horizontally. Its channel’s labels and the word ‘Expand’ are also flipped horizontally.
By the way, flipping it horizontally could be useful sometimes to let its connections to certain nodes on the circuit be clearer.

For instance, flipping it vertically is not practical/important. Therefore, the orientation of the writings on it, in this case, is not important as well.

About its 5th pin, I assumed it is for its reference voltage. And if it is not connected to any node on the circuit, its reference voltage is GROUND by default. Is this true?

Thank you.

There is a minor bug about the appearance of the oscilloscope when it is flipped horizontally. Its channel’s labels and the word ‘Expand’ are also flipped horizontally.

I will try to solve it.

SimulIDE_1.0.1-R1386_Win32

[1]
I guess fixing the flipping of the oscilloscope is not important now. I even suggest, in case it is easy to do, removing its two options of flipping (H & V) instead of fixing them, to save time for the time being in the least.

[2]
As you know, on a real digital oscilloscope, setting the’ Time Division’ is independent of triggering. And it has a fixed number of scales/bands (from second to nanosecond for example).
Also, setting the ‘Time Position’ is made by varying the position of the triggering edge (if it exists) on the displayed time scale/band.

Back to our actual oscilloscope, I wonder if it is possible (for example) to monitor clearly the pulse width (about 200us) of a periodic narrow pulse (50Hz), as it could be done on a real one.

Thank you.

As you know, on a real digital oscilloscope, setting the’ Time Division’ is independent of triggering.

I don't understand what you mean, in simulide the time division has nothing to do with trigger.

And it has a fixed number of scales/bands (from second to nanosecond for example).

There are many oscilloscopes out there, some have fixed number of scales and some don't.
In any case I don't see the advantage of limiting the time division to some fixed values.

Also, setting the ‘Time Position’ is made by varying the position of the triggering edge (if it exists) on the displayed time scale/band.

These are two different things.
With time position you can move back and forth more than 1 wave lenght along the entire data set.
By now the triggering level is not editable in simulide.

Back to our actual oscilloscope, I wonder if it is possible (for example) to monitor clearly the pulse width (about 200us) of a periodic narrow pulse (50Hz), as it could be done on a real one.

Why not?
Just set the trigger to that channel and set a time division around 200 us.
What problem do you find to do what you want?

arcachofo wrote:

Back to our actual oscilloscope, I wonder if it is possible (for example) to monitor clearly the pulse width (about 200us) of a periodic narrow pulse (50Hz), as it could be done on a real one.

Why not?
Just set the trigger to that channel and set a time division around 200 us.
What problem do you find to do what you want?

Perhaps it is just me and I don't know how to explain. The only thing that works right is that the settings on its right side are adjusted well automatically.

Always on my side, these 4 settings cannot be adjusted manually, like typing 2 0 0 u s , as you suggested. And doing it by using the up/down arrows is not easy at all and the debugger should be stopped first to let them respond. But by running again the debugger the 4 settings will be 're-adjusted' automatically and there will be no way to change them.

I mean, you surprised me when you suggest:
"set the trigger to that channel and set a time division around 200 us." because this is not possible with SimulIDE_1.0.1-R1386_Win32 running on Windows 7 in the least.

The only thing that works right is that the settings on its right side are adjusted well automatically.

Setting the "Auto" to some channel will scale the view to the wave length of that channel.
While "Auto" is active you can't change setting for that channel, because it will auto-scale again to fit to the wave length.

So to edit settings you need to deactivate "Auto".

And I don't understand why you say the only thing that works right is Auto.
If you set Time Division to a certain value instead of activating Auto the view will scale to that setting.
Same for all other settings.

arcachofo wrote:

The only thing that works right is that the settings on its right side are adjusted well automatically.

Setting the  "Auto" to some channel will scale the view to the wave length of that channel.
While "Auto" is active you can't change setting for that channel, because it will auto-scale again to fit to the wave length.

So to edit settings you need to deactivate "Auto".

And I don't understand why you say the only thing that works right is Auto.
If you set Time Division to a certain value instead of activating Auto the view will scale to that setting.
Same for all other settings.

Only now I discovered that the units of these settings are not supposed to be changed directly. They are adjusted automatically according to the actual one (as ms, us...) and its new entry (a decimal number).

And what puzzled me the most is that I didn't expect that typing every digit may take a couple of seconds before it is displayed on the small white box (of a setting).

Therefore, we may say that my questions here are answered.
Thank you for being patient.

As a side note, if it were my program, I let 'Auto' adjust the 'Volt Div' only and 'Trigger' the 'Time Div'. Then, the user can re-adjust them manually if necessary.

Only now I discovered that the units of these settings are not supposed to be changed directly. They are adjusted automatically according to the actual one (as ms, us...) and its new entry (a decimal number).

Sorry I didn't understand this.

And what puzzled me the most is that I didn't expect that typing every digit may take a couple of seconds before it is displayed on the small white box (of a setting).

This is weird, typing should be immediate. Never heard about something like this.

arcachofo wrote:

Only now I discovered that the units of these settings are not supposed to be changed directly. They are adjusted automatically according to the actual one (as ms, us...) and its new entry (a decimal number).

Sorry I didn't understand this.

In this case, may you tell me, step by step, how, on your side, you can change, for example, 4.000 ms to 125 us.

On my side, I have to delete 4.000 first (digit after digit or by the 'Delete' key after selecting them all by the mouse). Then, I press '0', '.', '1', '2', '5' while the unit 'ms' is displayed. By pressing 'Enter', I get 125.0 us ('ms' becomes 'us' automatically).
By curiosity, I re-tried this for 100 us. In this case, I got 0.100 ms sometimes instead of 100.0 us (it seems that 'ms' may not need to become 'us' always).

And what puzzled me the most is that I didn't expect that typing every digit may take a couple of seconds before it is displayed on the small white box (of a setting).

This is weird, typing should be immediate. Never heard about something like this.

I tested this now. The delay seems normal! So, I think when the delay was rather long, a certain application which I wasn't aware of was running in the background.

In this case, may you tell me, step by step, how, on your side, you can change, for example, 4.000 ms to 125 us.

If I want to set exactly 125 us I do like you did.
Most of the times I don't need an exact time division so I zoom in with the mouse wheel (<1.0.1) or use the dial.
Or first zoom in with the mouse then set an exact value.

Note that zooming with the mouse can change the time position if there is no trigger.

arcachofo wrote:

In this case, may you tell me, step by step, how, on your side, you can change, for example, 4.000 ms to 125 us.

If I want to set exactly 125 us I do like you did.
Most of the times I don't need an exact time division so I zoom in with the mouse wheel (<1.0.1) or use the dial.
Or first zoom in with the mouse then set an exact value.

Note that zooming with the mouse can change the time position if there is no trigger.

Thank you for the hint about using the mouse.

I tested it now after running the debugger and let it pause at a breakpoint.
I noticed that the mouse wheel works as the small up/down arrows (also the up/down keys on the keyboard) do. But the three methods stop at 0.000 (the lowest limit) while the scale unit (as 'ms') is fixed.

If I enter 0.100 (with the existing 'ms' unit, equivalent to 100us) and increase it (as to 1.100 ms or higher), decreasing it will return us to the previous lowest limit (0.000 ms).

A side note, I recall I saw 0.125 ms changed to 125 us in one of my previous tests in the least. Now, no matter what I do, also with or without activating the debugger, I can't make the unit 'us' appear again! Obviously, this is not important, speaking practically. I just tell you what I notice.

I noticed that the mouse wheel works as the small up/down arrows (also the up/down keys on the keyboard) do. But the three methods stop at 0.000 (the lowest limit) while the scale unit (as 'ms') is fixed.

If I enter 0.100 (with the existing 'ms' unit, equivalent to 100us) and increase it (as to 1.100 ms or higher), decreasing it will return us to the previous lowest limit (0.000 ms).

A side note, I recall I saw 0.125 ms changed to 125 us in one of my previous tests in the least. Now, no matter what I do, also with or without activating the debugger, I can't make the unit 'us' appear again! Obviously, this is not important, speaking practically. I just tell you what I notice.

I can't reproduce your problems:

arcachofo wrote:

I noticed that the mouse wheel works as the small up/down arrows (also the up/down keys on the keyboard) do. But the three methods stop at 0.000 (the lowest limit) while the scale unit (as 'ms') is fixed.

If I enter 0.100 (with the existing 'ms' unit, equivalent to 100us) and increase it (as to 1.100 ms or higher), decreasing it will return us to the previous lowest limit (0.000 ms).

A side note, I recall I saw 0.125 ms changed to 125 us in one of my previous tests in the least. Now, no matter what I do, also with or without activating the debugger, I can't make the unit 'us' appear again! Obviously, this is not important, speaking practically. I just tell you what I notice.

I can't reproduce your problems:

youtube-8hvFWyFRFks-/youtube

Now, with your video, everything is very clear.

I don't know why I had to focus 'always' on the small white boxes 'only' every time I tried changing a setting. I mean, I didn't image it can be done in a much easier way as you did on the video. Thank you.

I don't know why I had to focus 'always' on the small white boxes 'only' every time I tried changing a setting. I mean, I didn't image it can be done in a much easier way as you did on the video. Thank you.

Ok... again I didn't understand what you did.
I didn't even know that the mouse wheel could be used in the spinbox.

arcachofo wrote:

I don't know why I had to focus 'always' on the small white boxes 'only' every time I tried changing a setting. I mean, I didn't image it can be done in a much easier way as you did on the video. Thank you.

Ok... again I didn't understand what you did.
I didn't even know that the mouse wheel could be used in the spinbox.

SimulIDE_1.0.1-R1386_Win32

For example, if I left click on the box and keep the mouse over it (not moving it onto the screen as you did on the video), the mouse wheel increments or decrements the setting, though without changing its decimal part.

If you can reproduce this on your side, you may also notice other things as long the mouse is not anywhere on the big screen.

If you can reproduce this on your side, you may also notice other things as long the mouse is not anywhere on the big screen.

Yes, I tested yesterday when I understood you were doing that.
The box has an step of 1, so it is only useful if you want to increment/decrement exactly 1 or in you want to set an exact value.
I personally only use the box to set exact values.

It is planned to add a way to set exact value with unit, probably as you tried: by writing value + unit, (150 us for example).

arcachofo wrote:It is planned to add  a way to set exact value with unit, probably as you tried: by writing value + unit, (150 us for example).

This is a good update though not urgent, I guess.