Gmoccapy - A new screen for linuxcnc

Hallo Nils,

just ask, if you need any help, there are many people around, using already gmoccapy and some of them on industrial machines producing parts for commercial purpose.

I did not get any bug report in the last 14 days, so I do hope, the users are satisfied

Norbert

gmoccapy 1.1.2

scaling bug for jog wheel pin solved

- after changing units according to G20 / G21 the scales to be
applied to the jog wheel pin (jog_vel and max_vel has not been
changed, resulting in very large jumps after changing from
metric to imperial, i.e. one count should move the slider 100
increments in metric, but did that amount also in imperial,
insteadt only advancing 4 steps.
- all sliders and vel infos are now changing according to G20/G21
beeing active.
- There is still work to do on the offsetpage widget,
as it will not accept values in display units at the moment

Norbert

i am check auto tool change. Some time or when restart linuxcnc
Not get correctly value from #<_hal[gmoccapy.blockheight]>. For example i am set 30. Turn off linuxcnc. After start , set sero (Set offset and put 0 in cell)and start autozero. Turn on debug. and me show 30. But if i am set zero when push button Set blockheight it get correctly zero.

2.6 pre Gmoccapy 1.1.2 it error when start programm.

Found an error!
The following information may be useful in troubleshooting:

Traceback (most recent call last):
File "/usr/bin/gmoccapy", line 2573, in on_tbtn_use_screen2_toggled
self.widgets.window2.show()
File "/usr/lib/pymodules/python2.6/gmoccapy/widgets.py", line 36, in __getattr__
raise AttributeError, "No widget %widget" % attr
ValueError: unsupported format character 'w' (0x77) at index 11

Hallo Straga,

the hal value Blockheight should be zero after a restart of linuxcnc / gmoccapy, I did that on purpose.
I am not able to follow you in detail, where do you a auto Zero? Do you mean homing?

And you should not set a Z Value with touch off, as you did that already with entering the block height value.

Have you seen the auto tool measurement video?
You will find the link on the WIKI.

The error you mentioned (self.widgets.window2.show()) could not happen on program start.
I beleave you pushed the button "Show Screen 2" on the settings page. If so, then there is no file gmoccapy2.glade in your config dir.

But you are right, I should check if that file is there, and if it isn't, the button should not be sensitive.
I will change that.

Norbert

i am delete gmoccapy_development.pref, and error widget not more.

I play around with auto tool measurement, when change tool. I am write later - check all before again.

gmoccapy 1.1.4

ver. 1.1.4
- added again the gcode.lang file, it got lost, after changing gmoccapy to be
stand alone (Better gcode highlight in my opinion)
- the show screen2 button is now only sensitive if a file gmoccapy2.glade does
exist in the config dir.

Norbert

foam XYUV ?

Hallo nameless,

YXUV is has not been implemented yet, but can easily be done.
What are the special needs for a foam cutter? Do you just need the mentioned Joints/axis, or special temperatur and settings parameter?

Look at gmoccapy plasma more a stronger modified version, and also the embedded tabs section of the WIKI mayy help.

If there are more people interested in a XYUW Version of gmoccapy, I may include code for that.

Norbert

gscreen:
GEOMETRY = xyuv
FOAM =1

[TRAJ]

AXES = 9
COORDINATES = X Y U V

[AXIS_0]-[AXIS_8]

HALFILE = core_sim9.hal
HALFILE = axis_manualtoolchange.hal
HALFILE = simulated_home.hal
HALFILE = locking_indexer.hal

foam.ngc
err

gmoccapy?

GLADEvcp widgets
hal_action_open
??