Making first setup work ...

[fluppie]

http://www.uradmonitor.com/bosch-bme680/ and https://www.bosch-sensortec.com/bst/..._iot-smarthome

The Urad's campaign: https://www.indiegogo.com/projects/uradmonitor#/

So they are able to get hold of BME680 sensors... On Twitter I read Q1/2017 https://twitter.com/search?vertical=...c=typd&lang=nl

[fluppie]

Sadly, no programming for me. I'm suspecting my MDT IP interface. But ETS5 is logging the programming signals from the suite. I'm getting a little bit frustrated why I'm not having succes. Because I really like the idea of a programmable DIY KNX device.

[Eugenius]

Fluppie, try to send true or false to 0/0/1 GA with connection Test Sketch. It turns ProgLed on or off. So you can Test KNX-to-Arduinino direction. 0/0/2 is Arduino to KNX direction

And try Groupadress Monitor in the Suite, if it doesn't show any messages, it's PC/IP interface issue

[tuxedo]

Eugenius
The data the suite is sending, can be seen in ETS... So suite is working well with the interface.

fluppie
It's not clear to me:

Can you see the telegrams in ETS Eugen's example sketch with hard-coded groupaddresses is sending?

If you have an arduino with rx/tx leds onboard: If you send a telegram from ETS (doesn't matter what and to which groupaddress): Does the RX led blink/flicker according at the time you press the send button in ETS?

I'll try to give you (tomorrow) some hint's on enabling some more debug in the arduino device lib to get closer to the root-cause.

Another point: You can try to set a individual address in the suite that matches your area/line instead of using 15.15.255 .. Maybe there's something between ip interface and arduino that is blocking telegrams from different are/line ...

btw: Your screenshot is still showing german language. It should be english?! Can you copy&paste the first few lines of beta3 debug log file? especiall with the line that tells the current used locale setting.

[fluppie]

Fluppie, try to send true or false to 0/0/1 GA with connection Test Sketch. It turns ProgLed on or off. So you can Test KNX-to-Arduinino direction. 0/0/2 is Arduino to KNX direction

And try Groupadress Monitor in the Suite, if it doesn't show any messages, it's PC/IP interface issue

This works just fine . I'm going to try tuxedo's suggestion and reprogram the interface to 1.1.255

[tuxedo]

That means: if you sent Telegramm with ETS it is received by sketch. If suite sends Telegram it is not received?

I wanted you to give the suite another address, like 1.1.254. but setting the interface to 1.1.255 is also a good idea.

[fluppie]

IP interface is now 1.1.255 the tunneling addresses remain 15.15.something
Maybe I should reset the IP interface to factory settings? Only there is no English manual on the MDT site

[tuxedo]

Try to switch your Suite config to 1.1.254 (https://knx-user-forum.de/filedata/fetch?id=938418 --> old: 15.15.255 new: 1.1.254) and try again.

I'm sure that resetting the MDT Interface to factory will not solve this issue. The interface IS actually working. The received suite telegrams in ETS proves this.

It would help us to solve the problem, if you try to answer not only half of our questions ;-)

Open questions are:

> That means: if you sent Telegramm with ETS it is received by sketch. If suite sends Telegram it is not received?


Regarding the wrong user interface language of the suite:

I think I found the problem. Until I got time to fix it, you can add the selected part in suite's .BAT file:

suite_lang_en.png
This will force the language selection to EN.

If you want to translate to NL, download this file: https://github.com/KONNEKTING/Konnek..._en.properties, replace the translation (key=translation) and send it back to me (or create a github pull request for a file called Bundle_nl.properties in same folder).

[tuxedo]

Any update?

[fluppie]

Normally I'll have some time tonight.

[fluppie]

Sadly no progress with using 1.1.255/1.1.254 as address... See logfiles and screencaps in the ZIP file or "KonnektingTest2" in the Public folder: http://fluppie.backupcssolutions.be

I can achieve 2-way communication with the hard-coded example. If I send a telegram to the Konnekting device the prog led burns. I also receive the telegrams sent by the Konnekting device.

Could to problem be the fact that my tunneling addresses remain 15.15.something?

KNX IP-Interface
Status Programming Mode:	Off
Change Programming Mode:
Individual Address	1. 1.255
Tunneling Addresses	15.15.241 15.15.242 15.15.243 15.15.244
Set Tunneling Addresses
Serial Number	0083-477F02D2
TP Device
Status Programming Mode:	Off
Change Programming Mode:
Individual Address	15.15.254
Serial Number	0083-477F02D3

Also in the screencap from ETS you see "bronadres" = source address 15.15.242
The german manual (no English manual yet) speaks also of 15.15.something tunnelings addresses: http://www.mdt.de/download/MDT_THB_IP_Interface_02.pdf

To confirm, I run the suite under Windows 8.1 Pro x64 with this shortcut: KONNEKTING-Suite_DEBUG.bat

[tuxedo]

If you send from ETS to Arduino: which "bronadres" is logged?

[fluppie]

From my Raspberry Pi with Node-Red and the KNX node it's 15.15.241 and from ETS to bus = 15.15.242

The funny thing is, the KNX node (https://www.npmjs.com/package/node-red-contrib-knx) is not receiving the programming commands from the Konnekting Suite, where ETS5 is receiving them.

[tuxedo]

It's getting more and more confusing... A lot of information in many posts. I'm getting lost.

So, I try to collect the information and sum it up:

MDT IP-Interface:
* has tunneling-addresses (according to it's webinterface -> https://knx-user-forum.de/forum/proj...7#post939157):
** 15.15.241
** 15.15.242
** 15.15.243
** 15.15.244

---> Looks okay so far

Suite:
* uses tunneling
* uses address: 15.15.242 (as seen in ETS group monitor -> https://knx-user-forum.de/forum/proj...157#post939157 --> "Try1.PNG in attached ZIP)
* Screenshot ( a few posts earlier) showing suite config with address 15.15.255?! Is this still fact? --> https://knx-user-forum.de/filedata/fetch?id=938418

---> Confusing. Which address is now configured in suite? It should match the one seen in ETS group monitor + it must be one address that is not used by anyone else.


ETS:
* uses tunneling
* uses address: unclear ...

---> Take screenshot of ETS interface configuration.


Arduino with Siemens BCU:
* is in principle able to send to bus --> https://knx-user-forum.de/forum/proj...122#post938122
* is in principle able to receive from bus, send via ETS group monitor --> https://knx-user-forum.de/forum/proj...498#post938498

---> Looks okay so far

If the ETS is sending with individual address 1.1.255 and this is working, we should try to change the tunneling addresses in MDT IP Interface to 1.1.25x ...

But... step by step.
In the meantime I will try to experiment with the tunneling part of my MDT IP Router (should behave identically to MDT IP Interface).

[tuxedo]

I made a short video showing my setup using Arduino Leonardo, Siemens BCU, FTDI Adapter and MDT Interface (actually it's a router, but I'm using for this test the interface part only).

Configuration:

Tunnelingaddresses:

Same as your's:
** 15.15.241 ---> ETS
** 15.15.242 ---> Suite
** 15.15.243
** 15.15.244

The first one is configured in ETS, the 2nd one is configured in the Suite.

Upload is currently in progress: https://youtu.be/bO0NsO_nhOo

[update]
Finally found out why my ETS showed 1.0.254 as suite's adress instead auf 15.15.242 ... I mentioned that I DID a restart of the suite to apply the changes (switching from routing to tunneling to do the test). but obviously I did NOT restart the suite, so the programming was done via the old configuration (--> routing).

I did the same test again, but with restarted suite. Works exaclty the same, but this time the address logged in ETS is 15.15.242 as expected.


So, finally:
Please check your setup against the one in my video. If it's the same, my guess is that your IP Interface is somehow "defect".
If you have a 2nd Siemens BCU, you can use the Siemens BCU as your KNX Interface. Hook it up to an USB/RSR232 adapter (ftdi, cp2102....) and configure the suite to use the TPUART -> COM-port of your usb-adapter.

BE AWARE: To be electrically safe, you MUST use an galvanic isolation between Siemens BCU and your USB adapter. Something like a good optocoupler or an ADUM1201! Use without galvanic isolation ON YOUR OWN RISK.