Neues YouTube-Video: Visualisierung im Devices-Adapter

[winny1904]

Hallo zusammen,

Ich habe gestern meinen Ebus adapter für den Raspi bekommen.

Er liefert mir auch schon ein paar Daten. Aber nichts brauchbares.

Wir nutzen ein Ochsner WP. Das ganze soll vom EBUSD 3 Asapter für den Raspi ausgelesen werden.

# /etc/default/ebusd:
# config file for ebusd service.

# Options to pass to ebusd (run "ebusd -?" for more info):
EBUSD_OPTS="-d enh:/dev/ttyAMA0 -p 8888  --latency=50 --receivetimeout=100000 -l /var/log/ebusd.log  --scanconfig c /etc/ebusd  --configpath=/etc/ebusd  --httpport=8889 --htmlpath=/var/ebu$

# MULTIPLE EBUSD INSTANCES WITH SYSV
# In order to run multiple ebusd instances on a SysV enabled system, simply
# define several EBUSD_OPTS with a unique suffix for each. Recommended is to
# use a number as suffix for all EBUSD_OPTS settings. That number will then be
# taken as additional "instance" parameter to the init.d script in order to
# start/stop an individual ebusd instance instead of all instances.
# Example: (uncomment the EBUSD_OPTS above)
#EBUSD_OPTS1="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0 -p 8888 -l /var/log/ebusd1.log"
#EBUSD_OPTS2="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A900acTF-if00-port0 -p 8889 -l /var/log/ebusd2.log"
#EBUSD_OPTS3="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A900beCG-if00-port0 -p 8890 -l /var/log/ebusd3.log"

# MULTIPLE EBUSD INSTANCES WITH SYSTEMD
# In order to run muiltiple ebusd instances on a systemd enabled system, just
# copy the /usr/lib/systemd/system/ebusd.service file to /etc/systemd/system/
# with a different name (e.g. ebusd-2.service), remove the line starting with
# 'EnvironmentFile=', and replace the '$EBUSD_OPTS' with the options for that
# particular ebusd instance.

Code: [Auswählen]

root@ServerEbus:/etc/ebusd# ebusd --checkconfig
2021-10-07 11:41:38.090 [main error] invalid configpath without scanconfig
root@ServerEbus:/etc/ebusd#

Auch das mit den CSV dateien habe ich probiert.

root@ServerEbus:/etc/ebusd# ls -al
insgesamt 32
drwxr-xr-x 3 root root 4096 Okt  7 11:37 .
drwxr-xr-x 4 root root 4096 Okt  6 20:21 ..
-rw-r--r-- 1 root root 5620 Okt  7 08:20 22102.csv
-rw-r--r-- 1 root root 1253 Okt  6 20:21 broadcast.csv
-rw-r--r-- 1 root root  754 Okt  6 20:21 memory.csv
-rw-r--r-- 1 root root 2377 Okt  7 08:20 _templates.csv
drwxr-xr-x 2 root root 4096 Okt  6 20:21 vaillant

Könnt ihr mir vlt sagen wo der fehler liegt.

[crunchip]

@winny1904 habe heut auch installiert, komm aber auch nicht weiter, hab den Adapter an einem Raspberry Zero

[winny1900]

Hallo

I)ch habe heute noch einmal das ganze System neu aufgesetzt

Instaliert wurde nach dieser seit Link Text

Die Konfig wurde so angepasst

EBUSD_OPTS="-d enh:/dev/ttyAMA0 --latency=50 --receivetimeout=100000 -l /var/log/ebusd.log --scanconfig=full  --configpath=http://ebusd.eu/config/  --httpport=8889  --htmlpath=/va$"

Mache ich dann ein ebusctl Info kommt das dabei herum

root@ServerEbus:/home/pi# ebusctl info
version: ebusd 21.2.v21.2
update check: OK
signal: acquired
symbol rate: 44
max symbol rate: 97
min arbitration micros: 2
max arbitration micros: 15
min symbol latency: 10
max symbol latency: 33
reconnects: 0
masters: 5
messages: 15
conditional: 0
poll: 0
update: 4
address 01: master #6
address 03: master #11
address 06: slave #6, scanned "MF=TEM;ID=25440;SW=0113;HW=0000"
address 08: slave #11, scanned "MF=TEM;ID=WE_1 ;SW=3632;HW=3030"
address 10: master #2
address 13: master #12
address 15: slave #2, scanned "MF=TEM;ID=24849;SW=0605;HW=0102"
address 18: slave #12, scanned "MF=TEM;ID=WE_2 ;SW=3632;HW=3030"
address 31: master #8, ebusd
address 36: slave #8, ebusd

bei status

root@ServerEbus:/home/pi# service ebusd status
● ebusd.service - LSB: controls ebusd, the daemon for communication with eBUS he
   Loaded: loaded (/etc/init.d/ebusd; generated)
   Active: active (running) since Sun 2021-10-10 21:26:30 CEST; 4min 35s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1531 ExecStart=/etc/init.d/ebusd start (code=exited, status=0/SUCCESS
    Tasks: 4 (limit: 2062)
   CGroup: /system.slice/ebusd.service
           └─1538 /usr/bin/ebusd --pidfile /var/run/ebusd.pid -d enh:/dev/ttyAMA

Oct 10 21:26:30 ServerEbus systemd[1]: Starting LSB: controls ebusd, the daemon
Oct 10 21:26:30 ServerEbus ebusd[1531]: Starting ebusd: ebusd.
Oct 10 21:26:30 ServerEbus systemd[1]: Started LSB: controls ebusd, the daemon f
lines 1-12/12 (END)

Hat da vlt. jemand eine Idee ???

[crunchip]

ich bekomme den Dienst nicht mehr zum laufen. Nachdem ich das erst mal Installiert hatte, lief der Dienst, da aber keine Daten rein kamen, hatte ich nochmal neu installiert (SD Karte neu aufgesetzt).
Das habe ich jetzt schon 15mal in mehreren Varianten , mit/ohne upgrade (Kernel), zwischenreboot`s, ... , jedoch immer mit der gleichen Meldung. Hat jemand eine Idee?
Hardware Raspi Zero W, Raspian OS lite

1. Edit /etc/default/ebusd if necessary
   (especially if your device is not /dev/ttyUSB0)
2. Start the daemon with 'service ebusd start'
3. Check the log file /var/log/ebusd.log
4. Make the daemon autostart with 'update-rc.d ebusd enable'
Trigger für libc-bin (2.28-10+rpt2+rpi1) werden verarbeitet ...
Trigger für systemd (241-7~deb10u8+rpi1) werden verarbeitet ...
root@raspberrypi:/home/pi# nano  /etc/default/ebusd
root@raspberrypi:/home/pi# service ebusd start
Job for ebusd.service failed because the control process exited with error code.
See "systemctl status ebusd.service" and "journalctl -xe" for details.
root@raspberrypi:/home/pi# systemctl status ebusd.service
● ebusd.service - LSB: controls ebusd, the daemon for communication with eBUS heating systems.
   Loaded: loaded (/etc/init.d/ebusd; generated)
   Active: failed (Result: exit-code) since Mon 2021-10-11 10:27:22 CEST; 13s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 901 ExecStart=/etc/init.d/ebusd start (code=exited, status=139)

Okt 11 10:27:22 raspberrypi systemd[1]: Starting LSB: controls ebusd, the daemon for communication with eBUS heating systems....
Okt 11 10:27:22 raspberrypi ebusd[901]: Starting ebusd: ebusd/etc/init.d/ebusd: Zeile 43:   906 Speicherzugriffsfehler  start-stop-daemon --start --quiet --oknodo --pidfile $pidfile --exec $DAEMON
Okt 11 10:27:22 raspberrypi ebusd[901]:  failed!
Okt 11 10:27:22 raspberrypi systemd[1]: ebusd.service: Control process exited, code=exited, status=139/n/a
Okt 11 10:27:22 raspberrypi systemd[1]: ebusd.service: Failed with result 'exit-code'.
Okt 11 10:27:22 raspberrypi systemd[1]: Failed to start LSB: controls ebusd, the daemon for communication with eBUS heating systems..
lines 1-12/12 (END)
● ebusd.service - LSB: controls ebusd, the daemon for communication with eBUS heating systems.
   Loaded: loaded (/etc/init.d/ebusd; generated)
   Active: failed (Result: exit-code) since Mon 2021-10-11 10:27:22 CEST; 13s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 901 ExecStart=/etc/init.d/ebusd start (code=exited, status=139)

Okt 11 10:27:22 raspberrypi systemd[1]: Starting LSB: controls ebusd, the daemon for communication with eBUS heating systems....
Okt 11 10:27:22 raspberrypi ebusd[901]: Starting ebusd: ebusd/etc/init.d/ebusd: Zeile 43:   906 Speicherzugriffsfehler  start-stop-daemon --start --quiet --oknodo --pidfile $pidfile --exec $DAEMON -- --pidfile $pidfile ${!opts}
Okt 11 10:27:22 raspberrypi ebusd[901]:  failed!
Okt 11 10:27:22 raspberrypi systemd[1]: ebusd.service: Control process exited, code=exited, status=139/n/a
Okt 11 10:27:22 raspberrypi systemd[1]: ebusd.service: Failed with result 'exit-code'.
Okt 11 10:27:22 raspberrypi systemd[1]: Failed to start LSB: controls ebusd, the daemon for communication with eBUS heating systems..

root@raspberrypi:/home/pi# root@raspberrypi:/home/pi# journalctl -xe
bash: root@raspberrypi:/home/pi#: Datei oder Verzeichnis nicht gefunden
root@raspberrypi:/home/pi# -- The process' exit code is 'exited' and its exit status is 139.
> Okt 11 10:27:22 raspberrypi systemd[1]: ebusd.service: Failed with result 'exit-code'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- The unit ebusd.service has entered the 'failed' state with result 'exit-code'.
> Okt 11 10:27:22 raspberrypi systemd[1]: Failed to start LSB: controls ebusd, the daemon for communication with eBUS heating systems..
> -- Subject: A start job for unit ebusd.service has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- A start job for unit ebusd.service has finished with a failure.
> --
> -- The job identifier is 512 and the job result is failed.
> Okt 11 10:27:36 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories...
> -- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- A start job for unit systemd-tmpfiles-clean.service has begun execution.
> --
> -- The job identifier is 573.
> Okt 11 10:27:36 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
> -- Subject: Unit succeeded
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
> Okt 11 10:27:36 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
> -- Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- A start job for unit systemd-tmpfiles-clean.service has finished successfully.
> --
> -- The job identifier is 573.
> lines 1573-1609/1609 (END)
> -- The process' exit code is 'exited' and its exit status is 139.
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# Okt 11 10:27:22 raspberrypi systemd[1]: ebusd.service: Failed with result 'exit-code'.
bash: Okt: Kommando nicht gefunden.
root@raspberrypi:/home/pi# -- Subject: Unit failed
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# -- Defined-By: systemd
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# -- Support: https://www.debian.org/support
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# --
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# -- The unit ebusd.service has entered the 'failed' state with result 'exit-code'.
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# Okt 11 10:27:22 raspberrypi systemd[1]: Failed to start LSB: controls ebusd, the daemon for communication with eBUS heating systems..
bash: Okt: Kommando nicht gefunden.
root@raspberrypi:/home/pi# -- Subject: A start job for unit ebusd.service has failed
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi# -- Defined-By: systemd
bash: --: Kommando nicht gefunden.
root@raspberrypi:/home/pi#