Errors caused by Latency or something else?

15 Oct 2018 14:01 #118833 by simonmn
oh woops, didn't realize the difference, til I saw the 27.1 from the previous.
I found the gears animation thing, and just opened 8 of them to stress, could that have caused it? I didn't run the animation on the first one, I just opened a bunch of programs, and began creating big pictures in gimp.
Im I just messing up information? :(
16 Oct 2018 08:06 #118868 by simonmn
Ran histogram again this morning, and this time I get min(us): -34.5 and max(us):35.5
I have to ask, how does these correspond to the normal latency test numbers?

is 35 us equol to 35000 ns?

also, what do you guys do under the latency test? just use a couple of programs, or a lot?

I feel like i'm at a dead end. That the next step is to try a different computer, or another nc solution entirely.
16 Oct 2018 08:35 #118870 by andypugh
35uS = 35000nS = 0.035mS

What network adaptor do you have? Did you see the comment from PCW
"Also what host PC hardware are you running? If you have a Intel or Qualcom MAC you must make some driver setting adjustments with the ethtool utility"

Other options are, as you have suggested: A different motherboard (there are relatively cheap ones that are known to work fine) or switching to PCI hardware or a different controller.
Of those, the cheapest is likely to be a different motherboard. (as no other controllers are compatible with your hardware)
The following user(s) said Thank You: simonmn
16 Oct 2018 11:21 #118874 by simonmn
I have now found another computer(workshop pc) with an ssd too
Installed a fresh debian stretch preemt uspace install.
Made a fresh pncconfig config only setting it to lathe and metric, plus x and z stepgen.
I even grabbed a new Ethernet cable (since the old one wasn't long enough)
Set host ip to and card ip to

And I get the same two errors...:blink:
Even though this is progress, I want to smash my head into something!

So I guess its my Mesa card, my card setup, or maybe an incorrect way of connecting to the card?

As for PCW's question
Sorry, I read it, but didn't get the focus on Ethernet. thought it was more general hardware spec.
I snatched a lshw, hoping it will show more information about the Ethernet type and info. (This from the new, currently connected computer)

Hope you can use this information. I really appreciate you guys helping me!
16 Oct 2018 12:24 #118875 by andypugh
Looks like Realtek

description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0

Is there any chance that the problem is W8 being in the "setup" position?
16 Oct 2018 12:36 #118876 by simonmn
It should be in operate mode, left position (with Ethernet port in top left)
16 Oct 2018 14:51 #118881 by PCW
Can you post your hal and ini files?
16 Oct 2018 15:04 - 16 Oct 2018 15:06 #118882 by simonmn
Here you go

(edit) I realise the ip is, but I have edited it to everytime I used the config. this is a backup
Last edit: 16 Oct 2018 15:06 by simonmn.
16 Oct 2018 15:11 #118883 by PCW
SERVO_PERIOD = 1000000
in your ini file

This should work a lot better...
The following user(s) said Thank You: simonmn
16 Oct 2018 15:38 #118887 by simonmn
Man... that kick you get when motors buzz and growl because of bad settings - when you weren't expecting anything to happend.

That did the trick! I am so happy and relieved right now! Thank you guys for the help!

I thought I was supposed to enter the latency test value in there? Pncconf did say recommended servo period : 1000000. But i thought it was the base value for some reason. Maybe because my values where that stupid high to begin with.

Thank you guys again! I can finally continue with the project again!
Moderators: cmorley
Time to create page: 0.090 seconds
Powered by Kunena Forum