Possible Gscreen bug

Are you using Silverdragon?

Yes, using silverdragon. However, further developments. I did some experiments with gmoccapy and axis and had the same problems. I finally got a XYZY configuration to work with all UIs including gscreen, at least in simulation mode. It turns out it's all in which HAL files are specified in the INI file. In the hallib directory of the sim config directories, there is a gantrysim.hal which must be incorporated. I basically merged core_sim.hal and gantrysim.hal into silverdragon.hal and now it works in simulation mode with gscreen. The next step is to move this to the real hardware and figure out how to make it work with the 7i96. This problem didn't appear when I used the parport and BOB because stepconf has an option to slave 2 axes together, while the 7i96 config tool does not.

Interesting -I'll try to find time to look into it.
I did find that xyyz and xyzy worked differently - I didn't figure out why - thanks for the update.

Chris M

My machine is now working with the 7i96 in XYZY configuration. I will try XYYZ eventually, but there is a new problem. *Sorry*
After updating to linuxcnc 2.9.0, gscreen now spits out the entire contents of some module, probably the handler function. Here's a partial listing:

**** GSCREEN INFO: No Screen 2 glade file present
adding import dir /home/jim/linuxcnc/configs/sim.gscreen.gscreen_custom
module 'silverdragon_handler' imported OK
module 'silverdragon_handler' : 'get_handlers' function found

task: main loop took 0.043250 seconds
task: main loop took 0.033703 seconds
Auto Z Reference - Enabled
task: main loop took 0.011900 seconds
task: main loop took 0.041333 seconds
timeout 100
**** GSCREEN INFO: postgui filename: silverdragon_postgui.hal

This doesn't happen with gmoccapy or axis. I believe it occurs at or around line 399 in gscreen.py.
Not sure if all the text is showing up in a quick reply.

Not sure if you can see all the text I pasted. Just launch any gscreen sim config from a terminal and you will see what I mean.

yes I know what you are talking of - it's a debug line I forgot to erase. fixed in 2.8 but has not been pushed up yet.