Skip to content

gmoccapy: Fix reading [DISPLAY]CYCLE_TIME when wrongly set as a real - #4417

Open
BsAtHome wants to merge 1 commit into
LinuxCNC:masterfrom
BsAtHome:fix_gmoccapy-cycle-time
Open

gmoccapy: Fix reading [DISPLAY]CYCLE_TIME when wrongly set as a real#4417
BsAtHome wants to merge 1 commit into
LinuxCNC:masterfrom
BsAtHome:fix_gmoccapy-cycle-time

Conversation

@BsAtHome

@BsAtHome BsAtHome commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Several sims use the wrong [DISPLAY]CYCLE_TIME being set in seconds, whereas the docs say it is in milliseconds. The old INI read would cause an exception, which no longer happens. The new INI-file reader warns of trailing context and return the value zero (0). It will now test for existence and whether it is larger than 0. Otherwise the default is used.

Also, the existence test "not val" should read "val is None", which has been fixed in two places where INI values are read and zero (0) is a valid value.

Fixes #4415

After discussion in #4415 gmoccapy now accepts both seconds and milliseconds bringing it in line with Axis.

Comment thread share/gscreen/skins/silverdragon/silverdragon_handler.py
@BsAtHome
BsAtHome force-pushed the fix_gmoccapy-cycle-time branch from d05aae7 to 773474d Compare August 19, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gmoccapy: Multiple sim configs fail to launch

2 participants