- Posts: 29
- Thank you received: 0
Early Omniturn gang lathe to Linuxcnc?
- gearheaded
- Topic Author
- Offline
- Junior Member
-
Less
More
7 years 1 week ago #148371
by gearheaded
Replied by gearheaded on topic Early Omniturn gang lathe to Linuxcnc?
Hello:
I ran the latency-histogram --nobase while watching youtube vids, 5glx of various sizes, and used gimp to edit some photos. Here is a screenshot of the graph. Seems ok to me based on what I've been reading,
I did notice that videos played at varying speed as well as the gears not moving consistently, but nothing ever froze up.
Thanks for any additional insights
Karl
I ran the latency-histogram --nobase while watching youtube vids, 5glx of various sizes, and used gimp to edit some photos. Here is a screenshot of the graph. Seems ok to me based on what I've been reading,
I did notice that videos played at varying speed as well as the gears not moving consistently, but nothing ever froze up.
Thanks for any additional insights
Karl
Please Log in to join the conversation.
7 years 1 week ago #148378
by OT-CNC
Sorry about that. It's been a while since I configured my mpg.
Replied by OT-CNC on topic Early Omniturn gang lathe to Linuxcnc?
The MPG encoder pins that support 1x mode are not selected this way.
They require mode 3 and change a few GPIO pins to lower speed MPG encoder pins
Sorry about that. It's been a while since I configured my mpg.
Please Log in to join the conversation.
7 years 1 week ago #148382
by PCW
Replied by PCW on topic Early Omniturn gang lathe to Linuxcnc?
The latency looks OK (though I would probably turn off IsolCPUs as that will slow a already slow system down quite a bit)
Do you still get the SSerial port errors with a 1000000 ns servo thread?
If so, can you run LinuxCNC for a while and then run this command in a terminal:
halcmd show all *tmax*
and post the results here
Do you still get the SSerial port errors with a 1000000 ns servo thread?
If so, can you run LinuxCNC for a while and then run this command in a terminal:
halcmd show all *tmax*
and post the results here
Please Log in to join the conversation.
- gearheaded
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 29
- Thank you received: 0
7 years 1 week ago #148503
by gearheaded
Replied by gearheaded on topic Early Omniturn gang lathe to Linuxcnc?
Hello again:
I rebooted and removed the isolcpus=1, within seconds the latency shoots +/- 100us. With multiple glxgears and you tube running, it only takes 5-10 minutes to get huge jumps until finally reaching the levels in this screen shot.
This leads to a unexpected realtime delay. I tried setting the base period to 2ms, but no change.
I went back to isolcpus=1 and the latency histogram went back to +/-20us. Tried the suggested halcmd and the first time it showed a lot of data, I didn't take a screen shot at the time figuring I would get one later. Ever since, even after multiple reboots, all I get is this screen:
Should I just buy another mother board, I thought I was following the best advice I could find. I'm not worried about a few hundred bucks in the big picture, it's chasing my tail to the tune of 40 hours research and still can't get the software to even run, then alone start using it. Time is the expensive thing to me.
Any advice would be appreciated...just want to wire up the lathe, and learn to use it with Linuxcnc.
Thanks
Karl
I rebooted and removed the isolcpus=1, within seconds the latency shoots +/- 100us. With multiple glxgears and you tube running, it only takes 5-10 minutes to get huge jumps until finally reaching the levels in this screen shot.
This leads to a unexpected realtime delay. I tried setting the base period to 2ms, but no change.
I went back to isolcpus=1 and the latency histogram went back to +/-20us. Tried the suggested halcmd and the first time it showed a lot of data, I didn't take a screen shot at the time figuring I would get one later. Ever since, even after multiple reboots, all I get is this screen:
Should I just buy another mother board, I thought I was following the best advice I could find. I'm not worried about a few hundred bucks in the big picture, it's chasing my tail to the tune of 40 hours research and still can't get the software to even run, then alone start using it. Time is the expensive thing to me.
Any advice would be appreciated...just want to wire up the lathe, and learn to use it with Linuxcnc.
Thanks
Karl
Please Log in to join the conversation.
7 years 1 week ago #148506
by PCW
Replied by PCW on topic Early Omniturn gang lathe to Linuxcnc?
Looks like something is not setup right on your motherboard
Do you have all speed switching and cstates > C1 disabled in the BIOS setup?
I get this with the Stretch ISO on a ASRock J3355B, no isolCPUs
(youtube video running and 10 glxgears)
Do you have all speed switching and cstates > C1 disabled in the BIOS setup?
I get this with the Stretch ISO on a ASRock J3355B, no isolCPUs
(youtube video running and 10 glxgears)
Attachment not found
Please Log in to join the conversation.
7 years 1 week ago #148510
by PCW
Replied by PCW on topic Early Omniturn gang lathe to Linuxcnc?
BTW the way to get the tmax values is
halcmd show all *tmax*
(those are not quotes but asterisks)
halcmd show all *tmax*
(those are not quotes but asterisks)
Please Log in to join the conversation.
- gearheaded
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 29
- Thank you received: 0
7 years 1 week ago #148511
by gearheaded
Replied by gearheaded on topic Early Omniturn gang lathe to Linuxcnc?
As far as I know, I've disabled everything I could. In my bios, I disabled C-states entirely, however, it seems to me I remember reading about turning it off with boot parameters as well.
I tried setting c-state to c1 and disabling c1e, but latency was still way up there. Is there any other boot parameters I need to be using?
Here is the BIOS settings I've been using:
BIOS settings:
CPU page
Both fans set to full speed
Intel Speedstep = disabled
CPU C states = disabled
Intel virtualization technology = disabled
VT-d = disabled
Power Gear = sport mode
Chipset Config:
Memory set to 1.5V 4GB Patriot 1333
Onboard graphics
Shared memory 512M
Audio disabled
LAN enabled
PCIe1 link speed auto
Deep S5 disabled
Super I/O config:
Serial ports disabled
Para port disabled
ACPI config:
Everything disabled except for- ACPI HNET Table is enabled
Thanks
Karl
I tried setting c-state to c1 and disabling c1e, but latency was still way up there. Is there any other boot parameters I need to be using?
Here is the BIOS settings I've been using:
BIOS settings:
CPU page
Both fans set to full speed
Intel Speedstep = disabled
CPU C states = disabled
Intel virtualization technology = disabled
VT-d = disabled
Power Gear = sport mode
Chipset Config:
Memory set to 1.5V 4GB Patriot 1333
Onboard graphics
Shared memory 512M
Audio disabled
LAN enabled
PCIe1 link speed auto
Deep S5 disabled
Super I/O config:
Serial ports disabled
Para port disabled
ACPI config:
Everything disabled except for- ACPI HNET Table is enabled
Thanks
Karl
Please Log in to join the conversation.
7 years 1 week ago #148512
by PCW
Replied by PCW on topic Early Omniturn gang lathe to Linuxcnc?
I think I have only cstates speed-step and virtualization disabled
Can you replot the no-isolcpus setup with a wider scale so its possible to
see if the long times are outliers:
latency-histogram --nobase --sbinsize 1000
Can you replot the no-isolcpus setup with a wider scale so its possible to
see if the long times are outliers:
latency-histogram --nobase --sbinsize 1000
Please Log in to join the conversation.
- gearheaded
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 29
- Thank you received: 0
7 years 1 week ago #148517
by gearheaded
Replied by gearheaded on topic Early Omniturn gang lathe to Linuxcnc?
Please Log in to join the conversation.
7 years 1 week ago #148540
by PCW
Replied by PCW on topic Early Omniturn gang lathe to Linuxcnc?
Might be bad hardware (I've seen failing hard drives cause this kind of latency issue)
Might also be a BIOs issue of some kind
(Is your MB a AsRock J3355B?, that's what I tested)
At this point it might be quickest to just try another PC
Might also be a BIOs issue of some kind
(Is your MB a AsRock J3355B?, that's what I tested)
At this point it might be quickest to just try another PC
Please Log in to join the conversation.
Time to create page: 0.084 seconds
