Habe einen SDM630M-CT via Modus/TCP-IP Converter in FHEM eingebunden.
Die Anbindung funktioniert so weit, bis auf einige bad Frame Einträge die immer wieder häufiger auftreten.
2016.08.11 19:30:25 1: PERL WARNING: Use of uninitialized value $rx_bd_fc in numeric eq (==) at ./FHEM/36_ModbusTCPServer.pm line 333.
2016.08.11 19:30:25 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 18 00 00 00 06] 0A 04 00 18 00 02
2016.08.11 19:30:25 1: ModbusTCPServer_Parse: bad frame, received: [00 18 00 00 00 00]
2016.08.11 19:30:25 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 1A 00 00 00 06] 0A 04 00 1A 00 02
2016.08.11 19:30:25 1: ModbusTCPServer_Parse: bad frame, received: [00 1A 00 00 00 00]
2016.08.11 19:30:55 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 12 00 00 00 06] 0A 04 00 12 00 02
2016.08.11 19:30:55 1: ModbusTCPServer_Parse: bad frame, received: [00 12 00 00 00 00]
2016.08.11 19:31:25 1: PERL WARNING: Use of uninitialized value $dump[5] in concatenation (.) or string at ./FHEM/36_ModbusTCPServer.pm line 1045.
2016.08.11 19:31:25 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 00 00 00 00 06] 0A 04 00 00 00 02
2016.08.11 19:31:25 1: ModbusTCPServer_Parse: bad frame, received: [00 00 00 00 FF ]
2016.08.11 19:31:32 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [01 52 00 00 00 06] 0A 04 01 52 00 02
2016.08.11 19:31:32 1: ModbusTCPServer_Parse: bad frame, received: [01 52 00 00 00 00]
2016.08.11 19:32:56 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 18 00 00 00 06] 0A 04 00 18 00 02
2016.08.11 19:32:56 1: ModbusTCPServer_Parse: bad frame, received: [00 18 00 00 00 00]
2016.08.11 19:34:30 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 50 00 00 00 06] 0A 04 00 50 00 02
2016.08.11 19:34:30 1: ModbusTCPServer_Parse: bad frame, received: [00 50 00 00 FF ]
2016.08.11 19:34:59 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 2A 00 00 00 06] 0A 04 00 2A 00 02
2016.08.11 19:34:59 1: ModbusTCPServer_Parse: bad frame, received: [00 2A 00 00 00 00]
2016.08.11 19:36:02 1: PERL WARNING: Argument "" isn't numeric in numeric eq (==) at ./FHEM/36_ModbusTCPServer.pm line 333.
2016.08.11 19:36:02 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 50 00 00 00 06] 0A 04 00 50 00 02
2016.08.11 19:36:02 1: ModbusTCPServer_Parse: bad frame, received: [00 50 00 00 00 01] FF
2016.08.11 19:36:08 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 EE 00 00 00 06] 0A 04 00 EE 00 02
2016.08.11 19:36:08 1: ModbusTCPServer_Parse: bad frame, received: [00 EE 00 00 00 00]
Liegt das an meiner Konfiguration oder am Modbus.
Hat niemand eine Idee zu den Modbus bad Frames wie ich diese weg bekomme?
2016.09.22 18:21:52 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 6A 00 00 00 06] 0A 04 00 6A 00 02
2016.09.22 18:21:52 1: ModbusTCPServer_Parse: bad frame, received: [00 6A 00 00 00 01] FF
2016.09.22 18:21:53 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 66 00 00 00 06] 0A 04 00 66 00 02
2016.09.22 18:21:53 1: ModbusTCPServer_Parse: bad frame, received: [00 66 00 00 FF ]
2016.09.22 18:21:53 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 34 00 00 00 06] 0A 04 00 34 00 02
2016.09.22 18:21:53 1: ModbusTCPServer_Parse: bad frame, received: [00 34 00 00 00 00]
2016.09.22 18:21:53 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 42 00 00 00 06] 0A 04 00 42 00 02
2016.09.22 18:21:53 1: ModbusTCPServer_Parse: bad frame, received: [00 42 00 00 FF ]
2016.09.22 18:21:54 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 FE 00 00 00 06] 0A 04 00 FE 00 02
2016.09.22 18:21:54 1: ModbusTCPServer_Parse: bad frame, received: [00 FE 00 00 00 00]
2016.09.22 18:21:54 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 3C 00 00 00 06] 0A 04 00 3C 00 02
2016.09.22 18:21:54 1: ModbusTCPServer_Parse: bad frame, received: [00 3C 00 00 FF ]
Hallo,
Welche Version von ModbusTCPServer verwendest du ?
Die empfangenen Pakete sind zum Teil nicht vollständig, deshalb kommen die Meldungen.
Eventuell erfolgt die Abfrage des SDM zu schnell. Du kannst versuchen das Abfrageintervall des Servermodules mit
attr MBS pollInterval 5
zu erhöhen und die Anfragen mit
attr MBS combineReads 40
zu bündeln.
Grüße,
ChrisD
Habe die Parameter nach deinen Vorgaben angepasst.
Folgende Version werden verwendet.
Latest Revision: 12193
File Rev Last Change
fhem.pl 12192 2016-09-22 07:44:52Z rudolfkoenig
96_allowed.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
90_at.pm 12028 2016-08-21 12:08:28Z rudolfkoenig
98_autocreate.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
98_cloneDummy.pm 5919 2014-05-21 05:03:48Z joachim09876
00_CUL.pm 12027 2016-08-21 12:05:23Z rudolfkoenig
10_CUL_HM.pm 12138 2016-09-11 15:21:08Z martinp876
No Id found for 14_CUL_REDIRECT.pm
14_CUL_TCM97001.pm 11294 2016-04-21 20:32:28Z dancer0705
14_CUL_TX.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
98_dewpoint.pm 6757 2014-10-12 18:58:57Z joachim09876
98_DOIF.pm 11314 2016-04-26 18:29:24Z damian-s
98_dummy.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
70_ENIGMA2.pm 12048 2016-08-22 08:09:11Z loredo
91_eventTypes.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
93_FHEM2FHEM.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
01_FHEMWEB.pm 12007 2016-08-20 09:50:51Z rudolfkoenig
92_FileLog.pm 12193 2016-09-22 19:17:26Z rudolfkoenig
95_FLOORPLAN.pm 11443 2016-05-15 14:17:21Z ulimaass
10_FS20.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
98_help.pm 11992 2016-08-19 18:18:00Z betateilchen
14_Hideki.pm 14395 2016-07-14 18:00:00Z v3.2-dev
12_HMS.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
95_holiday.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
98_HTTPMOD.pm 11692 2016-06-19 09:08:31Z ststrobel
52_I2C_DS1307.pm 5927 2014-05-21 21:56:37Z ntruchsess
52_I2C_MCP23017.pm 12059 2016-08-22 21:14:59Z klauswitt
10_IT.pm 12179 2016-09-19 19:26:01Z dancer0705
70_JSONMETER.pm 11207 2016-04-08 20:12:23Z grompo
98_logProxy.pm 12056 2016-08-22 19:30:31Z justme1968
# $Id: 36_ModbusTCPServer.pm 0019 $
No Id found for 59_Moon.pm
91_notify.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
# $Id: 41_OREGON.pm 34476 2016-02-09 21:00:00 wherzig $
59_PROPLANTA.pm 11752 2016-07-06 16:27:06Z grompo
33_readingsGroup.pm 12137 2016-09-11 14:45:55Z justme1968
33_readingsProxy.pm 12056 2016-08-22 19:30:31Z justme1968
# $Id: 44_ROLLO.pm 1202 2016-08-29 19:14:00Z $ #
00_RPII2C.pm 12059 2016-08-22 21:14:59Z klauswitt
51_RPI_GPIO.pm 12129 2016-09-06 21:47:53Z klauswitt
# $Id: 14_SD_UT.pm 32 2016-04-02 14:00:00 v3.2-dev $
# $Id: 14_SD_WS.pm 32 2016-09-18 12:00:00 v3.2-dev $
# $Id: 14_SD_WS07.pm 9346 2016-07-14 18:00:00 v3.2-dev $
00_SIGNALduino.pm 10484 2016-09-18 16:00:00Z v3.3.0-dev
# $Id: 90_SIGNALduino_un.pm 15479 2016-01-28 20:00:00 dev-r32 $
98_structure.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
99_SUNRISE_EL.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
98_SVG.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
42_SYSMON.pm 11105 2016-03-20 19:37:02Z hexenmeister
32_SYSSTAT.pm 10567 2016-01-18 21:34:09Z justme1968
44_TEK603.pm 11877 2016-08-02 11:10:12Z eisler
98_telnet.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
45_TRX.pm 11456 2016-05-15 20:19:24Z wherzig
46_TRX_ELSE.pm 11451 2016-05-15 19:04:06Z wherzig
46_TRX_LIGHT.pm 11592 2016-06-01 21:15:30Z wherzig
46_TRX_SECURITY.pm 11452 2016-05-15 19:05:17Z wherzig
46_TRX_WEATHER.pm 11450 2016-05-15 19:03:23Z wherzig
10_UNIRoll.pm 6514 2014-09-07 11:10:40Z c-herrmann
99_Utils.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
98_version.pm 11987 2016-08-19 17:13:41Z markusbloch
98_weblink.pm 11984 2016-08-19 12:47:50Z rudolfkoenig
# $Id: 37_ModbusRegister.pm 0022 $
# $Id: 2016-06-15 10:31:44 V1.0 Christian Schmidt $
Blocking.pm 11918 2016-08-07 16:51:00Z rudolfkoenig
DevIo.pm 11786 2016-07-12 08:44:10Z rudolfkoenig
HMConfig.pm 12083 2016-08-28 06:10:21Z martinp876
HttpUtils.pm 12174 2016-09-19 05:53:59Z rudolfkoenig
RTypes.pm 10476 2016-01-12 21:03:33Z borisneubert
SetExtensions.pm 11513 2016-05-24 17:56:05Z rudolfkoenig
TcpServerUtils.pm 11908 2016-08-06 15:09:55Z rudolfkoenig
Die Änderung hat aber leider nichts gebracht.
2016.09.23 15:07:07 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [FD F4 00 00 00 06] 0A 04 00 00 00 6C
2016.09.23 15:07:07 1: ModbusTCPServer_Parse: bad frame, received: [FD F4 00 00 00 04] 0A 84 02 B3
2016.09.23 15:07:37 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [FD F7 00 00 00 06] 0A 04 00 00 00 6C
2016.09.23 15:07:37 1: ModbusTCPServer_Parse: bad frame, received: [FD F7 00 00 00 04] 0A 84 02 B3
Hallo,
Der Code 84 bedeutet SLAVE_DEVICE_FAILURE, das SDM kommt mit der Anfrage iregendwie nicht klar.
Kannst du das Modul auf Version 0020 updaten, das Attribut combineReads wieder löschen und es stattdessen mit
attr MBS queueDelay 200versuchen.
Grüße,
ChrisD
Wenn ich update ModbusTCPServer ausführe, bekomme ich als Rückmeldung nothing to do.
Hallo,
Du kannst die aktuelle Version mit
update force https://raw.githubusercontent.com/ChrisD70/FHEM-Modules/master/autoupdate/mb/controls_modbustcp.txt
installieren. Danach muss FHEM neu gestartet werden.
Grüße,
ChrisD
Habe FHEM jetzt komplett neu aufgesetzt und die aktuelle Version des ModbusServer installiert.
Parameter laut Vorgabe definiert.
pollInterval 5
queueDelay 200
state ist jetzt opened und nicht mehr ok
Trotzdem bekomme ich noch diese Meldungen.
2016.09.24 19:27:03 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 38 00 00 00 06] 0A 04 00 38 00 02, received 5 bytes
2016.09.24 19:27:17 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 28 00 00 00 06] 0A 04 00 28 00 02, received 5 bytes
2016.09.24 19:27:19 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 52 00 00 00 06] 0A 04 01 52 00 02, received 5 bytes
2016.09.24 19:27:21 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 56 00 00 00 06] 0A 04 01 56 00 02, received 5 bytes
2016.09.24 19:27:39 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 4E 00 00 00 06] 0A 04 00 4E 00 02, received 6 bytes
2016.09.24 19:27:40 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 50 00 00 00 06] 0A 04 00 50 00 02, received 5 bytes
2016.09.24 19:27:41 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 24 00 00 00 06] 0A 04 00 24 00 02, received 7 bytes
2016.09.24 19:27:42 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 18 00 00 00 06] 0A 04 00 18 00 02, received 6 bytes
2016.09.24 19:27:46 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 50 00 00 00 06] 0A 04 01 50 00 02, received 7 bytes
2016.09.24 19:27:52 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 56 00 00 00 06] 0A 04 01 56 00 02, received 5 bytes
2016.09.24 19:27:52 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 54 00 00 00 06] 0A 04 00 54 00 02, received 5 bytes
2016.09.24 19:27:54 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 64 00 00 00 06] 0A 04 00 64 00 02, received 5 bytes
Hallo,
Die Datenpakete die vom SDM kommen sind nicht vollständig und können somit auch nicht ausgewertet werden.
Welchen Umsetzer auf Modbus-TCP verwendest du ?
Grüße,
ChrisD
Bisher hatte ich dieses Problem nicht.
Das ist irgendwann bei den letzten FHEM Updates entstanden.
Im Einsatz habe ich den ModbusServer USR-TCP232-410 von http://www.usr.cn
Hallo,
Kannst du versuchen die UART packet Time zu erhöhen (auf 10, 20, 30 ms) ?
Das ist irgendwann bei den letzten FHEM Updates entstanden.
Hast du noch ein Backup mit dem alles funktioniert hat ? Wenn ja könnte man versuchen herauszufinden welche Änderungen am Code zum Fehler führen.
Grüße,
ChrisD
Egal welche UART packet Time größer 0 eingetragen wírd, kommt sofort eine timeout Meldungen des ModbusTCPServer Moduls selbst.
Ich habe jetzt den Parameter serverType Wago für das ModbusTCPServer Modul eingetragen.
Momentan sieht es aus, dass dieser Paramter das Problem behoben hat.
LIST:
Internals:
CFGFN /media/hdd/fhem/mycfg/Allgemein_rasp01.cfg
DEF 192.168.17.245:502
DeviceName 192.168.17.245:502
FD 5
NAME MBS
NR 160
NTFY_ORDER 50-MBS
PARTIAL
STATE ok
TYPE ModbusTCPServer
server Wago 1422-7424
statistics 66 / 63 / 808 / 756
Readings:
2016-09-27 09:49:33 state opened
Helper:
delayNextRead 0
delayNextWrite 0
fc 3
hd_tr_id 4130
hd_unit_id 0
lastFrame SimpleWrite [10 22 00 00 00 06] 00 03 10 22 00 04
lastSimpleWrite ""
last_fc 3
last_hd_tr_id 8208
state idle
Wago:
INFO_ITEM 7424
INFO_MAJOR 0
INFO_MINOR 0
INFO_REVISION 4096
INFO_SERIES 1422
x 1
Statistics:
bytesIn 808
bytesOut 756
pktIn 66
pktOut 63
Attributes:
alias ModBus Server
devStateIcon timeout:lan_rs485@yellow opened:lan_rs485@green ok:lan_rs485@green disconnected:lan_rs485@red
group Schnittstellen LAN
icon lan_rs485
pollInterval 0.5
queueDelay 200
room _RxTx
serverType Wago
verbose 1
Es hat alles nicht geholfen.
Immer wieder tauchen diese Meldungen auf.
2016.10.07 16:00:02.304 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 10 00 00 00 06] 0A 04 00 10 00 02, received 6 bytes
2016.10.07 16:00:23.097 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 4C 00 00 00 06] 0A 04 00 4C 00 02, received 8 bytes
2016.10.07 16:00:29.574 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 16 00 00 00 06] 0A 04 00 16 00 02, received 6 bytes
2016.10.07 16:00:52.046 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 2E 00 00 00 06] 0A 04 00 2E 00 02, received 7 bytes
2016.10.07 16:00:54.906 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 00 00 00 00 06] 0A 04 00 00 00 02, received 5 bytes
2016.10.07 16:00:57.255 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 68 00 00 00 06] 0A 04 01 68 00 02, received 6 bytes
2016.10.07 16:01:05.075 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 42 00 00 00 06] 0A 04 00 42 00 02, received 7 bytes
2016.10.07 16:01:23.522 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 4E 00 00 00 06] 0A 04 00 4E 00 02, received 6 bytes
2016.10.07 16:01:29.066 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 20 00 00 00 06] 0A 04 00 20 00 02, received 6 bytes
2016.10.07 16:01:55.496 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 00 00 00 00 06] 0A 04 00 00 00 02, received 7 bytes
2016.10.07 16:04:01.790 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 74 00 00 00 06] 0A 04 01 74 00 02, received 7 bytes
2016.10.07 16:04:08.807 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 54 00 00 00 06] 0A 04 00 54 00 02, received 6 bytes
2016.10.07 16:04:27.329 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 2E 00 00 00 06] 0A 04 00 2E 00 02, received 6 bytes
2016.10.07 16:04:37.252 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 0A 00 00 00 06] 0A 04 00 0A 00 02, received 7 bytes
2016.10.07 16:05:00.878 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 00 00 00 00 06] 0A 04 00 00 00 02, received 5 bytes
2016.10.07 16:05:04.278 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 02 00 00 00 06] 0A 04 01 02 00 02, received 6 bytes
2016.10.07 16:05:08.380 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 0A 00 00 00 06] 0A 04 00 0A 00 02, received 6 bytes
2016.10.07 16:06:01.488 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 00 00 00 00 06] 0A 04 00 00 00 02, received 7 bytes
2016.10.07 16:06:38.596 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 6A 00 00 00 06] 0A 04 00 6A 00 02, received 5 bytes
2016.10.07 16:07:33.240 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 12 00 00 00 06] 0A 04 00 12 00 02
2016.10.07 16:07:33.241 1: ModbusTCPServer_Parse: bad frame, received: [00 12 00 00 FF 00] 12 00 00 00 08 0A 04 04 45 48 BA 40 A6
2016.10.07 16:07:41.480 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 64 00 00 00 06] 0A 04 01 64 00 02, received 6 bytes
2016.10.07 16:07:41.765 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 28 00 00 00 06] 0A 04 00 28 00 02, received 6 bytes
2016.10.07 16:08:02.903 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 12 00 00 00 06] 0A 04 00 12 00 02, received 7 bytes
2016.10.07 16:10:06.203 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 26 00 00 00 06] 0A 04 00 26 00 02, received 6 bytes
2016.10.07 16:11:08.183 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 02 00 00 00 06] 0A 04 00 02 00 02, received 6 bytes
2016.10.07 16:11:18.615 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 50 00 00 00 06] 0A 04 01 50 00 02, received 7 bytes
2016.10.07 16:11:45.603 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 04 00 00 00 06] 0A 04 00 04 00 02, received 6 bytes
2016.10.07 16:12:34.655 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 06 00 00 00 06] 0A 04 00 06 00 02, received 7 bytes
2016.10.07 16:13:11.354 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 5E 00 00 00 06] 0A 04 01 5E 00 02, received 6 bytes
2016.10.07 16:13:41.165 1: ModbusTCPServer_Parse: bad frame, sent: SimpleWrite [00 1C 00 00 00 06] 0A 04 00 1C 00 02
2016.10.07 16:13:41.166 1: ModbusTCPServer_Parse: bad frame, received: [00 1C 00 00 00 00] 00 1C 00 00 00 08 0A 04 04 C3 82 82 00 BD
2016.10.07 16:15:41.490 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 14 00 00 00 06] 0A 04 00 14 00 02, received 6 bytes
2016.10.07 16:15:42.384 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 0A 00 00 00 06] 0A 04 00 0A 00 02, received 7 bytes
2016.10.07 16:16:06.276 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [00 46 00 00 00 06] 0A 04 00 46 00 02, received 7 bytes
2016.10.07 16:16:10.219 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 02 00 00 00 06] 0A 04 01 02 00 02, received 6 bytes
2016.10.07 16:17:35.372 1: ModbusTCPServer_Parse: incomplete frame received, sent: SimpleWrite [01 54 00 00 00 06] 0A 04 01 54 00 02, received 6 bytes
2016.10.07 18:08:28.949 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/36_ModbusTCPServer.pm line 908.
2016.10.07 18:08:28.950 3: stacktrace:
2016.10.07 18:08:28.950 3: main::__ANON__ called by ./FHEM/36_ModbusTCPServer.pm (908)
2016.10.07 18:08:28.951 3: main::ModbusTCPServer_Timeout called by fhem.pl (2853)
2016.10.07 18:08:28.952 3: main::InternalTimer called by ./FHEM/36_ModbusTCPServer.pm (522)
2016.10.07 18:08:28.953 3: main::ModbusTCPServer_SimpleWrite called by ./FHEM/36_ModbusTCPServer.pm (987)
2016.10.07 18:08:28.953 3: main::ModbusTCPServer_SendFromRQueue called by ./FHEM/36_ModbusTCPServer.pm (1002)
2016.10.07 18:08:28.954 3: main::ModbusTCPServer_AddRQueue called by ./FHEM/36_ModbusTCPServer.pm (548)
2016.10.07 18:08:28.955 3: main::ModbusTCPServer_DoInit called by ./FHEM/DevIo.pm (217)
2016.10.07 18:08:28.955 3: main::__ANON__ called by ./FHEM/DevIo.pm (440)
2016.10.07 18:08:28.956 3: main::DevIo_OpenDev called by ./FHEM/36_ModbusTCPServer.pm (180)
2016.10.07 18:08:28.957 3: main::ModbusTCPServer_Notify called by fhem.pl (3221)
2016.10.07 18:08:28.957 3: main::CallFn called by fhem.pl (3143)
2016.10.07 18:08:28.958 3: main::DoTrigger called by fhem.pl (1329)
2016.10.07 18:08:28.959 3: main::CommandRereadCfg called by fhem.pl (2898)
Hallo,
Es werden immer wieder unvollständige oder fehlerhafte Pakete geschickt. Das Modul kann damit nichts anfangen und verwirft die Daten. So ist z.B. im Paket
Zitat[00 1C 00 00 00 00] 00 1C 00 00 00 08 0A 04 04 C3 82 82 00 BD
ein Teil des Headers doppelt vorhanden (00 1C 00 00 00).
Die fehlerhaften Pakete können auf dem RS485-Bus entstehen (Abschlusswiderstände vorhanden ?) oder beim Gateway (Timing).
Grüße,
ChrisD