Zitat von Goahead
Beitrag anzeigen
If it's the case, it confirms that the port is /dev/ttyS0 and that we can send and receive through it.
I was expecting to receive exactly what we have sent, but the last 3 "Recv(...):" lines contain something else. I converted the hex data of these three lines, and got "BusyBox v1.4.2 (2007-05-14 21:50:52 CEST) Built-...". This is a console message. Because the serial port is by default connected to a console to allow people to connect it to a PC (with hyperterminal for example) and see the messages when the system is booting. Here is seems that EIBD and the console are both using the serial port at the same time and they end up talking to each other.
The serial console is started by a line in /etc/inittab file that looks like this:
tts/0::askfirst:/bin/ash --login
You'll have to remove it or comment it by putting a # at the beginning of the line.
Once you removed it, restart the router and try again (be careful, doing something wrong there could block completely the router, ask first if you're not sure)
Zitat von Goahead
Beitrag anzeigen
If you want to access eibd with "knxswrite ip:127.0.0.1 1/1/1 0", you must start eibd with -i option instead of -u to enable network sockets instead of unix sockets.
When you start EIBD without the -d option (e.g. "eibd -u ft12:/dev/ttyS0 -t1023"), it will display the log messages, but EIBD will stop when you do <ctrl>-C. To have EIBD running, you can start it in one command window, and open another command window to start knxswrite in parallel. Or you can start eibd with -d option, but then you don't see the messages.
To check if EIBD is running, you can do "ps ax | grep eibd" and see if there is a line corresponding to it.
Zitat von Goahead
Beitrag anzeigen
Another question, how did you connect the serial port to the bus coupler (5wg1 114-2AB02)?
Regards,
Jean-François
Kommentar