Thank you for sharing vital content which I presently need it, but I've got a question; How come do you prefer the UCCNC over LinuxCNC, is there any particular technical reason?
Honestly - when I was making my milling machine I was looking for a good CNC controller with ethernet connection. I was considering linuxcnc with MESA and UCCNC w/ AXBB-E. The linuxCNC is really robust but quite tough to setup. UCCNC is simple and very robust comparing to Mach3. When I was looking for that controller - the AXBB-E was cheaper with all the I/O's and it was available with shipping to my location. I'd like to avoid USB/LPT controllers, as the ethernet ones are much more stable. Considering all that I tried UCCNC and for now it seems that UCCNC is doing all I need, it is very simple to setup. With all the positive feelings after the milling machine projects I decided to give a go with UCCNC with my second lathe project, using the UC300ETH which has a lot more I/Os.
Really interesting. I have a similar servo and I think you can divide the encoder frequency output directly in the servo driver. There is a function for that. EDIT: Ah ok, you already answered at the end of the video. Nevermind 🙂
Tak. Niestety mimo, że działa to bardzo dobrze do zadawania pozycji w trybie puls/dir to na wyjściu enkoderowym jest to samo, niezależnie od tego parametru. W innych driverach widziałem, że faktycznie jest opcja podziału tego sygnału, ale tutaj nie udało mi się do tego dokopać. Nawet pisałem do sklepu, który mi to sprzedał i nie byli w stanie mi pomóc z tematem.
This might just be because of the improvised wiring on your table, but the encoder signals shouldn't affect each other as much as they do on your oscilloscope, with a high signal on one pulls the other to almost half it's voltage. Also do you really need to connect the encoder to the controller for coordinating it with the other axis, doesn't the servo driver make sure the motor does what the controller asks, like it can do with open loop steppers?
About the signals - this actually can be the improvised wiring as you said. Not sure though. I'm going to use this servo for my spindle. The machine has to know precisely how the spindle rotates, to make sure the feed in the axial direction of the spindle will be exactly at point. All this is needed to do tapping / thread cutting.
It seems the subtitles didn't generate automaticaly due to some kind of a bug. I will try to make manually subtitles when I catch a moment but that needs some time. Thanks for the info!
i enjoy watching your vids thanks .
Great to hear!
Used devices in the description.
Thanks for watching! :)
good video my friend GBWM
Thanks Michel!
Very good!
Thanks!
Muito bom ! Ótimo passo a passo.
Obrigado! :)
Thank you for sharing vital content which I presently need it, but I've got a question; How come do you prefer the UCCNC over LinuxCNC, is there any particular technical reason?
Honestly - when I was making my milling machine I was looking for a good CNC controller with ethernet connection. I was considering linuxcnc with MESA and UCCNC w/ AXBB-E. The linuxCNC is really robust but quite tough to setup. UCCNC is simple and very robust comparing to Mach3. When I was looking for that controller - the AXBB-E was cheaper with all the I/O's and it was available with shipping to my location. I'd like to avoid USB/LPT controllers, as the ethernet ones are much more stable. Considering all that I tried UCCNC and for now it seems that UCCNC is doing all I need, it is very simple to setup. With all the positive feelings after the milling machine projects I decided to give a go with UCCNC with my second lathe project, using the UC300ETH which has a lot more I/Os.
Really interesting. I have a similar servo and I think you can divide the encoder frequency output directly in the servo driver. There is a function for that. EDIT: Ah ok, you already answered at the end of the video. Nevermind 🙂
Exactly as you say! :)
Sprawdzałeś może, czy użycie funkcji "Electronic gear" zmienia częstotliwość impulsów na wyjściu enkoderowym?
Tak. Niestety mimo, że działa to bardzo dobrze do zadawania pozycji w trybie puls/dir to na wyjściu enkoderowym jest to samo, niezależnie od tego parametru. W innych driverach widziałem, że faktycznie jest opcja podziału tego sygnału, ale tutaj nie udało mi się do tego dokopać. Nawet pisałem do sklepu, który mi to sprzedał i nie byli w stanie mi pomóc z tematem.
@GBWM_CNC Czyli to jest jakby fizyczne wyjście z enkodera, a nie przetworzone przez elektronikę. Powodzenia.
@@marcinbrozek23 Tak to wygląda
This might just be because of the improvised wiring on your table, but the encoder signals shouldn't affect each other as much as they do on your oscilloscope, with a high signal on one pulls the other to almost half it's voltage. Also do you really need to connect the encoder to the controller for coordinating it with the other axis, doesn't the servo driver make sure the motor does what the controller asks, like it can do with open loop steppers?
About the signals - this actually can be the improvised wiring as you said. Not sure though.
I'm going to use this servo for my spindle. The machine has to know precisely how the spindle rotates, to make sure the feed in the axial direction of the spindle will be exactly at point. All this is needed to do tapping / thread cutting.
Very interesting video but why can't I turn on the subtitles? Can you fix that?
It seems the subtitles didn't generate automaticaly due to some kind of a bug. I will try to make manually subtitles when I catch a moment but that needs some time. Thanks for the info!
@@GBWM_CNC Apparently it came back, it's strange but thanks anyway.
@@Algone_11 That's strange, I didn't do anything - haha! :) Great to hear
that looks more like 'having them soldered by someone else' at 1:35 😉
My wife likes to hang around with my in my workshop, haha! :) Sometimes without her making all this stuff would be much harder.