search

knxd / knxd

GNU General Public License v2.0
538 stars 201 forks source link

knxd with ft12cemi for Weinzierl KNX BAOS Modul 838 kBerry #469

Open fichto opened 4 years ago

fichto commented 4 years ago

Hello, i am trying since weeks to make the knxd run with ft12cemi driver on a raspberry 3b with the serial interface BAOS 838 kberry.

What i did:

sudo apt-get install git-core build-essential
git clone https://github.com/knxd/knxd.git
cd knxd
git checkout deb
apt install debhelper autotools-dev autoconf automake libtool libusb-1.0-0-dev pkg-config libev-dev libsystemd-dev dh-systemd base-files libfmt3-dev cmake
dpkg-buildpackage -b -uc
cd ..
sudo dpkg -i knxd_*.deb knxd-tools_*.deb
sudo nano /boot/config.txt >> add "dtoverlay=pi3-disable-bt" at the end<<
sudo nano /boot/cmdline.txt >> remove "console=serial0,115200 console=tty1"<<
sudo systemctl disable hciuart
sudo nano /etc/udev/rules.d/70-knxd.rules >> add "ACTION=="add", SUBSYSTEM=="tty", ATTRS{id}=="00241011", KERNELS=="3f201000.serial", SYMLINK+="ttyknx", OWNER="knxd"
sudo nano /etc/knxd.conf >> the only line "KNXD_OPTS=/etc/knxd.ini"<<
sudo nano /etc/knxd.ini 
>>
[A.unix]
path = /tmp/eib
server = knxd_unix
systemd-ignore = false
[C.ft12cemi]
device = /dev/ttyknx
driver = ft12cemi
[debug-server]
name = mcast:knxd
[main]
addr = 15.15.250
cache = B.cache
client-addrs = 15.15.251:4
connections = A.unix,server,C.ft12cemi
systemd = systemd
[server]
debug = debug-server
discover = true
server = ets_router
<<
sudo nano /etc/groups >> ... dialout:x:20:openhabian,openhab,knxd,root ...<<
sudo reboot

i get the following outputs: ls -ahl /dev/ttyknx lrwxrwxrwx 1 root root 7 Apr 16 09:49 /dev/ttyknx -> ttyAMA0 ls -ahl /dev/ttyAMA0 crw-rw---- 1 knxd dialout 204, 64 Apr 16 09:49 /dev/ttyAMA0 systemctl status knxd.socket ● knxd.socket - KNX Daemon (socket) Loaded: loaded (/lib/systemd/system/knxd.socket; enabled; vendor preset: enabled) Active: active (listening) since Thu 2020-04-16 09:49:22 BST; 7min ago Listen: /var/run/knx (Stream)

Tasks: 0 (limit: 2319)

Memory: 0B CGroup: /system.slice/knxd.socket Apr 16 09:49:22 openhab systemd[1]: Listening on KNX Daemon (socket). systemctl status knxd.service ● knxd.service - KNX Daemon Loaded: loaded (/lib/systemd/system/knxd.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2020-04-16 09:57:10 BST; 1s ago Process: 1262 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=1/FAILURE) Main PID: 1262 (code=exited, status=1/FAILURE) Apr 16 09:57:10 openhab systemd[1]: knxd.service: Failed with result 'exit-code'.

journalctl -u knxd --since "1 min ago" -- Logs begin at Wed 2020-03-25 11:39:38 GMT, end at Thu 2020-04-16 10:05:26 BST Apr 16 10:04:26 openhab systemd[1]: knxd.service: Service RestartSec=10s expired Apr 16 10:04:26 openhab systemd[1]: knxd.service: Scheduled restart job, restart Apr 16 10:04:26 openhab systemd[1]: Stopped KNX Daemon. Apr 16 10:04:26 openhab systemd[1]: Starting KNX Daemon... Apr 16 10:04:26 openhab systemd[1]: Started KNX Daemon. Apr 16 10:04:26 openhab knxd[621]: E00000044: [27:C.ft12cemi] reset timed out Apr 16 10:04:26 openhab knxd[621]: F00000105: [22:C.ft12cemi] Link down, termina Apr 16 10:04:26 openhab systemd[1]: knxd.service: Main process exited, code=exit Apr 16 10:04:26 openhab systemd[1]: knxd.service: Failed with result 'exit-code' Apr 16 10:04:37 openhab systemd[1]: knxd.service: Service RestartSec=10s expired Apr 16 10:04:37 openhab systemd[1]: knxd.service: Scheduled restart job, restart

I tried a lot but i cant fix this problem. It seems that the ft12cemi driver doesn't get a connection to the serial port and KNX hardware.

I hope anybody has an idea what i do wrong. Many thanks for replies.

Tom from Germany

fichto commented 4 years ago

Does nobody have an idea for fixing my issue? @smurfix Please could you give me a little help, i am confusing... :|

fichto commented 4 years ago

Now I bought the Busware Tul Stick and after 10 minutes it was working. The weinzierl is still not running....

sichiwai commented 4 years ago

I have a simliar setup, and was able to get some connection by a) Disableing BLUETOOTH & enabling UART0 and
Edit /boot/config.txt -> [PI4]

Had problems on the 64bit though, but that might have been other issues.

sichiwai commented 4 years ago

oh, and nuked the bluetooth software: systemctl disable hciuart apt-get purge bluez -y