Machinekit Client discovers no instances after 4-6/may-2015

[Michael Brown]

I have been running a dated version of Machinekit Client for some time, due to my 2/4 Gantry modifications

in Machineface / Machinekit client, and noticing this problem trying newer versions of Machinekit Client.

But would now like to update 

So I decided to dig into this issue and found out that:

First compiling and installing an earlier/older version of QtQuickVCP

And then compiling Machinekit Client in QtCreator (Debian 8)

Made my configs reappear again in the Available Instances window

The actual QtQuickVCP  commit which made my bbb's invisible

 started in a branch named mklauncher3:

Revision: ac0f117
Author: Alexander Rössler
Date: 2015-05-04 15:43:50
applicationcontrols/ConnectionWindow: reworked ConnectionWindow, using
Private module

and got merged into master 6-may-2015

Revision: de83143
Author: Alexander Rössler
Date: 2015-05-06 12:45:30
applicationcontrols/ConnectionWindow: reworked ConnectionWindow, using
Private module

I'm running Machinekit Client mostly on Debian 8.0 -64-bit

But have also tested on  Android(no-go, didn't try earlier releases)

Win-7Pro-64 (binaries earlier than 6-may-2015 work)

MAC-Pro-64 (binaries earlier than 6-may-2015 work)

Linux-64 (binaries earlier than (6-may-2015 work)

I have also tried launching Alesanders latest Uni-print-3d config (both ve3 and ve4 branch)

Same issue ....

I'm not sure if this issue arises from my network-setup 

if its the builtin network filter in Machinekit Client 

thats pulling my leg ....

[Daren Schwenke]

I can confirm this for x86_64 at least.

[Alexander Rössler]

Sorry that I have informed no one about the development that is
ongoing. This is due the fact that the Machienkit-Client now connects to
the mklauncher.

To explain it quickly. Machinekit-Client can now launcher Machinekit
Instances. One needs to create a launcher.ini
(e.g. https://github.com/thecooltool/machinekit-configs/blob/master/launcher.ini)
and then start the mklauncher with "mklauncher <config-base-dir>". The
command works recursively meaning that you can run mklauncher . in you
home directory to list all configurations.

Connecting works similar as previously with the difference that you can
now start/stop instances. Launching mklauncher at boot time with systemd
is possible and recommended (see
https://github.com/strahlex/asciidoc-sandbox/wiki/Starting-a-Machinekit-configuration-at-boot)

Regards,
Alexander

--
Alexander

[Daren Schwenke]

I realize you are probably developing for your hardware, but I'm not sure making AP-Hotspot a requirement was a good idea.  It seems very few wireless chipsets (or drivers maybe) actually support 'master' mode, at least in the states.  I tried this before for another project and of the 5 different wireless adapters I was able to test, none of them could be switched to 'master' mode.

It's a great feature for those with compatible hardware.  Perhaps you got lucky.

On Wednesday, June 17, 2015 at 6:41:39 PM UTC-4, Michael Brown wrote:

[Michael Brown]

Thanks Alexander got it to work ...
Great to see config images too ...

On Thursday, June 18, 2015 at 10:19:22 AM UTC+2, Alexander Rössler wrote:

Sorry that I have informed no one about the development that is
ongoing. This is due the fact that the Machienkit-Client now connects to
the mklauncher.

To explain it quickly. Machinekit-Client can now launcher Machinekit
Instances. One needs to create a launcher.ini
(e.g. https://github.com/thecooltool/machinekit-configs/blob/master/launcher.ini)
and then start the mklauncher with "mklauncher <config-base-dir>". The
command works recursively meaning that you can run mklauncher . in you
home directory to list all configurations.

Inspiring to see the modular configs, but also a bit overwhelming so

I made a more modest conversion by just adding a modded version of the singular

Uni-print-3D/blob/ve4/launcher.ini 

+ a .jpg image in /image folder

 

Connecting works similar as previously with the difference that you can
now start/stop instances. Launching mklauncher at boot time with systemd
is possible and recommended (see
https://github.com/strahlex/asciidoc-sandbox/wiki/Starting-a-Machinekit-configuration-at-boot)

I ran mklauncher directly on the relevant config folder

as I have configs for different hardware printers in the same folder

However it would be nice if it was possible to see configs with different IP addresses(on different BBB's) 

in the same window (Available Launchers)(the one that shows the images),

instead of having to go back to the Available Instances window. 

Best wishes Michael

[Daren Schwenke]

On Thursday, June 18, 2015 at 11:30:55 AM UTC-4, Michael Brown wrote:

Thanks Alexander got it to work ...
Great to see config images too ...

On Thursday, June 18, 2015 at 10:19:22 AM UTC+2, Alexander Rössler wrote:

Sorry that I have informed no one about the development that is
ongoing. This is due the fact that the Machienkit-Client now connects to
the mklauncher.

To explain it quickly. Machinekit-Client can now launcher Machinekit
Instances. One needs to create a launcher.ini
(e.g. https://github.com/thecooltool/machinekit-configs/blob/master/launcher.ini)
and then start the mklauncher with "mklauncher <config-base-dir>". The
command works recursively meaning that you can run mklauncher . in you
home directory to list all configurations.

Inspiring to see the modular configs, but also a bit overwhelming so

I made a more modest conversion by just adding a modded version of the singular

Uni-print-3D/blob/ve4/launcher.ini 

+ a .jpg image in /image folder

 

Connecting works similar as previously with the difference that you can
now start/stop instances. Launching mklauncher at boot time with systemd
is possible and recommended (see
https://github.com/strahlex/asciidoc-sandbox/wiki/Starting-a-Machinekit-configuration-at-boot)

I ran mklauncher directly on the relevant config folder

as I have configs for different hardware printers in the same folder

This worked for me as well.