Advanced Search

I checked the index signal with a physical oscilloscope (Hameg 303 in this case) and I can see the index signal "fly by"... it is very fast

 

Thank you Andy, I will follow your advice to try to observe both, index-enable signal and hm2_7i80.0.encoder.00.input-index pin in the HAL scope and see if the index-enable pin behaves as you describe it.

Thank you
Sigi


 

Wiring is the same as the SKR2. RPi4 or 5?

I think I'm ready! Hopefully ordering the parts in the next 2 weeks. EEK!

 

 

Here is red box machine we are modifying into a control center. A keyboard and mouse pad will be secured to the shelf using velcro. Should make for a good cabinet plenty of space and resistant to impact. 

Yes. I have cloned latest remora-h7xx-pio repository from remora-cnc. And compiled that. And used config files attached in previous post.

Ok thank you that is a bit more more informative, if somewhat weird. As I suspected the whole MEM debacle is someone's labeling, maybe to make the machine more familiar.

Somewhere along the way some one is going to ask for the gcode file, and once again the config files and the rest relating to your machine so they may have a chance of the simulating the issue.

If there is any proprietary IP involved you may have to make an agreement with one of the devs to sort this issue out. I'm just putting this out there as your particular site situation is unknown.

Just a word of warning, if the issue relates to some sort of issue with any Mesa hardware you'll be dealing with the company run by the person you referred to as conceited. But what you need to consider is that over the years there has been dealings with people that have landed at this forum requesting cnc help not related to the Linuxcnc ecosystem, also those that will argue that Linuxcnc should support this hardware or that, usually related to some form of USB based controller that for various reason does not work within realtime, I know unrelated to your issue.

Now time to let bygones be bygones and other such cliches and sort this out. I can understand if this is causing some frustration but sometimes it can go both ways. Like multiple requests for a user to give information regarding their system, ask your sales or engineering team how this can be with some customers. But like I said if there is any proprietary IP involved some agreement with one of the devs maybe the way to go, so as any discussion can take place within a non-public way.

Have you checked for backlash with a Dial Indicator, as opposed to a dial test indicator which can be difficult to setup to negate any cosine error. T me this sounds like a backlash/leadscrew related issue.
Many times an similar issue has come up similar to this, even tho the user had checked the mechanical side, it turns out upon closer inspection it is indeed a mechanical issue. Coil type couplers aren't worth much as they can wind up. Don't rely on the stepper motor to provide any fixed bearing support (as many 3d printers and cheap chinese mills do), use angular contact bearings, the non driven end of a leadscrew should be able to "float" laterally to allow for thermal expansion.
Even ballscrews have backlash, unless you are paying alot and I mean alot for ballsrews expect some backlash.
Missing steps could also be a cause. But if I were a betting man I would put a wager on a mechanical issue. The thing regarding mechanical issues is they can add up, a little here and little there and another bit there can end up as a nightmare.

Here's a document far more eloquent than I could describe.
rick.sparber.org/mt.pdf

Once again can you please offer up the version of Linuxcnc,the underlying OS and whether you are using a parallel port based system with software step generation or you are using a hardware based solution, once again any config files will be helpful.

Call me what you want I really don't mind, as you don't know me personally it hasn't affect .

In my dealings with PCW I have found him to be very generous with his time, knowledge and the schematics related to his products. Like I said read the forums and pay attention to the advice, help and response to custom FPGA bitfiles for his line of Mesa products, you will find everything I said to be truthful representation of the facts.
If you require help we're here to help, if you want to argue I gladly indulge that as well. If you bear false witness regarding members of this forum I will refute any statements that do not truthfully represent their character.

In saying all that I feel this thread would be better off deleted as it is proving to be a tit for tat affair.

Mayhaps then you could start a new thread and we can forget about the whole MEM thing which isn't a "Linuxcnc concept" as per the standard codebase. If this was a feature the various GUI would have that button, Hal pins would be exposed for that feature and it would be documented.
The closet feature would be the "reload button" but that rereads the file from the filesystem, but will also use the the original filename with any changes that may have been made. Which when combined from the "run from here" feature is a useful way to add extra code to a file without having a complete rerun.

Once again, the I formation requested regarding your system will be most helpful.

I would like to request if this information isn't supplied that either the thread is locked or deleted.

youtube.com/

Is this a parallel port driven machine?
If yes, raise the BASE_PERIOD in the ini file to at least twice what you have now and test again.
Also, lengthening the step time and step space might help a lot.

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.