Gmoccapy - A new screen for linuxcnc
27 May 2013 04:01 #34734
by emcPT
I never used it, as I am still building my machine, but this is also very important to me.
In my previous search, I found a post of ArcEye that he said that he implemented it. I think it can manage only type 1 of the cycles (no recesses), but it is a start.
Filipe
Replied by emcPT on topic Gmoccapy - A new screen for linuxcnc
Hello Norbert ... My lathe is producing super good.
I have work in macros, remap, ngcgui ... I'm not familiar with these things.
I have the desire to see my machine, working cycles (G70, G71, G73).
G71, G72 P (initial line) Q (finish line) R (retract) D (depth of cut) F (Feed) U (X stock) W (Z stock)
G70 P (initial line G71, G72) Q (final line G71, G72) F (feed)
Sincerely,
Jorge Viloria
I never used it, as I am still building my machine, but this is also very important to me.
In my previous search, I found a post of ArcEye that he said that he implemented it. I think it can manage only type 1 of the cycles (no recesses), but it is a start.
Filipe
Please Log in or Create an account to join the conversation.
27 May 2013 22:04 #34756
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@Jorge
@Felipe
with remap you can do what ever you want! But the linuxcnc feature has nothing to do with gmoccapy, because gmoccapy is only a User Interface, not the machine control!
Norbert
@Felipe
with remap you can do what ever you want! But the linuxcnc feature has nothing to do with gmoccapy, because gmoccapy is only a User Interface, not the machine control!
Norbert
Please Log in or Create an account to join the conversation.
28 May 2013 00:23 - 28 May 2013 00:26 #34766
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@All
Please do not use G95, nor in gmoccapy or either gscreen!!!!!!!
There is an error witch I do not find at the moment, I will mail today to Chris and ask for help!
Here are the details:
If you enter in MDI
G21
G95 F0.01 S450 M3
G1 Z-10
The feed should be 0.01 mm / rev, with the spindle speed of 450 rpm this should give you a feed of 4,5 mm/min, but you will get 270 mm / min.
As you see the value is multiplied by 60!
IMHO the error must be in a part of gscreens emc interface, because in axis it is doing fine!
I changed the min screen size of gmoccapy to fit to a screen with 979 x 750 Pixel, so it should fit on most common screens.
Will push soon.
Norbert
Please do not use G95, nor in gmoccapy or either gscreen!!!!!!!
There is an error witch I do not find at the moment, I will mail today to Chris and ask for help!
Here are the details:
If you enter in MDI
G21
G95 F0.01 S450 M3
G1 Z-10
The feed should be 0.01 mm / rev, with the spindle speed of 450 rpm this should give you a feed of 4,5 mm/min, but you will get 270 mm / min.
As you see the value is multiplied by 60!
IMHO the error must be in a part of gscreens emc interface, because in axis it is doing fine!
I changed the min screen size of gmoccapy to fit to a screen with 979 x 750 Pixel, so it should fit on most common screens.
Will push soon.
Norbert
Last edit: 28 May 2013 00:26 by newbynobi. Reason: added a comment
Please Log in or Create an account to join the conversation.
28 May 2013 00:41 - 28 May 2013 00:48 #34768
by jlviloria
Replied by jlviloria on topic Gmoccapy - A new screen for linuxcnc
Norbert,
you know I'm using gmoccapy before industry was using.
I have not had this problem. the sample that moves forward but should be.
is more my machine has a fast speed of 10000mm/min, but shows 6000 mm / min, but my machine is moved to 10000mm/min.
I had thought that the problem was only visualization of the actual feed.
I assure you that my machine is working as it should, just does not show the actual values.
I am willing as a guinea pig to do the tests.
Jorge Viloria
you know I'm using gmoccapy before industry was using.
I have not had this problem. the sample that moves forward but should be.
is more my machine has a fast speed of 10000mm/min, but shows 6000 mm / min, but my machine is moved to 10000mm/min.
I had thought that the problem was only visualization of the actual feed.
I assure you that my machine is working as it should, just does not show the actual values.
I am willing as a guinea pig to do the tests.
Jorge Viloria
Last edit: 28 May 2013 00:48 by jlviloria.
Please Log in or Create an account to join the conversation.
28 May 2013 00:54 #34771
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Jorge,
did you enter exactly the code I mentioned?
If so, the machine should need more than 2 minutes to finish the move, but you will see it uses not even 30 seconds!
I believe you are mixing two things!
MAX Vel has nothing to do with the bug I mentioned.
Please explain with label is not showing the correct value?
Please add your INI File and your hidden preference file.
Norbert
did you enter exactly the code I mentioned?
If so, the machine should need more than 2 minutes to finish the move, but you will see it uses not even 30 seconds!
I believe you are mixing two things!
MAX Vel has nothing to do with the bug I mentioned.
Please explain with label is not showing the correct value?
Please add your INI File and your hidden preference file.
Norbert
Please Log in or Create an account to join the conversation.
28 May 2013 01:24 - 28 May 2013 01:29 #34774
by jlviloria
Replied by jlviloria on topic Gmoccapy - A new screen for linuxcnc
Norbert
None label shows the actual feed. show erroneous values.
The machine when running command G95, an alarm went out, I got to comment on these two lines and work.
def on_scl_feed_value_changed(self, widget, data=None):
feed_override = self.widgets.scl_feed.get_value() / 100
#real_feed = round(int(self.widgets.active_feed_label.get_text()) * feed_override)
#self.widgets.lbl_feed_act.set_text("F %d" %real_feed)
self.emc.feed_override(feed_override)
lbl_feed_act = disabled
lbl_current_vel = erroneous
but the machine moves well, at least as axis or industrial
I have my record the machining times have not changed.
attached my files.
Image Check the "tiempo ciclo" you see that just goes for 5 and takes more than 2 minutes
None label shows the actual feed. show erroneous values.
The machine when running command G95, an alarm went out, I got to comment on these two lines and work.
def on_scl_feed_value_changed(self, widget, data=None):
feed_override = self.widgets.scl_feed.get_value() / 100
#real_feed = round(int(self.widgets.active_feed_label.get_text()) * feed_override)
#self.widgets.lbl_feed_act.set_text("F %d" %real_feed)
self.emc.feed_override(feed_override)
lbl_feed_act = disabled
lbl_current_vel = erroneous
but the machine moves well, at least as axis or industrial
I have my record the machining times have not changed.
attached my files.
Image Check the "tiempo ciclo" you see that just goes for 5 and takes more than 2 minutes
Last edit: 28 May 2013 01:29 by jlviloria.
Please Log in or Create an account to join the conversation.
28 May 2013 02:26 #34782
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Jorge,
with the values you entered the cycle time must be about 10 minutes, but your cycle time is only 2 min 53 so IMHO the G95 cycle is not working correct.
By the way, I like the cycle time frame, can you mail me the corresponding code?
An about the max Vel , I could not find any error in your config, so if you jog both axis at ones with G0 the actual speed label should indicate something around 10000 mm/min and not only 6000.
I will check tomorow my code, may be I limited the values in some code snipped.
Norbert
with the values you entered the cycle time must be about 10 minutes, but your cycle time is only 2 min 53 so IMHO the G95 cycle is not working correct.
By the way, I like the cycle time frame, can you mail me the corresponding code?
An about the max Vel , I could not find any error in your config, so if you jog both axis at ones with G0 the actual speed label should indicate something around 10000 mm/min and not only 6000.
I will check tomorow my code, may be I limited the values in some code snipped.
Norbert
Please Log in or Create an account to join the conversation.
28 May 2013 02:35 - 28 May 2013 03:21 #34784
by jlviloria
Replied by jlviloria on topic Gmoccapy - A new screen for linuxcnc
as I mention, I always had "cycle time" and values not changed, I come from AXIS.
total time of 5:14 minutes.
cycle time is not a widgets is an component HAL :
linuxcnc.org/docs/2.5/html/man/man9/time.9.html
For me it is a problem of how to display the feed. as if he had the wrong scale. An error of those scales is reflected in the finished
Jorge Viloria
total time of 5:14 minutes.
cycle time is not a widgets is an component HAL :
linuxcnc.org/docs/2.5/html/man/man9/time.9.html
For me it is a problem of how to display the feed. as if he had the wrong scale. An error of those scales is reflected in the finished
Jorge Viloria
Last edit: 28 May 2013 03:21 by jlviloria.
Please Log in or Create an account to join the conversation.
28 May 2013 14:55 #34813
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@Jorge,
unfortunately I can not follow you.
On my machine speeds are shown as they should, but G 95 has a problem.
Norbert
unfortunately I can not follow you.
On my machine speeds are shown as they should, but G 95 has a problem.
Norbert
Please Log in or Create an account to join the conversation.
28 May 2013 14:56 #34814
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
gmoccapy - ver. 0.9.3.1 has been pushed
- Changed the required screen size to fit on 979 x 750
- A message window will warn the user in case he try to use G95
Norbert
- Changed the required screen size to fit on 979 x 750
- A message window will warn the user in case he try to use G95
Norbert
Please Log in or Create an account to join the conversation.
Time to create page: 0.161 seconds