Advanced Search

I hadn't opened it yet but I got this message on the screen

I would skip that for now, make the machine move first, later when you are happy that it works, you can punish yourself with some fine tuning!
Set the base period to 100000 at first (write 60000 in the jitter value in StepConf wizard), see if you get latency warnings when running LinuxCNC, and if you do not, then you can lower that value in 10000 increments.

JamesHoward wrote:

I know Chats algo's arent perfect.. Its like a highschooler still.

 

I guess it's more like a hallucinating 8 year old who read too many twitter and youtube comments and thinks he knows everything about the world. And of course, don't listen to the people who wrote these algorithms, because they do anything in their power to pump up the hype.

And sure, these bots can be valuable in some niche area's such as sorting through huge amounts of data which would be impossible for humans, but for many things they're not better than mostly random guesses at the moment.

Lpkkk wrote:

Update :

I believe my stlink stopped working fine. I've used nanoDaplink and there was still no answer from the nvem. Finally I've pushed (and keep it pressed) reset button on nvem, then start flashing with pyocd. When I started pyocd I've released reset button and whole process went fine from there. It was flashed with remora 3.1.3. Later I've connected ethernet and tried to ping. One of the leds on nvem went off and my ping was succefull. Then I've used this config :

github.com/scottalford75/Remora-RT1052-c...NC%2Fnvem-rt1052.txt

And it was all good. Previously I've used by mistake basic and full config from here :

github.com/scottalford75/Remora-NVEM/blo...vem-basic-config.txt

Which I believe was not for RT1052 version of nvem board. DON'T USE THIS CONFIG. 


Quick install eth component and everything works perfectly. I can move 3 connected axis with this linuxcnc config :

github.com/scottalford75/Remora-RT1052-c...Fremora-rt1052-basic

But this Linux cnc config is only for 3 axes. Do I have to manually set my 4th axis? 

Next step will be adding limit switches, one for each axis (except 4th). Maybe this evening I will find some time. 


 

Yes, you will need to configure both the INI and HAL files so LinuxCNC can use the additional axis. The NVEM config file you have used as all 6 axes configured. For the LinuxCNC configuration, I'd suggest posting questions in:

forum.linuxcnc.org/49-basic-configuration
forum.linuxcnc.org/10-advanced-configuration

jitter stabilized at 32000, if I adopt these values ​​and my driver's resolution is 800, what reliable speed can I explore with the machine?

Often you can simply put some (schottky) diodes in series in the step and direction signals in between both "step generators" and the stepper motor drivers, but it depends on the actual hardware you have.

Another option that can work is to put some 74HC series logic in between and use that to switch signals. For example with a 74HC541 you can switch 8 digital signals on/off via the "G" inputs. You can then use a simple double throw switch to switch the "G" inputs of the TTL IC's.

In a more elaborate setup, you can control the "G" inputs with some microcontroller and you can make it as complex as you want or need.

A boomerang test file :
 

fillets 0.01mm
 

fillets 0.1mm
 

green is an arc, its a cut off for the boomerang tip shape.
purple is clothoid fillets.
cyan is spline fillets.
white is line.

vel profiles G64 P0
 

vel profiles G64 P0.01
 

vel profiles G64 P0.1
 

sorry double

The product is about 4mm width on x axis and less then 3mm on y axis.

Oh my, that is really tiny. Well, that puts my mind to rest and I can go to sleep now.
Thanks for putting up with my constant niggling.

thanks!
everything is working again, even on Raspy Pi5

thanks to everyone

Hi Arciera,

The product is about 4mm width on x axis and less then 3mm on y axis. So very tiny product dimensions.
I can not run on realtime kernel now, otherwise i could jog to measure the grid size.

Thank you very much,
this avatar encouraged me
if I took a while to understand he would get even angrier lol
and you Tommy Light managed to do it, be patient too because I don't know anything about Linux.
but there you go, I'll see now what can be improved more with these jitters

May be the 'external offsets' feature could be of interest. This will let you superimpose offsets to any axis through hal pins (ie outside of GCode) while the program is executed. LinuxCNC plasma applications use this to regulate the torch height on the sheet metal.
For a short demonstration:

Hi mate,
You have to hold Reset button before starting pyocd command, when pressed start pyocd flash command and quickly release board reset button.
That works 100% for my nvem.
If you dont have reset button on your board try manual reset by looking on your board pinouts.

I understand that lowering the value will create smaller deviations. What I'm concerned about is the predictability of the maximum deviation a certain G64 Pn Qn command is going to produce as knowing this is crucial for CNC application.
I know we've had this discussion before but if 'G64 P0.1 Q0.1' means a maximum path deviation of 0.1 mm then those white GCode lines would have to be 0.1mm apart which seems a bit hard to believe (but of course I do not know for sure).