Making first setup work ...

[fluppie]

I think I'm a step further using the Funky v3 / Lilypad USB:

delay for 255s
ready!

When I touch the resistor leg of D7 the programming LED triggers, it then keeps burning. But in the SoftSerial terminal I don't read progbutton 0 / 1.
Do I need a blinking LED to program? Or does the LED need to burn continously?

[Eugenius]

LED should burn continously.

"delay for xxx" comes from sketch. that means, that everything works ok.

[fluppie]

Programming doesn't work. Could it be my MDT SCN-IP000.02 interface? If I use the ETS5 group monitor I see telegrams when pressing the red button in the Konnekting Suite.

I uploaded my sketch, some screenshots from the suite and the log files. I tried both the normal mode and debug mode of the suite. http://fluppie.backupcssolutions.be/ in the Public folder.

[tuxedo]

When pressing the red button in the suite, you should press the prog-button on the device as well, so that the device tells prog-mode=1 on it's console.

During programming, you should see telegrams in ETS group monitor, sent from the suite (GA 15/7/255) and from the device back (same GA 15/7/255).

pls. repeat the programming process and post a screenshot of ETS group monitor, filtered for GA=15/7/255 telegrams.

[fluppie]

Weird, the terminal doesn't detect the prog button press. There's no activity in the SoftSerial terminal, but the led goes on/off.

ETS gives this:

<CommunicationLog xmlns="http://knx.org/xml/telegrams/01">
  <RecordStart Timestamp="2016-04-08T19:50:51.1859436Z" Mode="LinkLayer" Host="B4BEANTWR2263" ConnectionName="MDT KNX TP IP" ConnectionOptions="Tunneling, IPAddress=192.168.1.5, IPPort=3671, UseNat=False" ConnectorType="KnxIpTunneling" />
  <Telegram Timestamp="2016-04-08T19:53:22.0838417Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800001116400000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:27.0316711Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:32.0876591Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:37.1072729Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:42.1161921Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:47.1283214Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:52.1396993Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:53:57.277354Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:02.2862591Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:07.2958716Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:12.3337567Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:17.3441013Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:22.3559148Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:27.3676332Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:32.3802002Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:37.5191421Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:42.530456Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:47.5426219Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:52.5557773Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:54:57.5724238Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <Telegram Timestamp="2016-04-08T19:55:02.7163485Z" Service="L_Data.ind" FrameFormat="CommonEmi" RawData="2900BCE0FFF37FFF0F00800015000000000000000000000000" />
  <RecordStop Timestamp="2016-04-08T19:55:45.7310351Z" />
</CommunicationLog>

[fluppie]

Tried some more, I don't know if the "Lilypad clone" is the issue or not... I can trigger the prog button, but the softserial terminal gives no feedback regarding the progstate.
I'll try to get a "regular" Arduino Micro.

[tuxedo]

If you press the prog-button on your device, softserial console should show:

PROGBUTTON toggle
PROGBUTTON 1

If not, your device is not in prog-mode.

If device is in prog-mode, it should reply to thse 15/7/255 telegrams the suite is sending.

Have a look at your ETS groupmonitor log..
The you you posted contains always the same message, ending with those 14-byte messages:

"0015000000000000000000000000"

You can read thise data with help of our programming protocol documentation: https://github.com/KONNEKTING/Konnek...col_general.md

The 1st byte is always the protocol version. Right now, this is always 0x00.
The 2nd byte is the message type. Here you have 0x15 --> https://github.com/KONNEKTING/Konnek...ividualaddress ---> ReadIndividualAddress telegram.

The Suite is asking all listening devices for their individual address (=physical address). But there's no response (https://github.com/KONNEKTING/Konnek...ividualaddress) in your log.

A new device, which hasn't been programmed yet, must be programmed with the red button (this will set the individual address of the device).

Question is: Why is your arduino not logging any protocol request ...

Can you provide a complete softserial log?

[fluppie]

The funny thing is, this was my full log...

delay for 255s
ready!

No response in the SoftSerial terminal when pushing the button. The weird thing is that the led burns but the terminal does not give any feedback.
I ordered a Arduino Micro to make sure my Atmega32U4 device isn't working differently. Normally I'll have it by tomorrow.

[Eugenius]

fluppie, you have to change SoftSerial Pins also in KnxTools.cpp:

https://github.com/KONNEKTING/Konnek...xTools.cpp#L47

[tuxedo]

btw: we will release beta3 this week, but still without i18n. This will be a feature of beta4.

If you have questions about features or translation, feel free to ask.

[fluppie]

fluppie, you have to change SoftSerial Pins also in KnxTools.cpp:

https://github.com/KONNEKTING/Konnek...xTools.cpp#L47

Aha, well spotted. Will re-try tonight!
Once I have everything up and running, I'm willing to invest some time in translations / English quick start guide.

[fluppie]

Aha, now I get a lot more info in the terminal .

Setup KnxTools
createProgComObject
Manufacturer: DEADhex
Device: 1hex
Revision: 0hex
numberOfCommObjects: 7
_deviceFlags: 11111111bin
Using FACTORY
IA: 0x11FE
KnxDevice startup status: 0x0
getParamValue: index=0 _paramTableStartindex=31 skipBytes=0 paramLen=1
 val[0]@31 --> 0xFF
delay for 255s
ready!
getParamValue: index=1 _paramTableStartindex=31 skipBytes=1 paramLen=1
 val[0]@32 --> 0x81
getParamValue: index=2 _paramTableStartindex=31 skipBytes=2 paramLen=4
 val[0]@33 --> 0xD2
 val[1]@34 --> 0x1
 val[2]@35 --> 0x0
 val[3]@36 --> 0x0
getParamValue: index=3 _paramTableStartindex=31 skipBytes=6 paramLen=1
 val[0]@37 --> 0x0
getParamValue: index=4 _paramTableStartindex=31 skipBytes=7 paramLen=1
 val[0]@38 --> 0x0
getParamValue: index=5 _paramTableStartindex=31 skipBytes=8 paramLen=2
 val[0]@39 --> 0x0
 val[1]@40 --> 0x0
 int16: [1]=0x0 [0]=0x0
getParamValue: index=6 _paramTableStartindex=31 skipBytes=10 paramLen=1
 val[0]@41 --> 0x0
getParamValue: index=7 _paramTableStartindex=31 skipBytes=11 paramLen=2
 val[0]@42 --> 0x0
 val[1]@43 --> 0x0
 int16: [1]=0x0 [0]=0x0
getParamValue: index=8 _paramTableStartindex=31 skipBytes=13 paramLen=1
 val[0]@44 --> 0x0
getParamValue: index=9 _paramTableStartindex=31 skipBytes=14 paramLen=4
 val[0]@45 --> 0x0
 val[1]@46 --> 0x0
 val[2]@47 --> 0x0
 val[3]@48 --> 0x0
getParamValue: index=10 _paramTableStartindex=31 skipBytes=18 paramLen=1
 val[0]@49 --> 0x0
getParamValue: index=11 _paramTableStartindex=31 skipBytes=19 paramLen=1
 val[0]@50 --> 0x0
getParamValue: index=12 _paramTableStartindex=31 skipBytes=20 paramLen=2
 val[0]@51 --> 0x0
 val[1]@52 --> 0x0
 int16: [1]=0x0 [0]=0x0
getParamValue: index=13 _paramTableStartindex=31 skipBytes=22 paramLen=1
 val[0]@53 --> 0x0
getParamValue: index=14 _paramTableStartindex=31 skipBytes=23 paramLen=2
 val[0]@54 --> 0x0
 val[1]@55 --> 0x0
 int16: [1]=0x0 [0]=0x0
PROGBUTTON toggle
PROGBUTTON 1

Still, programming isn't working. Could it be the MDT IP-interface?
Device Info

Device is currently running in normal mode.

normal operation
true
192.168.1.5
255.255.255.0
192.168.1.1
192.168.1.1
8080
CC-1B-E0-XX-XX-XX
KNX-IPIF-XXXXXX
MDT KNX TP IP
uuid:025a2c2d-025a-2c49-4a51-xxxxxxxxxxx
1.0.03
2.1

Logged in (29 min left)

KNX IP-Interface
Status Programming Mode:	Off
Change Programming Mode:
Individual Address	15.15.255
Tunneling Addresses	15.15.241 15.15.242 15.15.243 15.15.244
Set Tunneling Addresses
Serial Number	0083-XXXXXXX
TP Device
Status Programming Mode:	Off
Change Programming Mode:
Individual Address	15.15.254
Serial Number	0083-XXXXXXX

[fluppie]

KONNEKTING Suite - Version 1.0.0-BETA2 Build 2016-02-23_19-57-37 DEBUG MODE!
Running on Windows 8.1
KNX Verbindung: IP-Interface
[Programmieren] Programmiere: 1.1.100 Temp RH test Phil
[Programmieren] Initialize...
[Programmieren] Reading commobjects...
[Programmieren] Reading parameters...
[Programmieren] Fortschritt: 1/26
[Programmieren] Please press 'program' button...
Fehler beim Programmieren.
de.konnekting.deviceconfig.ProgramException: Problem writing individual address
    at de.konnekting.deviceconfig.Program.program(Program.java:107)
    at de.konnekting.suite.ProgramDialog$4.run(ProgramDialog.java:172)
    at java.lang.Thread.run(Thread.java:745)
    at de.konnekting.suite.BackgroundTask$1.run(BackgroundTask.java:59)
Caused by: de.root1.slicknx.KnxException: Can not set address. no device in prog mode
    at de.konnekting.mgnt.protocol0x00.ProgProtocol0x00.writeIndividualAddress(ProgProtocol0x00.java:358)
    at de.konnekting.mgnt.KonnektingManagement.writeIndividualAddress(KonnektingManagement.java:72)
    at de.konnekting.deviceconfig.Program.program(Program.java:103)
    ... 3 more

[Programmieren] Fertig! Dauer: 106833ms

[tuxedo]

Ah... *idea*....
Check your IP Interface configuration in ETS. Some IP Router/Interfaces are configured to not forward telegrams on main line 14 and/or 15. But we're using 1577/255 for communication...

This is my IP Router configuration:

Bildschirmfoto vom 2016-04-11 20-43-28.png

It's german, but the option "Hauptlinine 14 / 15 Gruppentelegramme: alles weiterleiten" means:

"Mainline 14/15 group telegrams: forward all"

Hmm, *thinking* forget it... You're using an IP Interface. And according to the manual, there's no such configuration for IP Interface... damn.

Hmm...

The suite is sending data, ETS does log those telegrams, device is in prog-mode, but is not receiving any data... and therefore not replying with a telegram....very strange.

Have to think about it...

[fluppie]

I checked ETS5, I have no parameters like that, only DHCP on/off and a setting for the http port 80 / 8080.

EDIT: I'm wondering if it would be handy to have a "test sketch" who sends a 1 or 0 to a group address let say every 10s. Everything hardcoded, just to make sure if the serial communication Arduino to BCU is working.