Advanced Search

I checked the userkins.comp file, found nothing strange, but in userkins.c, it was

int kinematicsForward ...
   ...
    pos->tran.x = j[0]/80; // X coordinate
    pos->tran.y = j[1]/80; // Y coordinate
    pos->tran.z = j[2]/80; // Z coordinate

while in userkins.comp or either of the kinematicsInverse functions, the /80 was not there. I tried compiling again, nothing changed. I tried deleting the /80 from userkins.c, everything is now working. I just have no idea why..

We moved to Ingleburn, not far from Campbelltown, in the very late 70's. At the time they were building a lot of housing commission places, the joys of coming from a "broken home", anyways all the building was causing the snakes to look for new places. Usually the first sign you got was the 2 dauschhunds going off their heads, and sure enough there was some snake or another making themselves at home.
Funnily enough the worst incident we had wasn't a snake bite but 2 of the neighbours' boys decided to sniff glue and start taking shots at each other with slug guns.
"But dad I only shot him in his glue"

On there was also the mattress fire under the house due to one of the neighbours and his girlfriend smoking and having a pash session.

And no I was only 6 or 7 at the time, we were just general menaces, favourite was running through the pond outside the doctors surgery. 40 years later I was working at the railway station when they were doing upgrades at Ingleburn, and yep the doctors surgery and pond were still there. I thought about it, but too many aches and pains to run through it, plus it was pretty cold that day.

Hi Hakan,

At the moment it's here.
But i can not help you with questions at the moment as i have not reviewed the code for a while now.
The ethercat-master is also there. It has different source code to store the xml in memory.
However i think it will run.

I just conversed the cia402.comp to c code .
I really don't get the dev's why they stay using .comp code, and even worse:  promoting it to use.

do you mean for a spindle? haven't looked at it yet.
i would be surprised if servos have velocity control... or do they?

I see you have a userkins module, that one becomes suspicious of course.

I agree, this is most likely a problem with your custom kinematic module. I usually see these kinds of jumps when the forward and the inverse kinematics do not match up.

langdons wrote:

Python does not even have switch statements!
 

It does now since 3.10 
www.reddit.com/r/pythontips/comments/122...s_switch_statements/

Personally I much prefer python over php and Java but C I am much more comfortable with.
It just annoys me that Python can do things in 100 lines that would take 1000 in C

Suddenly a big shift in axis.x.pos-cmd while joint.0.pos.cmd stays? When you shift between MDI and Manual.
The translation between joints and axis is done in the kinematics module but there are more things involved I don't know so much about.
I see you have a userkins module, that one becomes suspicious of course.

You can follow the signals, ms by ms, using the halscope utility.
Maybe interesting to do that when you shift between MDI and manual.

Judging from the halshow output you EtherCAT drives behave as they should. The problem isn't there.
 

Careful now, I grew up 500 miles from the coast and 90 miles from the nearest town! The brown mulga snake I grew up with is supposedly the third most deadly in the world. I tripped over a log once to find one sunning himself under my chest when I landed. We both got a fright, I froze and he took off. Another time, I met one in the house coiled up 2 feet in the air ready to strike at me. Maybe I was about 10. Took me a couple of weeks before I got him with the .22 under Mum's dressing table!

Yet I only ever knew two people who got bitten, both on the foot while riding a horse. One was my grandfather and they had to hit the snake with a stick to make him let go and the other was a young girl about 12, the daughter of a drover. Both lived through the event! I don't think much venom got past the kangaroo skin upper on their RM Williams riding boots!

Its quite tricky building a custom kernel for preempt_rt. What we have done here is look at the kernel version the RT patch was released on at kernel.org, then we have to find the actual commit in the Rpi kernel git that matches the same release. If the kernel version deviates from the RT patch, the kernel will fail. So we end up with a kernel in between released versions of Debian. We also need to be ahead of the released kernels to maximize support for the Pi 5 which was released just after Linuxcnc 2.9.1 was released. Rpi are also making it hard for us since the Pi 5 because they are no longer tracking each version of the Linux kernel so sometimes, we can't upgrade to a later RT patch.

So you have to wait for Linuxcnc to release new images for a  reason. Don't try and upgrade yourself without forking thr Linuxcnc builder and compiling from source

I have no idea how Ubuntu got in the conversation, these images are based on Debian with the Rpi kernel.

The kernel version used is ahead of the standard Debian versions so things break on a dist-upgrade.

is there a way to download previously uploaded nvem-rt1052.txt from NVEM?
 

Nice!

I have a MH500w2 i'm working on! I looked through your files and tried messing around abit. But i'm afraid i can't figure out how to add what appears to be different. you have some layer of "home-x" parameters which i seem to skip in my ini (made with Mesa CT). i'll add my files if you have the time for a quick look.

I'm running LCNC 2.10 with Gmoccapy.

I just tried that, not sure if I found something useful but something strange did come up.
The pins I looked at were:
joint.0.pos-cmd
joint.0.pos-fb
cia402.0.drv-actual-position
cia402.0.drv-target-position
joint.0.motor-pos-cmd
joint.0.motor-pos-fb
cia402.0.pos-cmd
cia402.0.pos-fb
axis.x.pos-cmd
cec.0.8Axis.xactual-position
lcec.0.8Axis.xtarget-position

all seem like they're what they should be except axis.x.pos-cmd, after I sent G0 X50 in MDI mode, it was 50, everything was fine, then I switched to manual control mode, it changed to 0.625. That is also when I get the motor position error.

I took some screenshots at startup, after homing, after sending a G0X50 command and after I got the error. I don't have anywhere to host the images though, so I put them in the attachment in case that helps.


 

Did you try with halshow? That is the way to debug this.
When linuxcnc is still running, start halshow in a terminal window. The machine can have e-stopped, that's ok.
Just type halshow at the prompt.
Navigate through pins and investigate the values of the pins outlined above.
This should hopefully give an understanding of where things go wrong.

I can't jog or do anything after running a program, I get motor position error on xyz axes afterwards and have to restart linuxcnc before I can reconnect to the machine. Same thing if I run a few lines in MDI mode and switch back to manual control.

Yes the x, y and z axes are driven by leadscrews.

Yes they are stepper motors.

I did double check the unit last week, we have everything set in mm. I wish it was as simple as that.