Two quesations about QtQuickVCP

Boris Skegin

unread,

Aug 14, 2019, 7:50:58 AM8/14/19

to Machinekit

Hallo.

1. Does anybody by chance has a vagrant box MachinekitSDK for jessie x86_64,

as this https://github.com/machinekoder/machinekit-vagrant/blob/master/Vagrantfile is a little bit outdated?

2. I installed MachinekitSDk on my local jessie machine.

I can compile and run my source code, but at least HAL Remore QML are not properly shown in the Designer.

Did anyone encounter such a problem and could solve it?

Thanks.

Regards

boris

Joonas

unread,

Aug 14, 2019, 12:54:10 PM8/14/19

to Machinekit

I've encountered the same on Debian stretch. The gui works but the qt creator seems to fail at importing the SDK so the buttons are not visible. I haven't had time to look into it much but it seems that either the install location is incorrect or they're missing the designer folder and metainfo file as outlined here. https://doc.qt.io/qtcreator/creator-qml-modules-with-plugins.html

Boris Skegin

unread,

Aug 17, 2019, 1:32:00 AM8/17/19

to Machinekit

Well, I actually also use stretch, just mixed it up above with jessie. My present Qt version is 5.12.4.

Did you check the examples https://github.com/machinekit/QtQuickVcp/tree/master/examples ? They seem to work even in the Designer.

BTW, do you know how to use ipc instead of tcp in haltalk.ini ? As in my case I have both the GUI and machinekit installation on the same machine...

Joonas

unread,

Aug 17, 2019, 3:51:23 AM8/17/19

to Machinekit

There seemed to be something weird going on when using multiple build targets or the sdk doesnt like 5.13 for some reason. I switched to 5.12.4 and not it's working somewhat. I'm trying to modify machineface for my robot application and you still can't see them on creator but in think its a feature at this point. It builds and works fine though.

No I haven't tried it. I also run them on the same machine but I'm working on just the ui at this point.

Boris Skegin

unread,

Aug 20, 2019, 2:50:31 PM8/20/19

to Machinekit

So your setup is similar to mine.

Let me ask you what "startup" times you have.

By saying "startup" up I mean the time span between starting your QML app and the very moment when all QML widgets

are fully shown/depicted.

b.

Joonas

unread,

Aug 20, 2019, 2:53:31 PM8/20/19

to Machinekit

Pretty fast, I don't saa any lagging if that's what you're asking. Though I only launch it from creator for now.

Boris Skegin

unread,

Aug 20, 2019, 3:09:06 PM8/20/19

to Machinekit

My "startup" times are between 15 and 20 seconds.

Are yours better/faster?

Joonas

unread,

Aug 20, 2019, 3:11:55 PM8/20/19

to Machinekit

I haven't timed it but I'd say well under 10. You can barely see the connection screen. Seems weird that its taking that long for you.

Paulo Sherring

unread,

Aug 25, 2019, 10:17:11 AM8/25/19

to Machinekit

Hey, just chipping in here. You could use TCP for Axis also, however, there would be a bit of additional overhead on connections. I've created a little line, called in setup.sh script, that switch from IPC <-> TCP:

echo 'Changing to Remote Mode'

sed -r '31 s/([^:]+).*/REMOTE=1/' /etc/linuxcnc/machinekit.ini > /tmp/machinekit.ini.temp

sudo mv /tmp/machinekit.ini.temp /etc/linuxcnc/machinekit.ini

echo 'Changing to Local Mode (IPC)'

sed -r '31 s/([^:]+).*/REMOTE=0/' /etc/linuxcnc/machinekit.ini > /tmp/machinekit.ini.temp

sudo mv /tmp/machinekit.ini.temp /etc/linuxcnc/machinekit.ini

There is probably a better way to do so, as I am not the most proficient in bash scripting :).

As for connection time, the first connection would take a little longer, as your client downloads the QML project and also there probably is a bit of overhead setting up the connection for the first - that is, for the first client. Subsequent connections here usually takes less time.