You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing value of 1000 was assumed by the number of available digits on the device display, but in fact it will go higher and simply not display the full "Wh" on the display once 1000 Wh is reached. If the ODROID Smart Power is plugged into an ODROID device and is performing computation, it can still take days of continuous execution to reach the 1000 Wh threshold. Perhaps the overflow is 10k Wh? 100k Wh? Higher? Leaving this issue open until we can identify the actual overflow point.
Fortunately the implementation doesn't incorrectly detect an overflow when 1000 Wh is reached. A problem will only appear when the actual overflow point is reached, at which point the read function will return an value that is too small.
The text was updated successfully, but these errors were encountered:
Reopening - it seems that the device actually maxes out at 8192.0 Wh. It doesn't overflow there, it just stops increasing in value. Perhaps a floating point overflow interrupt prevents it from rolling over.
So the 10k value we're now forcing a restart at is too high.
The existing value of 1000 was assumed by the number of available digits on the device display, but in fact it will go higher and simply not display the full "Wh" on the display once 1000 Wh is reached. If the ODROID Smart Power is plugged into an ODROID device and is performing computation, it can still take days of continuous execution to reach the 1000 Wh threshold. Perhaps the overflow is 10k Wh? 100k Wh? Higher? Leaving this issue open until we can identify the actual overflow point.
Fortunately the implementation doesn't incorrectly detect an overflow when 1000 Wh is reached. A problem will only appear when the actual overflow point is reached, at which point the read function will return an value that is too small.
The text was updated successfully, but these errors were encountered: