Advanced Search

Hey, I have a weird issue. Not sure where it comes from or what the cause is, but I don’t know what to look for anymore.My machine is off position at the end of the program. For troubleshooting: I put a work piece in my machine and went to X10 Y20 and made manually a mark on the workpiece.Then I run a program and at the end I go back to X10 and Y20, but the machine is off in X and Y for a few millimeter. This is happening again and again and it is always the same distance off. First I thought it had something to do with speed and acceleration. I tried lowering it. Same error. I let the machine then run in a higher Z position without any load. In the air so to say. Same error!Then I tried another NC program, same thing here. At the end it’s repeatable a little bit off.I lowered the acceleration (75mm/s2) and feed speed to 1/10 (600mm/min) of its original value. Same error!I had deadband at 0.01 and lowered it to 0.007. Same error.I tried changing the Ferror from 2.0 to 1.0. Same error.I tried different programs and it feels like the offset is larger if the travel within the program is larger.I checked the mechanics and I am sure it’s not a mechanical error.I don’t know what else to test.

The machine is an open loop stepper system with DM322T Driver and Nema 23 motors.

Thanks, how to turn it off?   Forgive me for being a newbie.

Nice find, and it does have a parallel port header and an M.2 slot.
But at 146 Euro here, i am skipping it for now, might go back to it later as it uses a single power supply, probably 12V adapter, and not the full ATX power supply.

What GUI? Assuming you are not using Axis as it is by default in Auto mode.
Does the machine use a tool changer?
Does it use any custom components?
Does it have any added hal wizardry?
-
I recall a while back in certain states/conditions it would run through all the tools in the gcode, but it was probably fixed since for a long time it was not mentioned here.

Probably would need also changing the - sign for home_search_velocity and maybe home_latch_velocity for that axis/joint.

Helpful? I'm fairly certain you believe that too.
If there's confusion about something, then ask a question. No questions were asked. It's really easy too. "What do you mean by MEM? I'm not familiar with that term." I would have been happy to answer to clear up any confusion and learn whatever you folks call it.

What did I get in return? Some self-conceited person you consider an "esteemed colleague" that thought that I was too dumb to not know what operating system I was using...
Bad news, I match energy. If you don't like what you put out thrown back at you? Then don't be that way.

And here you are tossing out childish insults...

I'll figure it out myself.

Oh this old gem, the solution is to remove or purge the offending raspberry pi package. Its been mentioned many many times throughout the forum, the exact commands can be found with a quick search.

But the the theories above do not take into account it is fine afterwards, very intriguing.

It's quite possible it is a gcode issue, mayhaps the cam is in metric units and the machine is setup in imperial units and no g21 was given in the preamble.

Another possibility is whoever setup the machine gave the overrides quite a large postivie range and the feed override is set at max.

And just for clarity Linuxcnc loads the gcode from the filesystem, ie from disk, not from "Internal memory", for those that are familiar with computers there is a distinction between memory (being ram/rom) and disk. As many things getting terms incorrect can cause confusion.
Look for all we know you could be using a custom interface with a MEM button implemented to make the machine more familiar. If that is the case it would be no wonder there has been confusion. Reading through the documentation for the various interfaces supplied with Linuxcnc there is no mention of a MEM button. I mention this as the frustration of the OP seems to be the questioning of a MEM button being implemented in Linuxcnc to retrieve gcode from "internal memory".

I have just realised that my thingy requires you to type in the values. That's not as ergonomic as one might hope. Give me a few minutes.
Files updated
 

@scotta Following chatgpt it could work by only do ARR/CCR-updates via DMA-burst and the rest with timers. Does that make sense?

This captured my interest, so I made one.
Drop the two attached files into the same folder as your INI file.
Then, in the [DISPLAY] section of the INI file add:Be careful with the buttons, they are not tested on real hardware.Set Zero - should set the coordinate system zero to be the centre of the probed circle (considers G54 etc but not G92 at the moment)GotoZero does a Z-hop of (currently) 20mm then G0 X0 Y0.The diameter measured has 6mm subtracted from it to allow for probe diameter.The Z-hop and probe diameter are constants defined near the top of the python file. Feel free to edit to suit.This uses GladeVCP. As has been suggested elsewhere, there are other VCP frameworks, but Glade works well enough with Axis.

So I've been trying to get this to work and I keep getting some error with dpkg.

I'm running a clean install from the latest iso from linuxcnc.org. Upgrading to trixie according to the instructions by rodw. My hardware is a NUC 14 with an Intel N150 processor.


What's this raspi-firmware doing here? Is this causing my issue or can it be ignored? It's quite late here, so I'm done for today. I hope someone can point me in the right direction.

Just read your post prior to mine.

Your still to provide the information I ask for to diagnose your situation.

See sometimes as issue can arise that none have seen before, there was a recent one regarding MDI pins. Until one user had used a particular setup it had never occurred. Fortunately the user supplied the information particular to their usage and the code was quickly fixed and merged into the code base.
If that user had of reacted as you did nothing would have been resolved.
Now old Tommy has a great deal of experience deploying Linuxcnc based equipment as a commercial endeavour, so he is no Johnny come lately. PCW is the Mesa presence on the forum, very helpful, very knowledgeable and quick to respond to users requests for custom firmware. Very respected, will even endeavour to help when the mesa firmware is being deployed on non Mesa Spartan 6 platforms. Also has been generous enough to supply schematics to his products when asked.
So I would my two esteemed colleagues conduct themselves in a manner that has earned them the utmost of respect.
So I think it would be a good time for you the reassess your comments, look through the forum and read the replies they have given other users. Then it would be an idea to offer an apology cool down and supply the information requested so this issue can be resolved .

So what version of Linuxcnc are you using, what is the underlying OS, are you able to attach the config files ? Also what hardware is being used to control the machine, is it parallel port based, Mesa based or some other hardware based step direction system ?
Diagnosis requires the collection of information and that is the reason for request.

I thought I was being quite helpful, like my esteemed colleagues I was confused about MEM.
Playing the victim, the use of the phrase "folks", the mini lecture on the use of the word again, whilst missing the comma you used to add emphasis as noted in the mini lecture and finally quoting google as to drive home the point that those that queried the whole MEM thing were plebs makes me wonder if the OP has had any oil, dirt or grease ever touch their hands.

But then again I'm a paranoid bastard that trusts no one.