Nembered Paramenters accessibility.

Hi Andy.
You are right I wrote badly.
I used the solution for GRUB2 with the file 07_rtai and related installation procedure that Kent Reed made.

bigalex

Hi .
I tried the SMI fix with the "rtapi.conf" file modifications.
But after that no way to start the latency test or run a LinuxCNC configuration and no errors coming as well.
So I went back to the original "rtapi.conf" file and everything work as before.
Maybe my chipsets are not listed so smi fix it is not applicable .
I'm attaching the lspci result so if somebody can give a look at this as tell me if I'm wrong.
Thanks.

bigalex

I will try to fix the SMI issue because I've verified that the chipsets on my mother board are listed as "affected" .

I listed all the affected chipsets here
wiki.linuxcnc.org/cgi-bin/wiki.pl?FixingSMIIssues
and here
www.linuxcnc.org/index.php/english/forum...me-latency-solutions

Intel Corporation 82801I (ICH9 Family)

Not sure how you can think that any revision of the ICH9 chipset has a SMI problem, it is not listed, none of the ICH9 family are.

Hi ArcEye.
Thank you so much.
I'm wrong.

bigalex

Hi people.
I've tried the Glade2Gcode example from Andy and I've to say that is really a possible solution to the problem I have.
Thanks to the new G code parameters naming functionality and linking to HAL pins the potentiality of the G code programming
is amazingly extended.
Now there is a link like this GladeVCP widget -> HAL pin -> G code parameter referring the HAL pin name.
The flow direction seems to be unique , in other words it is not possible to act from G code to HAL pin to GladeVCP widget (as Andy wrote).
Please Andy correct me if I'm wrong.
I'm trying to express what I think I've understood.
At the moment I've not yet the skills to manage properly this LinuxCNC improvement so I will try to learn the basics of GladeVCP
first and Python coding too.

bigalex

Hi Andy.

So the savestate.py never change and the savestate.ini is changed automatically
related to the widget programmed during the shut down (window close/destroy) event isn't it ?

bigalex

Hi Andy.
After some troubles I'm here again to ask for your support.
I'm testing your configuration example Glade2Gcode .
To experiment how it is working I made a new GladeVCP panel and fit on the window some spinbutton widgets and the dro object .
I renamed the GladeVCP panel as your panel is and rename the old one so I ran the configuration
and what I saw after the first shut down is that it didn't store the values of the spinbutton after the shut down.
I ran the configuration and I saw that the message

Destroy?

is not shown as using your GladeVCP panel did.
Into the savestate.py there is :

def on_destroy(self,obj,data=None):
print 'Destroy?'
self.ini.save_state(self)

So that is why if the Destroy message is not shown I supposed that the destroy event is not emitted .
If I change the values editing the savestate.ini file at the next startup the spinbutton widgets are setted with the proper values.
Is there a procedure to emit the destry event from GladeVCP panel or it should be emitted automatically (by default) ?
Excuse me if I'm telling something stupid .

bigalex