axises are dead after configuration
17 Apr 2019 06:06 #131038
by sm
Replied by sm on topic axises are dead after configuration
Chris, you are awesome!
When this build will be publicly available?
When this build will be publicly available?
Please Log in or Create an account to join the conversation.
17 Apr 2019 06:16 #131039
by cmorley
Replied by cmorley on topic axises are dead after configuration
If you are using 2.7.x then this might not be so helpful for you.
The master version of linuxcnc is the leading edge of development.
Master and 2.7.x are quite different because the concept of axes and joints are separated.
The buildbot used to make public builds, but it seems broken.
I always build from source, so am not up on the best way to get it prebuilt.
Chris M
The master version of linuxcnc is the leading edge of development.
Master and 2.7.x are quite different because the concept of axes and joints are separated.
The buildbot used to make public builds, but it seems broken.
I always build from source, so am not up on the best way to get it prebuilt.
Chris M
Please Log in or Create an account to join the conversation.
17 Apr 2019 06:22 #131040
by sm
Replied by sm on topic axises are dead after configuration
yes, I am running 2.7.<something>
oh, well... I can live with that. it is super that it will be available some day.
I am not planning to build it out of source as it is not the first priority for me right now and too much troubles (make separate linux box with deb just for this). but! it is nice to know, that some day I will be able to choose this configuration and that will NOT be for lathe!
Thank you, Chris!
oh, well... I can live with that. it is super that it will be available some day.
I am not planning to build it out of source as it is not the first priority for me right now and too much troubles (make separate linux box with deb just for this). but! it is nice to know, that some day I will be able to choose this configuration and that will NOT be for lathe!
Thank you, Chris!
Please Log in or Create an account to join the conversation.
18 Apr 2019 19:42 #131178
by sm
Replied by sm on topic axises are dead after configuration
Hi Chris,
I am sorry asking it here (and I made it as a separate topic/question), but if you could have a moment and take a look at:
forum.linuxcnc.org/38-general-linuxcnc-q...uestion-about-offset
I would really appreciate your suggestion you might have on this matter.
I am trying to resolve it for several days without much success.
basically I am trying to understand what and where I need to fix. I configured machine using stepconf and tested both drives. it looks like they are traveling correct distance. when I load a file:
linxcnc shows it will travel 10mm. I am cutting the piece - it comes out 4.44.
I don't get it, why this scaling? I see in linuxcnc.var 5241=-0.44 and 5242=-0.44. I've been trying to set those manually to 0, but they are stubbornly coming back.
are they the ones who is doing it? or it is something else? how do i reset in linuxcnc everything (including 5241 and 5242) to zeros, so, I could be sure that whatever is in the gcode will be implemented?
thank you!
I am sorry asking it here (and I made it as a separate topic/question), but if you could have a moment and take a look at:
forum.linuxcnc.org/38-general-linuxcnc-q...uestion-about-offset
I would really appreciate your suggestion you might have on this matter.
I am trying to resolve it for several days without much success.
basically I am trying to understand what and where I need to fix. I configured machine using stepconf and tested both drives. it looks like they are traveling correct distance. when I load a file:
linxcnc shows it will travel 10mm. I am cutting the piece - it comes out 4.44.
I don't get it, why this scaling? I see in linuxcnc.var 5241=-0.44 and 5242=-0.44. I've been trying to set those manually to 0, but they are stubbornly coming back.
are they the ones who is doing it? or it is something else? how do i reset in linuxcnc everything (including 5241 and 5242) to zeros, so, I could be sure that whatever is in the gcode will be implemented?
thank you!
Please Log in or Create an account to join the conversation.
- Mike_Eitel
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1159
- Thank you received: 185
18 Apr 2019 20:00 #131179
by Mike_Eitel
Replied by Mike_Eitel on topic axises are dead after configuration
Hi SM
Sorry for a question: When you do manual jogging, does the machine travel the shown distance.
Mike
Sorry for a question: When you do manual jogging, does the machine travel the shown distance.
Mike
Please Log in or Create an account to join the conversation.
18 Apr 2019 20:32 #131183
by sm
Replied by sm on topic axises are dead after configuration
Hi Mike.
yes, it does! that is the thing! I ran stepconf and tested each drive. they moved correctly. the code:
N0 ;(square1.ngc)
N1 G92.1(reset G92 and set values to zero)
N2 G17 (Plane Select. XY = default )
N3 G21 (use millimeters)
N4 G54 (select coordinate system. must be set before G42/G42)
N5 G90 (absolute distance mode)
N6 G40 (cancel cutter compensation)
N7 G61 (Exact path mode)
N8 F0.10 (set feed)
N9 ;G53 G0
N10 ;G54 X0.36 Y0.36
N11 G1 X1.40 Y1.00
N12 G1 X10.60 Y1.00
N13 G1 X11.00 Y1.40
N14 G1 X11.00 Y10.60
N15 G1 X10.60 Y11.00
N16 G1 X1.40 Y11.00
N17 G1 X1.00 Y10.60
N18 G1 X1.00 Y1.40
N19 G1 X1.40 Y1.00
N20 G40
N21 M2
I made intentionally not using any cutter compensation or offset (unless I am wrong and you see something in this code)
so, square should be 8.12mm as I calculate it. instead it comes out 4.44x4.45mm (well perhaps 0.01-.02) could be precision's matter, but still it is far from 8mm. linuxcnc finishes the piece and it does cut square. this tells me that both drives are moving correctly and in sync. but something does this scaling and I cannot figure out what it is.
yes, it does! that is the thing! I ran stepconf and tested each drive. they moved correctly. the code:
N0 ;(square1.ngc)
N1 G92.1(reset G92 and set values to zero)
N2 G17 (Plane Select. XY = default )
N3 G21 (use millimeters)
N4 G54 (select coordinate system. must be set before G42/G42)
N5 G90 (absolute distance mode)
N6 G40 (cancel cutter compensation)
N7 G61 (Exact path mode)
N8 F0.10 (set feed)
N9 ;G53 G0
N10 ;G54 X0.36 Y0.36
N11 G1 X1.40 Y1.00
N12 G1 X10.60 Y1.00
N13 G1 X11.00 Y1.40
N14 G1 X11.00 Y10.60
N15 G1 X10.60 Y11.00
N16 G1 X1.40 Y11.00
N17 G1 X1.00 Y10.60
N18 G1 X1.00 Y1.40
N19 G1 X1.40 Y1.00
N20 G40
N21 M2
I made intentionally not using any cutter compensation or offset (unless I am wrong and you see something in this code)
so, square should be 8.12mm as I calculate it. instead it comes out 4.44x4.45mm (well perhaps 0.01-.02) could be precision's matter, but still it is far from 8mm. linuxcnc finishes the piece and it does cut square. this tells me that both drives are moving correctly and in sync. but something does this scaling and I cannot figure out what it is.
![:( :(](/media/kunena/emoticons/sad.png)
Please Log in or Create an account to join the conversation.
- Mike_Eitel
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1159
- Thank you received: 185
18 Apr 2019 21:00 #131187
by Mike_Eitel
Replied by Mike_Eitel on topic axises are dead after configuration
Sorry, I move in smaller steps.
Just mount a needle in your spindle and then use jogging (not g code and not stepconf but in axis or what gui u use.)
You move by keyboard jogging 100 mm and how much moved the needle in your machine. If I gues your description right: these two values are not the same. So you have to correct the scaling until all axes are correct.
Then do simple g code commands in midi mode
After that you can return to your program...
Mike
Just mount a needle in your spindle and then use jogging (not g code and not stepconf but in axis or what gui u use.)
You move by keyboard jogging 100 mm and how much moved the needle in your machine. If I gues your description right: these two values are not the same. So you have to correct the scaling until all axes are correct.
Then do simple g code commands in midi mode
After that you can return to your program...
Mike
Please Log in or Create an account to join the conversation.
18 Apr 2019 21:02 #131188
by sm
Replied by sm on topic axises are dead after configuration
Hi Chris,
it is my understanding that you are developer for linuxcnc.
May I propose to use sqlite for all linuxcnc configurations settings instead of linuxcnc.var and the rest setting/configuration files?
I think that would significantly simplify development/configuration/usage.
sqlite is present practically everywhere on every platform. it is fast and small. its file/database is self-contained, so, it is easy to move configured linuxcnc to another machine if needed/appropriate.
it will be much easier to develop gui as well as all the settings/configurations can be read from it.
I see some other benefits as well.
Regards,
Slava
it is my understanding that you are developer for linuxcnc.
May I propose to use sqlite for all linuxcnc configurations settings instead of linuxcnc.var and the rest setting/configuration files?
I think that would significantly simplify development/configuration/usage.
sqlite is present practically everywhere on every platform. it is fast and small. its file/database is self-contained, so, it is easy to move configured linuxcnc to another machine if needed/appropriate.
it will be much easier to develop gui as well as all the settings/configurations can be read from it.
I see some other benefits as well.
Regards,
Slava
Please Log in or Create an account to join the conversation.
18 Apr 2019 21:05 #131190
by sm
Replied by sm on topic axises are dead after configuration
Thank you, Mike.
so, if find out that this needle move shorter distance, how do I correct it?
Thank you.
so, if find out that this needle move shorter distance, how do I correct it?
Thank you.
Please Log in or Create an account to join the conversation.
- Mike_Eitel
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1159
- Thank you received: 185
18 Apr 2019 21:26 #131196
by Mike_Eitel
Replied by Mike_Eitel on topic axises are dead after configuration
Sorry Slava, I think first thing you should do is sit down and read the doc.
And understand the concept behind the sw you want to use.
In this case look for the ini file and especially the parts where STEP_SCALE is described.
Mike
And understand the concept behind the sw you want to use.
In this case look for the ini file and especially the parts where STEP_SCALE is described.
Mike
Please Log in or Create an account to join the conversation.
Time to create page: 0.094 seconds