Gmoccapy - A new screen for linuxcnc

@Norbert,

No problem, I am not in a hurry, and can bypass the problem easily in my ini file.

Frans

@clive,

You can open a new thread here in the forum if you have any questions. If you prefer german as language, just use Peters cnc ecke

Norbert

@Nobert

Thanks for the reply I have opened a thread but not had any answers.

Would you mind giving me the correct command line and procedure to update Gmoccapy from the version on the live cd 2.6 which is 1.3.1 I think.

Clive

@Clive,

do you know the WIKI?
Or use also the documentation of the installed pakage.

• Open->Synaptic Package Manager
• In the Quick Search bar at the top, type linuxcnc.
• Click the check box to mark the new linuxcnc package for installation.
• Click the Apply button, and let your computer install the new package.

you will need a Internet connection to do the update.
And you should be done.

Norbert

@Nobert

Yes I have read and printed it out.
Thanks I will try that. I have already done (or thought I had) the updates for Linuxcnc. 2.6

I also don't see a virtual keyboard and notice that on page about 85 I see it has been mentioned about the matchbox keyboard so I will try and get that.

I have read all 114 page of this post and would like to thank you and the testers for all the effort and time you have put into this project.

Best regards

Clive

Ok update I have patched to the latest linuxcnc then Linux wouldn't load then I remembered reading about the POSTGUI_HALFILE so I commented that out of the ini file and it still did not run.

according to the error message it failed on:-

Debug file information:
./Warco_18.hal:6: Can't find module 'probe_parport' in /usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
7823

I then commented out loadrt probe_parport from the Hal ini Then the programme loaded.

I also installed matchbox key board.

My question a) is what do I do to resolve the hal ini problem

b) The button for loading files seems to be greyed out so how do I load gcode.

c) The jog icons below the dro seem to disappear sometimes.

d) Is it not possible to not to have to HOME before you can get further to touch off etc.

Sorry to be a pain but I have tried to resolve it and I am failing.
I have attached the ini,hal and error file










Clive

Norbert,

I have updated to the latest GMOCAPPY and linuxcnc. After I installed the upgrades I get an error message.


Operator Message

Important Warning

G-Code error in turn-od.ngc
Near Line 65
/..../.../linuxcnc/nc_files/ngcgui_files/turn-od.ngc
file ended with no percent sign or program end.

it does not come up with every time it is random.
Also I am havig a problem when this message comes up with a tool change if I ack the tool change and then stop the
program the interface will goo to sleep sometimes and may or maynot be usable again unless I reboot. I also have a problem when
I use my hardware estop with the interface locking up for several minutes.

Thank you for your hard work.

Jim

Nobert,

Can you explain how the 100% button works for feed override?
I've connected some hardware buttons to my machine for spindle and feed overrides.
I've got two sets of three buttons: increase button, decrease button, and a third button that I want to act as a reset / 100% button.
I have the increase and decrease button working via HALUI but can't find out how to use a button to set to 100%. I can't find a HALUI pin for it.

I tried looking in the gmoccapy files but I have very limited understanding of programming.

Thanks.

@Clive,

You sayed you patched something? Do you use 2.6 or 2.7 or master?

loadrt probe-parport should work, but I do not know why it does not on your machine.

The postgui hal stuff may be caused, because you do use the manual toolchange stuff in your hal file.

You may include NO_FORCE_HOMING = 1 in your ini to not to need to home.

Norbert

@Jim,

with the latest update you got also a g-code check, that does cause the message. Please begin and end you file with %

See gcode documents for details why to do that.

The other errors could be caused, because of your hal connections. If you emergency button do give a feedback, and that feedback is also given from gmoccapy, it could cause a endless loop

Please post your hal connection part regarding the estop.

Norbert