qtdragon error opening linuxcnc.var

More
3 years 6 months ago #269466 by rodw
I'm trying to migrate to qtdragon-hd on a working axis  on Bullseye Initially set up 12 months ago. 
I did an sudo apt upgrade to get the current version of Bullseye and then 
upgraded 2.9  using the debs on the hidden buildbot in training... All went well and the qtdragon sims work perfect.

So this morning, I worked through the qtdragon install and finally get the GUI to open after commenting out a few custom pins I used in an axis side panel. BUt on openingit displays this error:
Code:
mill2@mill2:~/linuxcnc/configs/VMNmillQT$ linuxcnc -l LINUXCNC - 2.9.0-pre1-683-g5585d6c36 Machine configuration directory is '/home/mill2/linuxcnc/configs/VMNmillQT' Machine configuration file is 'VMNmillQT.ini' Starting LinuxCNC... linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod Note: Using POSIX realtime Found file(REL): ./VMNmillQT.hal qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 2062, resource id: 0, major code: 20 (GetProperty), minor code: 0 [QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW][ERROR] File does not exist: /home/mill2/linuxcnc/VMNmillQT/linuxcnc.var (origin_offsetview.py:301) [QTvcp][CRITICAL] Aborted from Error Dialog Qtvcp encountered an error. The following information may be useful in troubleshooting: LinuxCNC Version : 2.9.0-pre1-683-g5585d6c36 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qtvcp/widgets/origin_offsetview.py", line 383, in periodic_check self.reload_offsets() File "/usr/lib/python3/dist-packages/qtvcp/widgets/origin_offsetview.py", line 232, in reload_offsets temp[STATUS.stat.g5x_index-1] = STATUS.stat.g5x_offset TypeError: 'tuple' object does not support item assignment (qtvcp:465) [QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW][ERROR] File does not exist: /home/mill2/linuxcnc/VMNmillQT/linuxcnc.var (origin_offsetview.py:301) /usr/bin/linuxcnc: line 977: 24340 Segmentation fault $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS Shutting down and cleaning up LinuxCNC... Running HAL shutdown script task: 3895 cycles, min=0.000035, max=0.018058, avg=0.005082, 0 latency excursions (> 10x expected cycle time of 0.005000s) vfdmod: close request received. iov2: exiting vfdmod: application closed. Note: Using POSIX realtime LinuxCNC terminated with an error. You can find more information in the log: /home/mill2/linuxcnc_debug.txt and

It seems like its failing due to a missing .var file but I have tried a few different file names to ensurethe file exists. How can I get past this road block?

Please Log in to join the conversation.

More
3 years 6 months ago #269470 by cmorley
Could you post your config files?

Please Log in to join the conversation.

More
3 years 6 months ago #269471 by rodw
Try this. I think I got it all. First cut with the full folder was too big
 

Attachment not found

Please Log in to join the conversation.

More
3 years 6 months ago #269516 by cmorley
Could you run using
DISPLAY = qtvcp -d qtdragon_hd
and post the terminal

I can't replicate the obvious error. Maybe that can give me more info.

Please Log in to join the conversation.

More
3 years 6 months ago #269527 by cmorley
ok it seems to be the absolute path to the var file.
can you change it to a relative to the config folder path and see what happens.
PARAMETER_FILE = /home/mill2/linuxcnc/VMNmillQT/linuxcnc.var
to
PARAMETER_FILE = linuxcnc.var

Please Log in to join the conversation.

More
3 years 6 months ago #269532 by rodw
Chris,thanks for this. I'll check over the weekend. Looks like the monitor failed yesterday so I can't check for a while.

Please Log in to join the conversation.

More
3 years 6 months ago #269591 by rodw

ok it seems to be the absolute path to the var file.
can you change it to a relative to the config folder path and see what happens.
PARAMETER_FILE = /home/mill2/linuxcnc/VMNmillQT/linuxcnc.var
to
PARAMETER_FILE = linuxcnc.var
Chris, That was it thanks! We have movement and a Modbus spindle (RPM not properly scaled yet, but we'll get there...)

Please Log in to join the conversation.

More
3 years 6 months ago #269594 by cmorley
Ok great. I'll look into why that was a problem in the future.

Please Log in to join the conversation.

Time to create page: 0.098 seconds
Powered by Kunena Forum