qtdragon pins?

 A lot of the pins are already available and can be reused.

You're probably right, but backwards compatibility is not something I considered at the time. Personally, I think trying to have a single hal file that suits all iterations of the gui would not be possible, or at least be a major pain. It's much easier to have completely separate config folders. In fact, that is how all the sample screens are organized.

persei8 wrote:

 A lot of the pins are already available and can be reused.
You're probably right, but backwards compatibility is not something I considered at the time. Personally, I think trying to have a single hal file that suits all iterations of the gui would not be possible, or at least be a major pain. It's much easier to have completely separate config folders. In fact, that is how all the sample screens are organized.

That's true, but it shouldn't be a pain is my opinion. I don't want to appear stubborn but it would be nice if things that are the same only have one name. The documentation is lacking on a lot of levels, I use designer to find out how to name the stuff in the hal files and look further in the handler file. It's not ideal.

I started of with gmoccapy years ago, that was a steep learning curve, the qtvcp screens are not much easier to setup. Therefore I plan to release my ini and hal files for others to learn from.
My machine has a 7i96, vfd, xyyz, air switches, vacum cleaner switches, arcade joystick interface for extra buttons and a Chinese bob for extra outputs (the lights in the switches of the joystick board).
Should make things easier for people who want to use these great looking and functioning screens.

Thanks once again for the very nice screens.

Having the HAL pin names for qtdragon/hd the same as possible sounds like a pretty good idea.
Even makes docs easier

I'll try to remember to look at it this weekend.

By the way if you wrote some sentences for documenting something you had to work too hard to find - I would add them to linuxcnc.

Chris

Having the HAL pin names for qtdragon/hd the same as possible sounds like a pretty good idea.
Even makes docs easier

Thanks, sometimes you just forget when you are busy creating stuff that things can be done easier.

By the way if you wrote some sentences for documenting something you had to work too hard to find - I would add them to linuxcnc.

I was planning to do that, I want to add some examples to the documentation. Will do that when I get everything working.

 The POWER label is a progressBar and it's value is calculated in the handler file by multiplying AMPS and VOLTS values read from the VFD.

I added the net

looks like you need to add maximum motor watts:
MAX_SPINDLE_POWER =

under [DISPLAY] in the ini

cmorley wrote:

cmorley post=223612 userid=482

looks like you need to add maximum motor watts:
MAX_SPINDLE_POWER =

under [DISPLAY] in the ini

 
Ok, I see it now:  

cmorley wrote:

looks like you need to add maximum motor watts:
MAX_SPINDLE_POWER =

under [DISPLAY] in the ini
 

Turns out in 2.9pre it should be for the first spindle

You must be using Jim's version. In linuxcnc it's still MAX_SPINDLE_POWER =

cmorley wrote:

You must be using Jim's version. In linuxcnc it's still MAX_SPINDLE_POWER =
 
 

No, using 2.9 pre. If I change back to just plain MAX_SPINDLE_POWER = it doesn't work. I have to add the spindle number.

The file: /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
pastebin.com
in order to provide information about the linuxcnc
system and configuration.

VIEWER=mousepad
Date: Thu 21 Oct 2021 03:38:39 PM CEST
UTC Date: Thu 21 Oct 2021 01:38:39 PM UTC
this program: /usr/bin/linuxcnc_info
uptime: 15:38:39 up 4:47, 1 user, load average: 1.13, 0.94, 0.92
lsb_release -sa: Debian Debian GNU/Linux 10 (buster) 10 buster
which linuxcnc: /usr/bin/linuxcnc
pwd: /home/cnc/linuxcnc/configs/qtZ0
USER: cnc
LOGNAME: cnc
HOME: /home/cnc
EDITOR:
VISUAL:
LANGUAGE: en_US:en
TERM: xterm-256color
COLORTERM: truecolor
DISPLAY: :0.0
DESKTOP: lightdm-xsession
display size: 1920x1080 pixels (508x285 millimeters)
PATH: /usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

uname items:
nodename -n: cncmachine
kernel-name -s: Linux
kernel-vers -v: #1 SMP PREEMPT RT Debian 4.19.208-1 (2021-09-29)
machine -m: x86_64
processor -p: unknown
platform -i: unknown
oper system -o: GNU/Linux

/proc items:
cmdline: BOOT_IMAGE=/boot/vmlinuz-4.19.0-18-rt-amd64 root=UUID=1c2d3975-99eb-405f-8b53-ba15deab3459 ro quiet
model name: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
cores: 4
cpu MHz: 3392.284
parport:
serial: 0000-0000 : serial 0000-0000 : serial

Versions:
gcc: gcc (Debian 8.3.0-6) 8.3.0
python: Python 3.7.3
git: git version 2.20.1
git commit: NA
tcl: 8.6
tk: 8.6
glade: not_in_PATH

linuxcnc_var all:

LINUXCNCVERSION: 2.9.0-pre0-4829-g0fbbb2910
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
REALTIME: /etc/init.d/realtime
RTS: uspace
HALLIB_DIR: /usr/share/linuxcnc/hallib
PYTHON: /usr/bin/python3

dpkg -l '*linuxcnc*':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================-============================-============-=====================================================================
un linuxcnc <none> <none> (no description available)
un linuxcnc-dev <none> <none> (no description available)
un linuxcnc-doc <none> <none> (no description available)
ii linuxcnc-doc-en 1:2.9.0~pre0.4829.g0fbbb2910 all motion controller for CNC machines and robots (English documentation)
un linuxcnc-sim <none> <none> (no description available)
un linuxcnc-sim-dev <none> <none> (no description available)
ii linuxcnc-uspace 1:2.9.0~pre0.4829.g0fbbb2910 amd64 motion controller for CNC machines and robots
ii linuxcnc-uspace-dev 1:2.9.0~pre0.4829.g0fbbb2910 amd64 PC based motion controller for real-time Linux