GScreen and some understanding gap of hal-widgets

The learning curve is steep - I understand

Pncconf doesn't make sim config as it's too much work to simulate the many variations of the board pins ( well as far as i'm concerned anyways).

Pncconf in 2.8 does make xyyz configs - pick a xyza machine and add a tandem (y2) axis - if it doesn't work it's a bug.

Core_sim9 gives simulated axes HAL-wise but it must be connected properly.

I don't know the first error message.
The second seems to indicate that your Mesa board was not found - but there may be more information in other messages given at that time.

Chris M

Core_sim9 gives simulated axes HAL-wise but it must be connected properly.

That was my first try, but the result was completely weird and I don't understand core_sim9 at all.

I'm going to try figure simulation out for my setup.

basic_sim seems to do the trick

... but hallib is not part of searchpath, so that I had to specify the relative path from my ini file: All other HALFILE-entries commented out.

Execution of linuxcnc creates a file <myInifileName>_cmds.hal, that includes all simulation stuff.
Next the HALFILE-entry needs to be changed to use the generated file.
With that file homing works and I can start with MDI input.

So let's find out how far I can get with that setup

Glad you found away. My next suggestion was using a prebuilt sim config from linuxcnc that was close to what you want and modify it.

Chris M

I believe, that's insane, change something if you don't know, what you're doing.
I looked into the sim*.hal files, but I don't understand, what's going on there.
The generated hal file is straight forward and easy to read and understand

by the way: I used pncconf of master - I did not find support for my desired setup.
May be, description needs some extension.
... but after all - I was able to change generated ini manually to the desired setup

With the help of some mdi commands I was able to get different numbers on absolute and relative dro.

.
Blue dros are the relative positions and green the absolute positions
.

What I don't understand:
both images are taken right after start of linuxcnc, powering on and home all axis.
Shouldn't the fixture-table show the difference between relative and absolute position in some line?
I looked at offset-widget.py and there's a periodic call, that should update the table content - at least at my understanding.
What am I missing here?

My guess is the tooltable is not initialized with the toolfile path.

try adding:
self.gscreen.init_tooleditor()

to the def initialize_widgets(self): function

Chris M

Hi Chris,

that line is already active.
Where can I find the source of GScreen class?

src/emc/usr_intf/gscreen/gscreen.py

Also in 2.8 you can gleem some information in the terminal with:

gscreen -f | more

Chris M

Sorry i'm tired... the command should have been:

self.gscreen.init_offsetpage()

Chris M