Feature Request

I noticed that yesterday before pushing and fixed it. It works fine here, with your code as well. Strange happenings...

Is there anything about my table that could be different or cause different behavior? Definitely acting odd. It losing the soft limit on a rapid has me nervous lol

Not sure it would help but do you need my hal/ini fileS? Could Rod’s ohmic2 comp be interfering somehow?

snowgoer540 wrote:

I noticed that yesterday before pushing and fixed it. It works fine here, with your code as well. Strange happenings...

Is there anything about my table that could be different or cause different behavior? Definitely acting odd. It losing the soft limit on a rapid has me nervous lol

It is possible that the errors caused the Y&Y offsets to not zero out and I don't think the soft limits keep track of the offsets (not 100% sure)
It may be worthwhile to keep Halshow open while doing this testing and keep an eye on the X&Y offsets and it they aren't zero (or as close as a float can show zero) when you stop a job then you need to restart LinuxCNC. Attached is my.halshow that I am using while testing. Copy it to your config directory and have the following in the .ini file and it will load when you start LinuxCNC. You can delete anything you don't want to watch. Remove the .txt from the end - I can't belive this forum doesn't allow halshow files...

Not sure it would help but do you need my hal/ini fileS? Could Rod’s ohmic2 comp be interfering somehow?

I don't believe so.

phillc54 wrote:

snowgoer540 wrote:

I noticed that yesterday before pushing and fixed it. It works fine here, with your code as well. Strange happenings...

Is there anything about my table that could be different or cause different behavior? Definitely acting odd. It losing the soft limit on a rapid has me nervous lol

It is possible that the errors caused the Y&Y offsets to not zero out and I don't think the soft limits keep track of the offsets (not 100% sure)
It may be worthwhile to keep Halshow open while doing this testing and keep an eye on the X&Y offsets and it they aren't zero (or as close as a float can show zero) when you stop a job then you need to restart LinuxCNC. Attached is my.halshow that I am using while testing. Copy it to your config directory and have the following in the .ini file and it will load when you start LinuxCNC. You can delete anything you don't want to watch. Remove the .txt from the end - I can't belive this forum doesn't allow halshow files...

Code:

[APPLICATIONS] DELAY = 3 APP = halshow my.halshow

Not sure it would help but do you need my hal/ini fileS? Could Rod’s ohmic2 comp be interfering somehow?

I don't believe so.

Ok, I’ll add that and keep an eye on things.

Anything else I can be doing in the meantime? Any more info I can feed you that might help?

snowgoer540 wrote: Anything else I can be doing in the meantime? Any more info I can feed you that might help?

No, I think you are keeping me occupied.

phillc54 wrote:

snowgoer540 wrote: Anything else I can be doing in the meantime? Any more info I can feed you that might help?

No, I think you are keeping me occupied.

Haha well if I ever get around to designing a reduction system, you may get a bit of a reprieve while I implement it

Well I am glad you posted the code you are using because it shows odd behaviour that the code I used doesn't.

I have no idea what is going on with that, very strange, so bear with me...

Haha well if I ever get around to designing a reduction system, you may get a bit of a reprieve while I implement it

I may copy it.

phillc54 wrote: Well I am glad you posted the code you are using because it shows odd behaviour that the code I used doesn't.

I have no idea what is going on with that, very strange, so bear with me...

Haha well if I ever get around to designing a reduction system, you may get a bit of a reprieve while I implement it

I may copy it.

Interesting. I wonder what’s special about it. I have gotten a lot of mileage out of testing with it though, so I’ll thank the guy I did the cut for he will get a kick out of it :laugh:

I wish I knew about the resonance stuff and distance per resolution before I designed the table. I always planned to use linuxcnc, but it wasn’t until I was mostly done with the build that I learned of Plasmac, and even later (table built) that I learned of the Plasma primer. So I now see for myself why everyone uses a reduction system. The ironic thing is I always thought it was about torque and couldn’t understand why there wasn’t enough. Live and learn. Lessons taught by experience are supposed to stick the longest I guess? At any rate I say all of that to say that it’ll be a challenge to work it into the area I have now, without a complete resign... but necessity is the mother of all invention... I hope

At any rate I say all of that to say that it’ll be a challenge to work it into the area I have now, without a complete resign...

That is what is putting me off doing it...

The next lot of mistakes have been pushed.:blink:

phillc54 wrote: That is what is putting me off doing it...

Same...

The next lot of mistakes have been pushed.:blink:

Ok, excited to get out of here today and test it out. Did you find anything profound? Any area of the aforementioned issues I should focus my efforts around?

Also, are the errors cut-recovery related? Or would they have affected the main branch and the mesh branch as well?