Gmoccapy - A new screen for linuxcnc

Norbert,
It is looking very good. Can I give some feedback if I may please?

1: The DRO tab opens up to big so the DRO are cut off to the right
2: The last button on jog increments shows inches while the rest show mm
3: Under settings - the keyboard shortcuts frame is to small
4:In the settings - appearance-dro the first radio button label has a typo (Schow -> Show)

Thanks a lot for all your hard work on this. I am really happy that you are doing it for us.

Yes you are welcome to give feedback!

1. You are right, but this is only an example for an embedded tab. If you click in the bottom button list the button "make the preview as large as possible" You will see it fits to the screen. I will make this a little bit smaller to fit better.

2. That is on purpose! You can mix them around like you like, just change the INCREMENTS line of your INI file, see also the WIKI

3. Only if you use the GUI with smaller size than 768 height I will make the buttons "log Actions and Close" small in one of the next releases.

4. Will be fixed with the next release, but not in 0.9.3.2 witch is finished already and waiting to be pushed from Chris.

Norbert

The problem is in my configuration HAL.


I had noticed that my had a problem on the scale.

My HAL.

#setp scale.spindle.gain 60 before
setp scale.spindle.gain 40 now
setp lowpass.spindle.gain 1.000000
net spindle-vel-fb => lowpass.spindle.in
net spindle-fb-filtered-rps lowpass.spindle.out => abs.spindle.in
net spindle-fb-filtered-abs-rps abs.spindle.out => scale.spindle.in
net spindle-fb-filtered-abs-rpm scale.spindle.out

postgui.hal:

net spindle-fb-filtered-abs-rpm gscreen.hal_hbar_spindle_feedback




but I have another problem, sometimes when I run s100 m3, the spindle turns me on more or less at 180-200 rpm. I do not understand why this happens, when it happens reset, and again I run s100 m3 and if you turn 100 rpm.

but I have another problem, sometimes when I run s100 m3, the spindle turns me on more or less at 180-200 rpm. I do not understand why this happens, when it happens reset, and again I run s100 m3 and if you turn 100 rpm.

Do you have set 180 rpm in your settings page as start rpm?

I am able to reproduce this, when giving the command S 100 M3 just after homing.

If I do S100 in one line and M3 in an other, this will not happen.

I will investigate how to avoid this.

Norbert

Thanks Norbert. I am busy with a mill and a lathe for my own shop so I am very excited about using the screen.

Norbert.

if that is what is happening. I have my machine set to s180.

well at least we found something.

Remember I am here willing to try or test anything.

Thanks,

Jorge Viloria

Do you have set 180 rpm in your settings page as start rpm?

I am able to reproduce this, when giving the command S 100 M3 just after homing.

If I do S100 in one line and M3 in an other, this will not happen.

I will investigate how to avoid this.

I think I found a solution, I mailed a patch to Chris, I will inform as soon he pushed it.

Norbert

gmoccapy 0.9.3.2 released!

ver. 0.9.3.2

- alligned the jog_button and jog_rates frame on the top (just cosmetic)
- The Page-up and Page_Down keyboard keys moved the Z axis in oposide directions
- Feed values will only be shown with digit if G95 is active
- added classicladder button to the list of buttons to be able to handle it with hardware button
- changed hardware button handling to fit also to lathe mode
- included a test to avoid speeding the spindle over its limit using the spindle speed overide
i.e. max = 6000 but S = 5500 and overide = 120 % would result in 6600, but only 6000 is possible
- also check spindle speed if the commands are given trough MDI and overide is to high will reduce
the overide value to max allowed

Norbert

@Jorge,

0.9.3.2 fixes the spindle bug you found, but unfortunately not jet the G95 bug.

@Marius

3. Only if you use the GUI with smaller size than 768 height I will make the buttons "log Actions and Close" small in one of the next releases.
4. Will be fixed with the next release, but not in 0.9.3.2 witch is finished already and waiting to be pushed from Chris.

I fixed it, but needed to remove the patch afterwards, for incompatibility reasons, will be fixed in the nest release, witch will be a mayor one with new Features!

Norbert

Thanks a lot Norbert. Will Chris notify us here when the patched has been pushed?

Thanks a lot Norbert. Will Chris notify us here when the patch has been pushed?