Replies: 6 comments 2 replies
-
Ich nutze zwar den ebus-adapter v5 von John30 für eine atmoTEC exclusiv VCW DE 204/4-7-HL hatte bis vorhin aber die gleichen Probleme. Leider führte das nicht direkt zum Erfolg. Erst als ich in der Konfigurationsdatei --receivetimeout=100000 --latency=10000 einfügte bekam ich die Heizung angezeigt. Meine Konfig ist jetzt:
Danach machte ich viele Versuche etwas geziehlt zu lesen mit wenig Erfolg, da ich wohl nicht den richtigen Namen eingesetzt hatte. Die Namen konnte ich dann durch weitere Suche in Foren mit find auslesen.
Aber auch hier erhielt ich oft eine Fehlermeldung
eine direkte Wiederholung liefert dann ein gültiges Ergebnis.
Ich hoffe, das hilft dir weiter. Although I use the ebus adapter v5 from John30 for an atmoTEC exclusiv VCW DE 204/4-7-HL, I had the same problems until just now. Unfortunately, this did not lead directly to success. Only when I inserted --receivetimeout=100000 --latency=10000 in the configuration file did I get the heating displayed. My config is now:
I then made many attempts to read something in a targeted manner with little success, as I had probably not entered the correct name. I was then able to read the names by further searching in forums with find.
bai,AccessoriesOne,d.27 Option relay 1 But here, too, I often received an error message
a direct repetition then provides a valid result.
I hope this helps you. Translated with DeepL.com (free version) |
Beta Was this translation helpful? Give feedback.
-
Besten Dank für deine Hinweise, der enhanced Modus scheint nicht zu funktioniert, da konnte ich jetzt immer sehen, wie er die Verbindung aufbaut, aber sofort wieder ganz verliert und wieder von vorne startet. Aber ich habe jetzt die Latenz und Antwortzeit hochgesetzt...ich bin gespannt... |
Beta Was this translation helpful? Give feedback.
-
Ich habe deine Parameter noch eingebaut, leider keine Änderung. Ich überlege gerade, ob es am Regler liegen kann. Das ist eine Funkfernbedienung (bzw. wie eine Funkfernbedienung), könnte es an der liegen? Das die nicht/ nicht schnell genug antwortet? |
Beta Was this translation helpful? Give feedback.
-
ich starte den Service immer neu, nach Änderung der Konfiguration...leider bringen die Einstellungen derzeit keine Besserung. |
Beta Was this translation helpful? Give feedback.
-
Mir war vorhin aufgefallen, dass ich die Therme nicht mehr erreichte als ich mit |
Beta Was this translation helpful? Give feedback.
-
Tatsächlich gibt das keine Besserung. Das Verhalten ist derzeit immer gleich. Ich habe ein wenig den Regler im Verdacht, ob es an dem liegt. |
Beta Was this translation helpful? Give feedback.
-
Hello,
i have some problems with the connection/ scanning of eBus participants. Following configuration:
ebus-Koppler by ESERA, ebusd Version 23.3
log:
2024-01-19 11:50:00.902 [main debug] >>> i
2024-01-19 11:50:00.902 [main debug] <<< version: ebusd 23.3.23.3
update check: OK
device: tcp:192.168.178.33:5000, TCP
access: *
signal: acq ...
2024-01-19 11:50:00.903 [network info] [00025] connection closed
2024-01-19 11:50:01.109 [bus debug] arbitration won
2024-01-19 11:50:01.109 [bus debug] arbitration delay 4 micros
2024-01-19 11:50:01.109 [bus debug] switching from ready to send command
2024-01-19 11:50:01.114 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.120 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.125 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.131 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.131 [bus debug] switching from send command to send command>
2024-01-19 11:50:01.136 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.136 [bus debug] switching from send command CRC to receive >
2024-01-19 11:50:01.206 [bus debug] notify request: ERR: read timeout
2024-01-19 11:50:01.206 [bus info] scan c3 cmd: 31c3070400
2024-01-19 11:50:01.206 [bus debug] ERR: read timeout during receive command AC>
2024-01-19 11:50:01.206 [bus debug] start request 31
2024-01-19 11:50:01.206 [bus debug] arbitration start with 31
2024-01-19 11:50:01.648 [bus debug] arbitration won
2024-01-19 11:50:01.648 [bus debug] arbitration delay 10 micros
2024-01-19 11:50:01.649 [bus debug] switching from ready to send command
2024-01-19 11:50:01.655 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.662 [bus debug] send/receive symbol latency 7 ms
2024-01-19 11:50:01.668 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.673 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.673 [bus debug] switching from send command to send command>
2024-01-19 11:50:01.679 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:01.679 [bus debug] switching from send command CRC to receive >
2024-01-19 11:50:01.749 [bus debug] notify request: ERR: read timeout
2024-01-19 11:50:01.749 [bus info] scan c4 cmd: 31c4070400
2024-01-19 11:50:01.749 [bus debug] ERR: read timeout during receive command AC>
2024-01-19 11:50:01.749 [bus debug] start request 31
2024-01-19 11:50:01.750 [bus debug] arbitration start with 31
2024-01-19 11:50:01.767 [network debug] dead connection removed - 0
2024-01-19 11:50:02.230 [bus debug] ERR: CRC error during receive command CRC, >
2024-01-19 11:50:02.240 [bus debug] ERR: ACK error during receive command ACK, >
2024-01-19 11:50:02.470 [bus debug] arbitration won
2024-01-19 11:50:02.470 [bus debug] arbitration delay 5 micros
2024-01-19 11:50:02.470 [bus debug] switching from ready to send command
2024-01-19 11:50:02.476 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:02.482 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:02.487 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:02.493 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:02.493 [bus debug] switching from send command to send command>
2024-01-19 11:50:02.498 [bus debug] send/receive symbol latency 5 ms
2024-01-19 11:50:02.498 [bus debug] switching from send command CRC to receive >
2024-01-19 11:50:02.568 [bus debug] notify request: ERR: read timeout
2024-01-19 11:50:02.569 [bus info] scan c5 cmd: 31c5070400
2024-01-19 11:50:02.569 [bus debug] ERR: read timeout during receive command AC>
2024-01-19 11:50:02.569 [bus debug] start request 31
2024-01-19 11:50:02.569 [bus debug] arbitration start with 31
.
.
.
2024-01-19 11:50:03.650 [bus debug] notify request: ERR: read timeout
2024-01-19 11:50:03.650 [bus info] scan c7 cmd: 31c7070400
2024-01-19 11:50:03.650 [bus debug] ERR: read timeout during receive command AC>
2024-01-19 11:50:03.650 [bus debug] start request 31
2024-01-19 11:50:03.650 [bus debug] arbitration start with 31
2024-01-19 11:50:04.091 [bus debug] arbitration lost
2024-01-19 11:50:04.091 [bus debug] ERR: arbitration lost during ready, retry
2024-01-19 11:50:04.164 [bus debug] ERR: read timeout during receive command, s>
2024-01-19 11:50:04.164 [bus debug] start request 31
2024-01-19 11:50:04.164 [bus debug] arbitration start with 31
2024-01-19 11:50:04.647 [bus debug] arbitration lost
2024-01-19 11:50:04.648 [bus debug] ERR: arbitration lost during ready, retry
2024-01-19 11:50:04.720 [bus debug] ERR: read timeout during receive command, s>
2024-01-19 11:50:04.720 [bus debug] start request 31
and this repeats again and again.
My config:
EBUSD_OPTS="--scanconfig=full --configpath=https://cfg.ebusd.eu/ --accessleve=* -d tcp:192.168.XXX.XX:5000 --address=31 --latency 5000 --acquiretimeout=15000 --loglevel=debug --httpport=8889"
version: ebusd 23.3.23.3
update check: OK
device: tcp:192.168.178.33:5000, TCP
access: *
signal: acquired
symbol rate: 31
max symbol rate: 43
min arbitration micros: 3
max arbitration micros: 52
min symbol latency: 5
max symbol latency: 32
scan: finished
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning
i can't identify a problem, i change the cable, i change the koppler vom ECO305 to 12002, i set the threshold, nothing helps.
Beta Was this translation helpful? Give feedback.
All reactions