hazzy - Another touchscreen GUI

rodw wrote: Lets face it, its only something of interest to integrators like us on the forum, the average user won't even want to know about joints!

Well I consider myself a user rather than integrator and I am always happy when a joint is available.

Cheers, Phill.

newbynobi wrote: Hallo,

rodw is right, I solved the gmoccapy gantry homing issue. I also need a correct INI config, but I do check within getiniinfo the kins and some more stuff, to display the DRO or JOINTS Pos.

Take care, that till now the jogging problem is not solved. The user of a gantry is still able to jog one joint without homing the machine, I am working on that!

Norbert

Norbert, going off topic for a moment, I'm not totally convinced Gmoccapy has solved everything in relation to the changes in Master. I've had a number of errors in relation to limit switch and following errors (now fixed) that are reported on the command line but do not raise an error dialog window. I think errors like this were previously reported by Axis within the GUI. I'm not sure if its a GUI issue or a LCNC issue. One error I traced back to deep within the LCNC code and it appeared to be making an incorrect assumption as to what was causing the error due to JA changes. "Axis is misconfigured" when it wasn't.

Hallo Phill,

I have taken care of users like you
if you add <kinstype=both> to the KINS section, you get all joints prior to homing and you can switch modes with a GUI button or F12.

Norbert

@rodw,

Norbert, going off topic for a moment, I'm not totally convinced Gmoccapy has solved everything in relation to the changes in Master. I've had a number of errors in relation to limit switch and following errors (now fixed) that are reported on the command line but do not raise an error dialog window. I think errors like this were previously reported by Axis within the GUI. I'm not sure if its a GUI issue or a LCNC issue. One error I traced back to deep within the LCNC code and it appeared to be making an incorrect assumption as to what was causing the error due to JA changes. "Axis is misconfigured" when it wasn't.

I need more information about that, because I have not realized such a behavior. The GUI passes all errors and messages from linuxcnc to the pop up GUI messages. If the code do only a print message, than it will only appear in the terminal. I use that way to show informations on start up.

Norbert

newbynobi wrote: I need more information about that, because I have not realized such a behavior. The GUI passes all errors and messages from linuxcnc to the pop up GUI messages. If the code do only a print message, than it will only appear in the terminal. I use that way to show informations on start up.

Norbert

Norbert, I've reported this in my bug report thread in the Gmoccapy section to avoid derailing this thread.

Rod, Thanks you for mentioning that Gmoccapy issue here, as I think it relegates to (or is the same as) an issue I am having. Since switching to master I have noticed that my hazzy interface displays maybe 50% of LinuxCNC errors, before it reliably displayed all of them. I can't figure out what is causing this, but I am fairly certain it is not a problem with Gmoccapy, (or hazzy in my case). I am pretty sure the problem is in the LinuxCNC error channel as my own messages are always displayed, and I have not changed any of that code since switching to master. As far as I can tell the the error channel misses errors of all types randomly, and since it is not consistent I am having trouble taking down were the problem originates.

I am waiting to see what Norbert says, if he agrees that the problem is likely not in the UI, I'll do some deeper digging and see if there is a way to solve this problem.

Cheers,
Kurt