-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FNIRSI GC-01: Graphical glitches at startup #163
Comments
Also noticed the same dots.
FNIRSI GC-01, APM32F103RBT6 - 2418, M4011, display flat cable: GMT024-05
V2.0
Is this an issue? However...
ugo
Il giorno ven 6 dic 2024 alle ore 14:29 ThatBum ***@***.***>
ha scritto:
… I first noticed this in the latest build of 2.0.4. On the splash screen
there's a line of corrupted pixels here:
PXL_20241206_131447909.jpg (view on web)
<https://github.com/user-attachments/assets/ba5f2930-bd29-4389-8e1f-5eddab4e3ff8>
They're not dead pixels on the display, once it's past the splash screen
it goes away.
On 2.0.3 the splash screen disappears too quickly to see if it's there,
but I did notice a similar bit of corruption on the main screen:
PXL_20241206_131608655.jpg (view on web)
<https://github.com/user-attachments/assets/f47e2cf4-8b66-4187-8092-f9ed5637983f>
This also goes away after a second. I guess something with the video
memory isn't initializing quite right.
Unit is a FNIRSI GC-01 with the Geehy processor and an M4011 tube. If it
helps any, the code on the display ribbon cable is ENH-TV240B026.
—
Reply to this email directly, view it on GitHub
<#163>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWI7RBH6NWESATUQK2IN6T2EGREBAVCNFSM6AAAAABTEVMELCVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZDGMBWG4YDEOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Ugo Papetti
***@***.***
Tel. 3357368922
|
Thus the minor in the title. I know it's probably low priority but figured I should report it anyway. Might be a trivial fix. |
agree
Il giorno ven 6 dic 2024 alle ore 15:51 ThatBum ***@***.***>
ha scritto:
… Is this an issue?
Thus the minor in the title. I know it's probably low priority but figured
I should report it anyway. Might be a trivial fix.
—
Reply to this email directly, view it on GitHub
<#163 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWI7RCFSYOLI4TF7XZQERD2EG2WXAVCNFSM6AAAAABTEVMELCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTGQZDANBSGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Ugo Papetti
***@***.***
Tel. 3357368922
|
Thanks for the report! ¿Can somebody confirm this did not occur in 2.0.2? |
It's not on the splash screen like 2.0.4, but does appear on the measurement screen for a second like 2.0.3. |
In 2.0.4, does the spot always appear at the same spot, or does it move every time you turn on the device? Does the spot's pattern stay the same or does it change (another photo might help)? Is there any spot afterwards? I insist: could you check if there is any spot in 2.0.2? This would help a lot in diagnosing the problem. |
This is in 2.0.2, that's what I meant by this. The glitch has the same appearance and the same position every time. |
Can somebody check if this also manifests on the Bosean FS-5000? Trying the landscape release would help a lot. |
Here my dots with 2.0.4:
Il gio 19 dic 2024, 22:44 Neptuns ***@***.***> ha scritto:
… This is on 2.0.2. Dotted line always appear on startup. Double dots above
decimal separator always appear on first measurement update. The small dots
after number 4 appear rarely and randomly.
fnirsi.jpg (view on web)
<https://github.com/user-attachments/assets/d8abfccc-d60e-4316-944b-ffc15558a964>
—
Reply to this email directly, view it on GitHub
<#163 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWI7RH2HVDQWZYP3ZE7MV32GM45LAVCNFSM6AAAAABTEVMELCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVHAZDMMBWGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi all,
so,me tests with the counter GC-01
Processor brand / moidel: Geehy APM32F103RBT6 - 2418
Geiger tube: GM4011H
Display model: GMT024-05 V2.0
Internal port layout: #VCC – GND – DIO – CLOCK (VCC: square)
2.0.2: splash screen without corruptions, measurement screen corrupted for
about 1,5 seconds, then screen becomes as expected, without any extra dots.
2.0.3: splash screen too fast to observe for defects, measurement screen
corrupted for about 1,5 seconds, then screen becomes as expected, without
any extra dots.
2.0.4: splash screen corrupted, measurement screen ok
Il giorno ven 20 dic 2024 alle ore 10:03 Ugo Papetti ***@***.***>
ha scritto:
… Here my dots with 2.0.4:
Il gio 19 dic 2024, 22:44 Neptuns ***@***.***> ha scritto:
> This is on 2.0.2. Dotted line always appear on startup. Double dots above
> decimal separator always appear on first measurement update. The small dots
> after number 4 appear rarely and randomly.
> fnirsi.jpg (view on web)
> <https://github.com/user-attachments/assets/d8abfccc-d60e-4316-944b-ffc15558a964>
>
> —
> Reply to this email directly, view it on GitHub
> <#163 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AKWI7RH2HVDQWZYP3ZE7MV32GM45LAVCNFSM6AAAAABTEVMELCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVHAZDMMBWGI>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
Ugo Papetti
***@***.***
Tel. 3357368922
|
Can somebody try this: https://github.com/Gissio/radpro/actions/runs/12775724387 (click below on radpro-firmware-snapshot) and see if it fixes this issue? |
White screen. It is detecting counts but is otherwise unresponsive. |
Same issue here as well with the snapshot, nothing but blank display with backlight but can hear clicks and see led activity |
Thanks for the reports. There was a very silly bug. Could you please try again? https://github.com/Gissio/radpro/actions/runs/12780156091 |
This one works and the artifact is gone from the splash screen but this one is still present. |
Those images were very useful! I was able to reproduce and fix the glitch involving the 1 and 4 characters. Can you try once again? https://github.com/Gissio/radpro/actions/runs/12816891832 |
This one seems to function properly for the 1 and 4 case, but i am seeing the dots on the initial screen again, as in this post: #163 (comment) |
The Pulses menu is messed up. Haptic leads to Pulse LED, Pulse LED leads to Display flashes, and Display flashes leads to Haptic. |
Can you try https://github.com/Gissio/radpro/actions/runs/13103763916/artifacts/2524185828 and see if this is fixed? |
Fix'd, but a new minor problem. When turning it off, if the power button is held down for slightly too long, it'll register it as an on press and turn on again. Which is slightly annoying. |
Excellent bug report. Thanks for your help. Did you try the new features? Alarm dismissal, more rate/dose alarm options, configurable alarm signaling, keyboard lock mode? Do the graphical glitches still appear? |
Thanks, I'm told I have a knack for finding bugs. Speaking of, another more serious one. It seems the cumulative dose is not saved upon power cycling anymore. Every time it starts with zero counts. The new features all work, however I'd like to suggest a change with alarm signaling. The way it is now the Acoustic setting applies all three levels of alarm, Haptic applies itself and Visual, and Visual just applies itself. You can only choose one of the three as if they were radio buttons. Instead I feel it would make more sense to be able to select any combination of these such that one could apply them individually. Furthermore I'd like an LED alarm option because I'd prefer not to have the alarm flashing obscure blinks from the pulse counts. The glitch is still there. I had no idea this would be such a bugbear to hunt down! |
Hi Gissio,
Glitches @Splash are not present fir me. Instrad for 1 secondo this apparso
After Power on, as in the attached picture.
Thanks for the developments, keyboard lock prevents to enter config mode,
alarms, Need time to test them.
Cheers ugo
Il lun 3 feb 2025, 16:44 Gissio ***@***.***> ha scritto:
… Excellent bug report. Thanks for your help.
Did you try the new features? Alarm dismissal, more rate/dose alarm
options, configurable alarm signaling, keyboard lock mode?
Do the graphical glitches still appear?
—
Reply to this email directly, view it on GitHub
<#163 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWI7RCZRQ5M7CJSX5HUBNT2N6FEFAVCNFSM6AAAAABTEVMELCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZRGM3TANRYGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Ugo: I don't understand what you mean:
|
Gissio, saw some mispelled words due to the Word corrector of my mobile...
After Power on the screen with the release Is without any glitch.
When the measurement screen apparso there Is a corruption, as in the
picture below, above the decimali point.
The dots remains for 1 secondo then disappear.
Cheers ugo
Il lun 3 feb 2025, 22:27 Gissio ***@***.***> ha scritto:
… Ugo: I don't understand what you mean:
Glitches @Splash <https://github.com/Splash> are not present fir me.
Instrad for 1 secondo this apparso After Power on, as in the attached
picture."
—
Reply to this email directly, view it on GitHub
<#163 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWI7RHAYFZJ4HNQF5ZTSS32N7NLBAVCNFSM6AAAAABTEVMELCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZSGEYTGMJWGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
There was an error with the watchdog timer (which resets the microcontroller in case of malfunction). Could you try again with 2.1beta5? https://github.com/Gissio/radpro/actions/runs/13228168353/artifacts/2561063487 |
I first noticed this in the latest build of 2.0.4. On the splash screen there's a line of corrupted pixels here:
![PXL_20241206_131447909](https://private-user-images.githubusercontent.com/4646042/393262303-ba5f2930-bd29-4389-8e1f-5eddab4e3ff8.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyODEyMjcsIm5iZiI6MTczOTI4MDkyNywicGF0aCI6Ii80NjQ2MDQyLzM5MzI2MjMwMy1iYTVmMjkzMC1iZDI5LTQzODktOGUxZi01ZWRkYWI0ZTNmZjguanBnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTFUMTMzNTI3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzBhNTc3Nzk0MWRmZWI0ODQzZGUwOWE0MDg0YTE4NThjM2ZlYjI2ZGFiZDQyMjE4MzQ0NzNjZGQ3Yjc1OGFjZCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.xDo0HHfSPh7qo-VwiYWFkzAq8aoSAZz6Uuoge4jxxT8)
They're not dead pixels on the display, once it's past the splash screen it goes away. Always appears in the same place.
On 2.0.3 the splash screen disappears too quickly to see if it's there, but I did notice a similar bit of corruption on the main screen:
![PXL_20241206_131608655](https://private-user-images.githubusercontent.com/4646042/393262960-f47e2cf4-8b66-4187-8092-f9ed5637983f.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyODEyMjcsIm5iZiI6MTczOTI4MDkyNywicGF0aCI6Ii80NjQ2MDQyLzM5MzI2Mjk2MC1mNDdlMmNmNC04YjY2LTQxODctODA5Mi1mOWVkNTYzNzk4M2YuanBnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTFUMTMzNTI3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MDEwNDFhNWZjZjQ2ZDg5NmMyY2Q2ODc2N2IwNTkwOTJiZGFiYWRiYTI2ZTYwNDk2ZjY5YzlkYzA4MTFkYWZiMiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.8MY6cPZHd1hngCRbdye6yBBiGDFT1b_5ECeh5qsy1bI)
This also goes away after a second. I guess something with the video memory isn't initializing quite right.
Unit is a FNIRSI GC-01 with the Geehy processor and an M4011 tube. If it helps any, the code on the display ribbon cable is ENH-TV240B026.
The text was updated successfully, but these errors were encountered: