[GH-ISSUE #316] Non homogenous behaviour of LED in exam mode #141

Open
opened 2026-05-06 13:15:42 +02:00 by BreizhHardware · 17 comments

Originally created by @Overengined on GitHub (Mar 5, 2023).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/316

Describe the bug
Exam mode LED is bahving differently depending on whether the device is on or off.

To Reproduce
Steps to reproduce the behavior:

  1. Put the calculator in exam mode and take notice of the LED blink speed.
  2. Turn the calculator off and notice that the LED is blinking at a different speed.

Expected behavior
The LED should blink at the same speed, otherwise an over-zealous examinator might find it supsicious.

Device (please complete the following information):

  • N0110
  • Upsilon Version: 1.0.1 -dev
  • Upsilon commit: 4acc79f
    (seems to be version independant tho)
Originally created by @Overengined on GitHub (Mar 5, 2023). Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/316 **Describe the bug** Exam mode LED is bahving differently depending on whether the device is on or off. **To Reproduce** Steps to reproduce the behavior: 1. Put the calculator in exam mode and take notice of the LED blink speed. 2. Turn the calculator off and notice that the LED is blinking at a different speed. **Expected behavior** The LED should blink at the same speed, otherwise an over-zealous examinator might find it supsicious. **Device (please complete the following information):** - N0110 - Upsilon Version: 1.0.1 -dev - Upsilon commit: 4acc79f (seems to be version independant tho)
Author
Owner

@0x4c756e61 commented on GitHub (Mar 5, 2023):

I was able to reproduce it, and it looks like it is slower when we turn off the calculator

<!-- gh-comment-id:1455068821 --> @0x4c756e61 commented on GitHub (Mar 5, 2023): I was able to reproduce it, and it looks like it is slower when we turn off the calculator
Author
Owner

@Overengined commented on GitHub (Mar 5, 2023):

Can confirm

<!-- gh-comment-id:1455069020 --> @Overengined commented on GitHub (Mar 5, 2023): Can confirm
Author
Owner

@theodorechle commented on GitHub (Mar 11, 2023):

Same thing when it does something (calculation, execution of a program, ...). It's faster than when it does nothing.

<!-- gh-comment-id:1464945269 --> @theodorechle commented on GitHub (Mar 11, 2023): Same thing when it does something (calculation, execution of a program, ...). It's faster than when it does nothing.
Author
Owner

@Overengined commented on GitHub (Mar 24, 2023):

In my opinion this issue should get tagged in a way that illustrates its importance. I'm not saying we're dealing with something major here, but since it's related to the exam mode, it deserves some attention.

<!-- gh-comment-id:1482370796 --> @Overengined commented on GitHub (Mar 24, 2023): In my opinion this issue should get tagged in a way that illustrates its importance. I'm not saying we're dealing with something major here, but since it's related to the exam mode, it deserves some attention.
Author
Owner

@NowanPython commented on GitHub (Sep 17, 2023):

I just checked the exam mode and I noticed that when using ΧCAS' plot3d it blinks so fast that anyone would probably find it suspicious.

<!-- gh-comment-id:1722448329 --> @NowanPython commented on GitHub (Sep 17, 2023): I just checked the exam mode and I noticed that when using ΧCAS' `plot3d` it blinks so fast that anyone would probably find it suspicious.
Author
Owner

@Overengined commented on GitHub (Sep 19, 2023):

@Lauryy06 would it be possible to kncrease the priority of this issue ? We dont have ans idea why its happening. My best guess would be that the blinking is set with cpu cycles and so when they get longer the blinking gets slower. Opposite works too.

<!-- gh-comment-id:1726318306 --> @Overengined commented on GitHub (Sep 19, 2023): @Lauryy06 would it be possible to kncrease the priority of this issue ? We dont have ans idea why its happening. My best guess would be that the blinking is set with cpu cycles and so when they get longer the blinking gets slower. Opposite works too.
Author
Owner

@Lisra-git commented on GitHub (Sep 19, 2023):

Hard to fix this issue, it exist since Omega and was only "fixed" partially in Epsilon recently.

<!-- gh-comment-id:1726355567 --> @Lisra-git commented on GitHub (Sep 19, 2023): Hard to fix this issue, it exist since Omega and was only "fixed" partially in Epsilon recently.
Author
Owner

@Overengined commented on GitHub (Sep 19, 2023):

Hard to fix this issue, it exist since Omega and was only "fixed" partially in Epsilon recently.

How did they do it ?

<!-- gh-comment-id:1726367691 --> @Overengined commented on GitHub (Sep 19, 2023): > Hard to fix this issue, it exist since Omega and was only "fixed" partially in Epsilon recently. How did they do it ?
Author
Owner

@GillesSchippers commented on GitHub (Dec 24, 2023):

Hard to fix this issue, it exist since Omega and was only "fixed" partially in Epsilon recently.

How did they do it ?

Exactly, I will try and see what they changed. Hope that change isn't too big or complicated.

<!-- gh-comment-id:1868472686 --> @GillesSchippers commented on GitHub (Dec 24, 2023): > > Hard to fix this issue, it exist since Omega and was only "fixed" partially in Epsilon recently. > > How did they do it ? Exactly, I will try and see what they changed. Hope that change isn't too big or complicated.
Author
Owner

@Lisra-git commented on GitHub (Dec 24, 2023):

Surprise, source is private

<!-- gh-comment-id:1868507310 --> @Lisra-git commented on GitHub (Dec 24, 2023): Surprise, source is private
Author
Owner

@GillesSchippers commented on GitHub (Dec 24, 2023):

Surprise, source is private

Huh? I thought they still had the repo updated, perhaps I am mistaken 😭

<!-- gh-comment-id:1868615344 --> @GillesSchippers commented on GitHub (Dec 24, 2023): > Surprise, source is private Huh? I thought they still had the repo updated, perhaps I am mistaken 😭
Author
Owner

@Overengined commented on GitHub (Dec 25, 2023):

The Epsilon OS isn't private, but it has gone from free software to closed source. So you legally cannot copy anything they do in their code.

<!-- gh-comment-id:1868617109 --> @Overengined commented on GitHub (Dec 25, 2023): The Epsilon OS isn't private, but it has gone from free software to closed source. So you legally cannot copy anything they do in their code.
Author
Owner

@AngeDieu commented on GitHub (Dec 25, 2023):

but can you get inspired by their code and then make a other similar one, or not similar ?

<!-- gh-comment-id:1868950582 --> @AngeDieu commented on GitHub (Dec 25, 2023): but can you get inspired by their code and then make a other similar one, or not similar ?
Author
Owner

@GillesSchippers commented on GitHub (Dec 25, 2023):

but can you get inspired by their code and then make a other similar one, or not similar ?

Yes you can, as long as it is not a direct copy, but will probably remain in a grey area

<!-- gh-comment-id:1869030449 --> @GillesSchippers commented on GitHub (Dec 25, 2023): > but can you get inspired by their code and then make a other similar one, or not similar ? Yes you can, as long as it is not a direct copy, but will probably remain in a grey area
Author
Owner

@GillesSchippers commented on GitHub (Dec 25, 2023):

The Epsilon OS isn't private, but it has gone from free software to closed source. So you legally cannot copy anything they do in their code.

Then we will just observe how they fixed it, and implement it similarly or differently, as long as the issue is fixed and nothing illegal has been done

<!-- gh-comment-id:1869031028 --> @GillesSchippers commented on GitHub (Dec 25, 2023): > The Epsilon OS isn't private, but it has gone from free software to closed source. So you legally cannot copy anything they do in their code. Then we will just observe how they fixed it, and implement it similarly or differently, as long as the issue is fixed and nothing illegal has been done
Author
Owner

@Lisra-git commented on GitHub (Dec 25, 2023):

The relevant code is private

<!-- gh-comment-id:1869041273 --> @Lisra-git commented on GitHub (Dec 25, 2023): The relevant code is private
Author
Owner

@GillesSchippers commented on GitHub (Dec 25, 2023):

The relevant code is private

Seriously...
Then we would have to look at this issue ourselves.
Once I am back home from my vacation I'll try and see what is up with this

<!-- gh-comment-id:1869046056 --> @GillesSchippers commented on GitHub (Dec 25, 2023): > The relevant code is private Seriously... Then we would have to look at this issue ourselves. Once I am back home from my vacation I'll try and see what is up with this
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Upsilon#141
No description provided.