Modbus Adapter: Poll error count e3dc S10
-
Ist das Modbus TCP oder Seriell?
-
-
Mal das PE11 oder was auch immer genau die Gegenstelle zum Modbus Adapter ist neu gestartet?
Mal einen PING auf das Device gemacht und die Zeiten angeschaut?
Hatten letztens den Fall mit SMA WR. Da lag es am WR, nach einem kompletten Neustart des WR war das Problem weg.
Konnte man an den Antwortzeiten des Ping sehen.
-
Neustart habe ich schon öfter gemacht.
Ich hoffe das ich die Pingzeiten richt darstelle.
Last login: Sun Mar 13 17:39:00 on ttys000 achimpassiep@Mac-mini-von-Achim ~ % ping 192.168.8.44 PING 192.168.8.44 (192.168.8.44): 56 data bytes 64 bytes from 192.168.8.44: icmp_seq=0 ttl=255 time=7.551 ms 64 bytes from 192.168.8.44: icmp_seq=1 ttl=255 time=12.303 ms 64 bytes from 192.168.8.44: icmp_seq=2 ttl=255 time=7.255 ms 64 bytes from 192.168.8.44: icmp_seq=3 ttl=255 time=111.964 ms 64 bytes from 192.168.8.44: icmp_seq=4 ttl=255 time=7.291 ms 64 bytes from 192.168.8.44: icmp_seq=5 ttl=255 time=9.604 ms 64 bytes from 192.168.8.44: icmp_seq=6 ttl=255 time=4.741 ms 64 bytes from 192.168.8.44: icmp_seq=7 ttl=255 time=7.498 ms 64 bytes from 192.168.8.44: icmp_seq=8 ttl=255 time=6.295 ms 64 bytes from 192.168.8.44: icmp_seq=9 ttl=255 time=6.520 ms 64 bytes from 192.168.8.44: icmp_seq=10 ttl=255 time=6.082 ms 64 bytes from 192.168.8.44: icmp_seq=11 ttl=255 time=9.055 ms 64 bytes from 192.168.8.44: icmp_seq=12 ttl=255 time=7.106 ms 64 bytes from 192.168.8.44: icmp_seq=13 ttl=255 time=6.613 ms 64 bytes from 192.168.8.44: icmp_seq=14 ttl=255 time=27.431 ms 64 bytes from 192.168.8.44: icmp_seq=15 ttl=255 time=7.738 ms 64 bytes from 192.168.8.44: icmp_seq=16 ttl=255 time=6.470 ms 64 bytes from 192.168.8.44: icmp_seq=17 ttl=255 time=18.053 ms 64 bytes from 192.168.8.44: icmp_seq=18 ttl=255 time=44.237 ms 64 bytes from 192.168.8.44: icmp_seq=19 ttl=255 time=8.979 ms 64 bytes from 192.168.8.44: icmp_seq=20 ttl=255 time=7.036 ms 64 bytes from 192.168.8.44: icmp_seq=21 ttl=255 time=9.036 ms 64 bytes from 192.168.8.44: icmp_seq=22 ttl=255 time=6.447 ms 64 bytes from 192.168.8.44: icmp_seq=23 ttl=255 time=13.222 ms 64 bytes from 192.168.8.44: icmp_seq=24 ttl=255 time=7.086 msMOD Edit: Log in Code Tags
-
@koenigpils läuft iobroker auf dem MAC ?
Du musst mal Ping vom iobroker Rechner aus machen
Wobei die Antwort Zeiten schon teilweise „hoch“ sind und stark schwanken.
-
@wendy2702
Komme nicht mehr auf meinen PaspyThe fingerprint for the ED25519 key sent by the remote host is SHA256:otCrXLnicRgAwbenAvIfyWvrpov7E6eEK7VZNBjXiJM. Please contact your system administrator. Add correct host key in /Users/achimpassiep/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/achimpassiep/.ssh/known_hosts:3 Host key for 192.168.8.35 has changed and you have requested strict checking. Host key verification failed. achimpassiep@Mac-mini-von-Achim ~ % Last login: Sun Mar 13 17:56:00 on ttys000 achimpassiep@Mac-mini-von-Achim ~ % ssh pi@192.168.8.35 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ED25519 key sent by the remote host is SHA256:otCrXLnicRgAwbenAvIfyWvrpov7E6eEK7VZNBjXiJM. Please contact your system administrator. Add correct host key in /Users/achimpassiep/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/achimpassiep/.ssh/known_hosts:3 Host key for 192.168.8.35 has changed and you have requested strict checking. Host key verification failed. achimpassiep@Mac-mini-von-Achim ~ %MOD Edit: Log in Code Tags
-
@koenigpils was steht in dem erwähnten known Hosts File?
-
@wendy2702
habe den Mac erst seit kurzen, ich weiss nicht wie ich da hinkomme. -
-
@wendy2702
Geht wieder ,tausend Dank64 bytes from 192.168.8.44: icmp_seq=1 ttl=255 time=3.90 ms 64 bytes from 192.168.8.44: icmp_seq=2 ttl=255 time=5.49 ms 64 bytes from 192.168.8.44: icmp_seq=3 ttl=255 time=4.07 ms 64 bytes from 192.168.8.44: icmp_seq=4 ttl=255 time=4.13 ms 64 bytes from 192.168.8.44: icmp_seq=5 ttl=255 time=3.16 ms 64 bytes from 192.168.8.44: icmp_seq=6 ttl=255 time=2.89 ms 64 bytes from 192.168.8.44: icmp_seq=7 ttl=255 time=13.9 ms 64 bytes from 192.168.8.44: icmp_seq=8 ttl=255 time=3.43 ms 64 bytes from 192.168.8.44: icmp_seq=9 ttl=255 time=3.79 ms 64 bytes from 192.168.8.44: icmp_seq=10 ttl=255 time=3.56 ms 64 bytes from 192.168.8.44: icmp_seq=11 ttl=255 time=4.80 ms 64 bytes from 192.168.8.44: icmp_seq=12 ttl=255 time=8.21 ms 64 bytes from 192.168.8.44: icmp_seq=13 ttl=255 time=3.36 ms 64 bytes from 192.168.8.44: icmp_seq=14 ttl=255 time=4.06 ms 64 bytes from 192.168.8.44: icmp_seq=15 ttl=255 time=9.30 ms 64 bytes from 192.168.8.44: icmp_seq=16 ttl=255 time=3.81 ms 64 bytes from 192.168.8.44: icmp_seq=17 ttl=255 time=3.49 ms 64 bytes from 192.168.8.44: icmp_seq=18 ttl=255 time=4.31 ms 64 bytes from 192.168.8.44: icmp_seq=19 ttl=255 time=4.69 ms 64 bytes from 192.168.8.44: icmp_seq=20 ttl=255 time=3.88 ms 64 bytes from 192.168.8.44: icmp_seq=21 ttl=255 time=6.50 ms 64 bytes from 192.168.8.44: icmp_seq=22 ttl=255 time=5.00 ms 64 bytes from 192.168.8.44: icmp_seq=23 ttl=255 time=18.5 ms 64 bytes from 192.168.8.44: icmp_seq=24 ttl=255 time=4.39 ms 64 bytes from 192.168.8.44: icmp_seq=25 ttl=255 time=6.01 ms 64 bytes from 192.168.8.44: icmp_seq=26 ttl=255 time=48.7 ms 64 bytes from 192.168.8.44: icmp_seq=27 ttl=255 time=3.15 ms 64 bytes from 192.168.8.44: icmp_seq=28 ttl=255 time=4.83 ms 64 bytes from 192.168.8.44: icmp_seq=29 ttl=255 time=4.71 ms 64 bytes from 192.168.8.44: icmp_seq=30 ttl=255 time=3.19 ms 64 bytes from 192.168.8.44: icmp_seq=31 ttl=255 time=5.28 ms 64 bytes from 192.168.8.44: icmp_seq=32 ttl=255 time=3.74 ms 64 bytes from 192.168.8.44: icmp_seq=33 ttl=255 time=18.8 msMOD Edit: Log in Code Tags
-
