[SOLVED] Qtpyvcp - error on startup

I am going to ask the obvious and basic questions as I am not seeing some basic root cause dignostics mentioned. If I hace missing this then apologies and ignore or better yet link me to the relevant post.

[1] Does a vanilla install using Axis work from a latency and responsiveness angle?
i.e this is not systemic to the pc/os/linuxcnc install?

[2] Next would be, have you tried another qtpyvcp UI (something from Turbos for example) as a comparision test?
i.e. is this a common experience across qtpyvcp UIs?

Thanks - J.

James,
Thanks, and don't assume I haven't done something dumb.

Background
Had MX21, LCNC 2.9, qtpyvcp, PB (python3) installed as of late last summer.  Went to do a fresh install of MX21 due to hardware changes (new mesa config) and ran in to problems with my PC and real-time delays due to the realtek NIC. Tried multiple distros/kernel conbinations and nothing seemed to work properly

Bought a new(used) PC with an Intel NIC in hopes of avoiding that issue.

Setup

• HP elitedesk 800 G2 mini i7-6700, 8g. Intel NIC (new to me PC)
• Bullseye installed from iso pulled from Debian site a few days ago
• Grub: quiet nomodeset isolcpus=2,3 nohz_full=1
• Edited /etc/network/interfaces for Intel NIC
• RT-PREEMPT 5.10, LCNC 2.10, qtpyvcp, PB installed via your script.  Had to add python3-distro dependency to get editvcp working, but QTDesigner starts with no errors

Problem
Probe Basic is throwing errors during start up, but still loads and I can home the sim.  When I try to load my old working config (edited for new mesa sserial board & other changes) the same error shows up in the terminal (as with the sim), as well as hanging up for a long time.

When PB eventually loads, I can't come out of estop and power on the machine.  I've tried editing HAL so there's nothing connected and i should be able to toggle the GUI buttons or directly in halshow, but nothing works.

Troubleshooting (starting from terminal and using LCNC config chooser)

• Config Chooser
  • loads, but the window and contents are distorted.  Like it's loading at the wrong resolution.
  • This distortion is new behavior since i started this thread.
• Axis
  • loads, homes, no errors
• gmoccapy
  • loads, homes, some errors in terminal but nothing on screen
  • Window & content size look normal.
• QtDragonHD
  • loads, homes, no errors, one terminal warning about a pdf viewer missing
• qtpyvcp (brender)
  • loads, no errors
• qtpyvcp (PB sim)
  • loads, homes, error in terminal, resolution is wrong (screen cut off)
• qtpyvcp (PB_lathe_sim)
  • loads, homes, resolution is wrong, no terminal errors
• qtpyvcp (PB my edited config)
  • loads after delay seen in terminal, window is wrong, can't turn machine on

I think latency looks OK, screenshot attached.  I ran the lcnc-hw script for a couple hours last night and no spikes showed up.

I've attached terminal outputs from multiple LCNC startups.  HAL and INI were attached earlier and I've not made any significant changes.

Regards,
Ralph

Remaining attachments.

You have file errors in those reports,  check your paths again and see if it resolves.  Looks like ladder file and postgui..

Are you talking about this one?

EDIT
Interesting update... edited my INI file and saw I had a bad path for my subroutines.  Started my config and the delay disappeared as well as the halui error

Still getting the same error message qtpyvcp widgets, and PB & LCNC config choose are still showing up at he wrong screen resolution:

When you run the qtpyvcp sims are you pointing to the newly installed config folder in the dev probe basic directory? Or some copied over that were in the previous linuxcnc folder?  

Lcvette wrote:

When you run the qtpyvcp sims are you pointing to the newly installed config folder in the dev probe basic directory? Or some copied over that were in the previous linuxcnc folder?  
 

For PB_sim:
start lcnc in terminal, config chooser window shows up, and I select the probe_basic sim under My Configurations

For PB_lathe_sim:
start lcnc in terminal, config chooser opens, select sim.qtpyvcp, select XYZ, and select PB_lathe from menu

Xyz is mill

tommylight wrote:

[code][code]A screenshot of TOP or HTOP can also be helpful, while your config is running.

[/code][/code]
 

Tommy - this one may be solved when I fixed the subroutine path... but what is "TOP" or "HTOP"?