Watchdog has bit!

More
13 Jun 2020 12:31 #171418 by little_sparky
Replied by little_sparky on topic Watchdog has bit!
To reconfigure eth0 do I use:
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

Please Log in or Create an account to join the conversation.

More
13 Jun 2020 13:04 #171427 by Mike_Eitel
Replied by Mike_Eitel on topic Watchdog has bit!
Give it a try. Should work.
Sorry to many different linux versions to be sure..
The following user(s) said Thank You: little_sparky

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 03:39 #171541 by little_sparky
Replied by little_sparky on topic Watchdog has bit!
Sadly still getting the message.

I’m honestly not sure what to do now. Should I buy a new computer? Or how else can I pinpoint the fault?

This is really starting to become a nightmare

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 04:07 #171544 by PCW
Replied by PCW on topic Watchdog has bit!
What ping times do you get if you ping the 7I76E card?

Can you post your hal/ini files?

What does

ethtool -c eth1

report?

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 05:05 - 14 Jun 2020 05:08 #171554 by little_sparky
Replied by little_sparky on topic Watchdog has bit!
ethtool didnt seem to work. it said command not found
jonty@jonty:~$ ethtool -c eth1
bash: ethtool: command not found
jonty@jonty:~$ ethtool -c eth0
bash: ethtool: command not found

i am also not sure if i am using eth0 or eth1 but most things point towards eth0.

File Attachment:

File Name: jonty_plasma2.ini
File Size:10 KB


File Attachment:

File Name: jonty_plasma2.hal
File Size:12 KB
Attachments:
Last edit: 14 Jun 2020 05:08 by little_sparky. Reason: attachments

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 05:10 #171555 by little_sparky
Replied by little_sparky on topic Watchdog has bit!
some extra information so see if it means anything.

latency test results.



ip a
jonty@jonty:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 18:03:73:36:2f:1b brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.11/24 brd 10.10.10.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::1a03:73ff:fe36:2f1b/64 scope link
       valid_lft forever preferred_lft forever

uname -r
jonty@jonty:~$ uname -r
4.9.0-12-rt-amd64

uname -a
jonty@jonty:~$ uname -a
Linux jonty 4.9.0-12-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.210-1 (2020-01-20) x86_64 GNU/Linux
Attachments:

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 05:11 #171556 by little_sparky
Replied by little_sparky on topic Watchdog has bit!
sorry here is the ping results too

from ping 10.10.10.10
jonty@jonty:~$ ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10): 56 data bytes
64 bytes from 10.10.10.10: icmp_seq=0 ttl=64 time=0.161 ms
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.100 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.084 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.084 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.099 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.085 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.098 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.080 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.098 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.088 ms

64 bytes from 10.10.10.10: icmp_seq=279 ttl=64 time=0.109 ms
64 bytes from 10.10.10.10: icmp_seq=280 ttl=64 time=0.096 ms
64 bytes from 10.10.10.10: icmp_seq=281 ttl=64 time=0.105 ms
64 bytes from 10.10.10.10: icmp_seq=282 ttl=64 time=0.109 ms
64 bytes from 10.10.10.10: icmp_seq=283 ttl=64 time=0.105 ms
64 bytes from 10.10.10.10: icmp_seq=284 ttl=64 time=0.103 ms
64 bytes from 10.10.10.10: icmp_seq=285 ttl=64 time=0.118 ms
64 bytes from 10.10.10.10: icmp_seq=286 ttl=64 time=0.101 ms
64 bytes from 10.10.10.10: icmp_seq=287 ttl=64 time=0.101 ms
64 bytes from 10.10.10.10: icmp_seq=288 ttl=64 time=0.106 ms
64 bytes from 10.10.10.10: icmp_seq=289 ttl=64 time=0.097 ms
64 bytes from 10.10.10.10: icmp_seq=290 ttl=64 time=0.107 ms
64 bytes from 10.10.10.10: icmp_seq=291 ttl=64 time=0.102 ms
64 bytes from 10.10.10.10: icmp_seq=292 ttl=64 time=0.103 ms
64 bytes from 10.10.10.10: icmp_seq=293 ttl=64 time=0.105 ms
64 bytes from 10.10.10.10: icmp_seq=294 ttl=64 time=0.099 ms
64 bytes from 10.10.10.10: icmp_seq=295 ttl=64 time=0.102 ms
64 bytes from 10.10.10.10: icmp_seq=296 ttl=64 time=0.102 ms
64 bytes from 10.10.10.10: icmp_seq=297 ttl=64 time=0.107 ms
^C--- 10.10.10.10 ping statistics ---
298 packets transmitted, 298 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.080/0.099/0.264/0.000 ms

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 05:52 #171559 by PCW
Replied by PCW on topic Watchdog has bit!
OK so you do not have ethtool
This can be remedied by

sudo apt-get install ethtool

Note that the interfaces file setting of IRQ coalescing will not work without ethtool
Though the ping time do look OK so it may not be needed with the particular chip
set used.

The Dell 990 uses a 82579LM Ethernet chip, and I have seen some reports of this
being buggy and unreliable for realtime not sure if this is the issue here

If it is an issue an add-in Ethernet card should fix the problem

On possible thing to check is if a slower servo thread helps, so you might try 2 ms
(2000000 ns) This will require changing all the PID P terms to 500

Reading the tmax values would also help.
From a terminal with LinuxCNC running:

halcmd show pin *.tmax

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 06:40 #171566 by little_sparky
Replied by little_sparky on topic Watchdog has bit!
updating the ethtool gave this.
jonty@jonty:~$ sudo apt-get install ethtool
Reading package lists... Done
Building dependency tree       
Reading state information... Done
ethtool is already the newest version (1:4.8-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
jonty@jonty:~$ ethtool -c eth1
bash: ethtool: command not found
jonty@jonty:~$ ethtool -c eth0
bash: ethtool: command not found
jonty@jonty:~$ sudo ethtool -c eth0
Coalesce parameters for eth0:
Adaptive RX: off  TX: off
stats-block-usecs: 0
sample-interval: 0
pkt-rate-low: 0
pkt-rate-high: 0

rx-usecs: 0
rx-frames: 0
rx-usecs-irq: 0
rx-frames-irq: 0

tx-usecs: 0
tx-frames: 0
tx-usecs-irq: 0
tx-frames-irq: 0

rx-usecs-low: 0
rx-frame-low: 0
tx-usecs-low: 0
tx-frame-low: 0

rx-usecs-high: 0
rx-frame-high: 0
tx-usecs-high: 0
tx-frame-high: 0

i couldnt seem to get halcmd show pin *.tmax to give any values.

this is what came up.

Attachments:

Please Log in or Create an account to join the conversation.

More
14 Jun 2020 12:48 #171600 by PCW
Replied by PCW on topic Watchdog has bit!
Sorry that's:

halcmd show param *.tmax

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.422 seconds
Powered by Kunena Forum