Advanced Search

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).

Hello everyone!

I am very inexperienced in this field and I am attempting to develop a project. The basic premise is that I want to deposit material from a cnc machine fitted with an extruder on its end effector onto a free standing object. As the object is free standing, it may occasionally inadvertently move causing the predetermined toolpath (original g-code) to deposit material in the incorrect position. As a remedy, I am working to add cameras which can track the object being operated on and any movement will be tracked and it will automatically adjust the toolpath so that it does correctly print regardless of toolpath. I currently use mach4 to operate the machine and as such, I am struggling to determine how I can in real time, adjust the inputted g-code. I came across linuxcnc and QtPyVCP which from my own understanding, enables custom applications. Can anyone give me a sense of direction as to whether something like this can be implemented on this application? Thanks!

What does
uname -a
in a terminal return?

Reboot
hold down the SHIFT key till you see the GRUB menu, choose the line with RTAI in the name and press enter
run LinuxCNC

Not sure but as far as I understand this issue, things might be a lot easier switching to a PC with an intel network chip.

Hi Arciera,

That is the result of using a 0.1 fillet.
Here is a 0.01 fillet for comparishment.

 

i have been fighting with this issue for over six months. it doesn't matter what i do, this issue keeps coming back. PCW advised me to contact Mesa, and i did, but they want to charge shipping fees and other fees to look at this board and it may not even need anything done to it by them. i think i would just be throwing more money away and i would like to exhaust ALL my options before i send it back to them. not to mention the snarky attitude you get after a week of the run around. so i will conserve sending it back as a last, last resort. the attitude they have about issues with these boards are its all your fault and there is no way the board can be faulty. so i'm turning to the good people on this site to see if we can come up with a solution before i send it back to Mesa. 

as stated in the description, im getting the error hm2/hm2_7i96s.0: watchdog has bit! (set the .has-bit pin to false to resume)
also, Unexpected realtime delay on task ) with period 1000000. i am also getting an error hm2/hm2_7i96s.0: stepgen.04. maxvel is too big for current step timings & position-scale. clipping to max possible.

now i know the last error is not an issue at the moment, but the watchdog error (error plus red light on, on the 7i96s) i followed the instuctions on this link docs.google.com/document/d/1jeV_4VKzVmOI...m1x7oiw8VcLFdiY/edit. when i install the dkms drivers for the realtek ethernet adapter, i lose my network. as it is right now, i have a fresh install of Debian trixie and i installed linuxcnc and configured the network. Axis starts up and i can home but after a few minutes, i get the watchdog error (red light on, on the mesa 7i96s along with error in description).

what else ive done is outlined in the following links. forum.linuxcnc.org/9-installing-linuxcnc...-connection-problems. and forum.linuxcnc.org/38-general-linuxcnc-q...oint-following-error. i have also tried a couple different power supplies to make sure the board is getting enough power.
can't we flash firmware on this board? i really don't know what i am doing when it comes to flashing these boards. (as i have never done it before) and i don't want to brick the board, but i think with your guys help, i can straighten this out. without sending it back to mesa. i really think its a firmware issue since i am unable to read the firmware through terminal or in mesaflash, the firmware section is greyed out.
any help is greatly appreciated.

ok, I got this screen, I didn't do any more procedures here. What to do now? restart linux or is there any other procedure?