Error on startup

More
5 years 9 months ago #194735 by snowgoer540
Error on startup was created by snowgoer540
I moved this from a topic under PlasmaC as there were two separate errors being posted at the same time and I didnt want it to go missed.

After updating yesterday evening, I started randomly getting this error on startup:
Code:
Traceback (most recent call last): File "/home/plasma/linuxcnc-dev/lib/python/qtvcp/widgets/system_tool_button.py", line 106, in _set_user_system_text self.setText(convert[int(data)]) KeyError: 0

Here is the terminal info from when it happens:

Attachment not found



I am unsure what the cause is, or if it's a QTVCP problem, but as it pointed to a QTVCP widget, I figured I'd point it out here. Apologies if it was already reported. I do believe user robertspark also saw it forum.linuxcnc.org/plasmac/38521-gui-for...mac?start=150#194659

But for me, it is definitely the #1 error message when it happens.

Thanks!

Please Log in to join the conversation.

More
5 years 9 months ago #194739 by cmorley
Replied by cmorley on topic Error on startup
The error message is a red herring, unfortunately.
This is not a consistent error on start up?
Isee lts of error messages from the Motion component indicating something is hanging early in the process.
you running 2.8 or master?

Please Log in to join the conversation.

More
5 years 9 months ago #194740 by cmorley
Replied by cmorley on topic Error on startup
oh I can see your using master.
I get this when switching to conversational tab (in sim)
Code:
[QTvcp][CRITICAL] Aborted from Error Dialog Qtvcp encountered an error. The following information may be useful in troubleshooting: LinuxCNC Version : 2.9.0~pre0 Traceback (most recent call last): File "/home/chris/emc/share/qtvcp/screens/qtplasmac/qtplasmac_handler.py", line 1195, in <lambda> self.w.main_tab_widget.currentChanged.connect(lambda w:self.main_tab_changed(w)) File "/home/chris/emc/share/qtvcp/screens/qtplasmac/qtplasmac_handler.py", line 979, in main_tab_changed self.conv_setup() File "/home/chris/emc/share/qtvcp/screens/qtplasmac/qtplasmac_handler.py", line 2698, in conv_setup self.conv_shape_request('conv_line', CONVLINE, True) File "/home/chris/emc/share/qtvcp/screens/qtplasmac/qtplasmac_handler.py", line 2792, in conv_shape_request reload(module) NameError: name 'reload' is not defined

Please Log in to join the conversation.

More
5 years 9 months ago #194752 by snowgoer540
Replied by snowgoer540 on topic Error on startup

cmorley wrote: The error message is a red herring, unfortunately.
This is not a consistent error on start up?
Isee lts of error messages from the Motion component indicating something is hanging early in the process.
you running 2.8 or master?


red herring? new term for me haha

Yea, master as you saw.

I dont see that particular error. Are you using buildbot or RIP?

Please Log in to join the conversation.

More
5 years 9 months ago #194771 by cmorley
Replied by cmorley on topic Error on startup
RIP

You could try running qtvcp with -v (in the INI) to see if it gives any more info.

Please Log in to join the conversation.

More
5 years 9 months ago #194783 by snowgoer540
Replied by snowgoer540 on topic Error on startup
Interesting, They should work, Might want to get Phill to take a peek at them.

I added -v in the event it happens again, maybe I can provide additional info. I've only seen it in SIM not in a live table, so it could be a timing thing.

Please Log in to join the conversation.

More
5 years 9 months ago #194897 by andypugh
Replied by andypugh on topic Error on startup
I think that "ini.z.maxlimit does not exist" is probably the real problem.

At a guess a HAL file is referencing those pins before the module that creates them is loaded. I am not sure which module creates them, though. I would have guessed motion, but they are not in the manpage

Please Log in to join the conversation.

More
5 years 9 months ago #194913 by snowgoer540
Replied by snowgoer540 on topic Error on startup

andypugh wrote: I think that "ini.z.maxlimit does not exist" is probably the real problem.

At a guess a HAL file is referencing those pins before the module that creates them is loaded. I am not sure which module creates them, though. I would have guessed motion, but they are not in the manpage


I think that's a fairly accurate guess. the maxlimit errors mostly shows up in SIM, but I have seen it once or twice on a live table. It always felt like a timing thing, so maybe we need to delve a little deeper into the order the modules are loaded.

Please Log in to join the conversation.

More
5 years 9 months ago #194971 by phillc54
Replied by phillc54 on topic Error on startup
I have not seen that error before.

ini.z.max_limit is netted by the handler file as the fourth command of the initialized function. Quick testing has shown that there is no difference whether it is the first or last command.

If I rename it to the wrong pin number then I get the following:
Code:
<commandline>:0: Pin 'ini.z.max_limits' does not exist <commandline>:0: Pin 'ini.z.min_limits' does not exist
but I dont see these messages which are in the first post.
Code:
USRMOT: ERROR: command timeout emcMotionInit: emcTrajInit failed
or further down:
Code:
waiting for component 'inihal' to become ready......

Please Log in to join the conversation.

More
5 years 9 months ago #194973 by phillc54
Replied by phillc54 on topic Error on startup
A bit more testing:

In the ini file, if I change:
Code:
SUBROUTINE_PATH = ./:./qtplasmac:../../nc_files/subroutines
to a non existing path:
Code:
SUBROUTINE_PATH = ./:./wqtplasmac:../../nc_files/subroutines
I get this error in terminal:
Code:
emc/task/emctask.cc 69: interp_error: File not open File not open emc/task/emctaskmain.cc 3070: can't initialize interpreter
plus this error from qtvcp:
Code:
Traceback (most recent call last): File "/home/phill/git/linuxcnc-dev/lib/python/qtvcp/widgets/system_tool_button.py", line 106, in _set_user_system_text self.setText(convert[int(data)]) KeyError: 0
so I don't think it is a qtvcp error, just qtvcp's reaction to not being able to load correctly because of some other pre-existing issue.

Please Log in to join the conversation.

Time to create page: 0.066 seconds
Powered by Kunena Forum