gcs-cli unable to execute any task like --home, --file etc but is connected. Works on Windows not on Linux

[willemdeschryver]

Hi,

I'm trying to get the gcs-cli running on a raspberrypi zero.
I tested the functionality of the cli interface on Windows using the following command.
This worked perfectly for my gemitsu 4040pro machine using GRBL 1.1h
java -Xmx256m -cp UniversalGcodeSender.jar com.willwinder.ugs.cli.TerminalClient -h

When i tried to port this to the RPIzero running raspberry OS I couldn't get it to work.
Connecting isn't the problem but running task like home is.

The same goes for running a file or reseting the alarm

What could be the problem?
Thank you for you help!

Greetings,
Willem

[breiler]

For some reason your controller responds with a weird message to the $G command:
GC:G0 G54 G17 G21 G90 G94 M5 M M9 T0 F0 S0

The single M in the response above is faulty. What is the output if you connect to the same CNC controller using a UGS GUI and type the command $G?

[willemdeschryver]

I'm not around the machine anymore. I got the same error on windows environment aswell, since these both use the same sourcecode i don't know if this will make a difference.
I will test the command tomorrow..
Thank you for your quick response!

[willemdeschryver]

I just tested the command $G
>>> $G [GC:G0 G54 G17 G21 G90 G94 M5 M M9 T0 F0 S0] ok

I get the same respons in the GUI.

[breiler]

What variant of GRBL are you using (where did you download it)?

What is the response of $I?

[willemdeschryver]

It's GRBL1.1h
it was preinstalled on the controller of the genmitsu 4040pro
>>> $I [VER:GD32 V2.1.20220827:] [OPT:VZL,35,254] ok

[breiler]

Ok this is probably the cause. They have changed the version string so that it looks very different than the original variant. UGS can't decipher it and doesn't know what type of controller it is connected to.

On your Windows machine you are probably using an older version of UGS (2.0.15 maybe?) and on your Linux machine you are using a later version.

As I haven't access to their firmware or hardware I will have to guess how to fix this.
I've made an attempt here: #2255

It should now be available in the latest nightly build here:
https://github.com/winder/Universal-G-Code-Sender#downloads

This only fixes the version string which should make it possible to connect to the machine. But we will probably not be able to parse the faulty $G-response which could cause other problems...

[willemdeschryver]

Hi, i just got the chance to test this out. Im getting the following error using the latest nightly build.
Error is the same when using start-cli.sh

[willemdeschryver]

I just tested all the previous versions (2.0.15-2.0.17) they both give the same error listed on my previous past. Only 2.0.18 is Running on the Rpi zero w

[willemdeschryver]

Running a command on windows give me this.

it homes the machine without any delay or trouble, it's the same .jar file

[willemdeschryver]

Hi, i switched my hardware o a RPI b3 on ths machine i can run the lastet nightly build.
Running the nightly build i get the following error. The machine will start after the error was thrown but i have the feeling this introduces some delay.

This error only throws when running home commands.

When stopping a cli command mind operation and rerunning an other close after i get the following error thrown

It seems to me that some responses of the cnc aren't catched.

Thank you for your time !