Making first setup work ...

[tuxedo]

Trapped in a beta2 bug... close the suite and open the affected XML with an texteditor like notepad++. Remove the <configuration> and all of its childs, save and try again with the suite.

If that does not solve your problem, please provide the .kdevice.xml so that I can debug in the IDE.

btw: pls. report bugs here:

https://github.com/KONNEKTING/KonnektingSuite/issues
https://github.com/KONNEKTING/Konnek...Library/issues

[fluppie]

OK. Is there a quick-start guide available? How to configure your first device after uploading the .ino sketch. I think I'm using the Suite wrong. The group monitor works, so it connects succesfully to my KNX bus.
https://www.youtube.com/watch?v=iYpo5rwjAFs this is what I get after connecting the Arduino Nano v3 (http://www.gravitech.us/arna30wiatp.html) only flickering rx/tx lights.

[Eugenius]

Hello fluppie,

Is that china clone Aruino Nano with ch340g chip on the bottom?

[fluppie]

No it's using a FT232RL http://s29.postimg.org/4kji6cbwn/IMG_8312.jpg
It could be a fake FT232RL, but I guess they should work just fine?

[tuxedo]

Your wiring is correct.

The "L" LED is flickering... This is typically connected to PIN13.

My current assumption:

Your sketch uses PIN13 / L LED as Programming-LED, but you don't have a prog-button connected. So your button-input pin has no determined level (high/low) and is toggling very fast. The sketch is then switching very fast the programing-state and switch on/off the prog-led.

Connect your prog-button-pin with 1k or 10k resistor to ground and with a button to +5V. If button is not pressed, level is tied to GND. If button is pressed, level is at 5V.

Another important hint:
We are using SoftwareSerial to have debug output. You need a separate UART-to-USB adapter to attach this. I'm using this one:
http://www.ebay.de/itm/1Stk-USB-2-0-...IAAOSwqu9VGQeR

But every other would do it as well.

Maybe post your sketch so that we can have a look at?

Regarding "quick-start guide":

No, there's no quick-start guide yet. In short: connect BCU, connect Prog-LED and Prog-Button, apply example sketch, load example XML into suite, press Prog-button and program your device.

[fluppie]

Okay thanks, I have a CP2102 adapter at home . Resistors/breadboard/... also no prob.
I use the default Temp/RH sketch without modifications. I'll try again tonight

Can you explane wat the "parken" button does. Or what does "parken" mean in English? Is it program group address? Is the suite prepared for multi language? I could assist for a translation file in English and/or Nederlands.

[fluppie]

[Programmieren] Programmiere: 1.1.100 Temp RH test Phil
[Programmieren] Initialize...
[Programmieren] Reading commobjects...
[Programmieren] Reading parameters...
[Programmieren] Fortschritt: 1/20
[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(ProgramDia log.java:172)
at java.lang.Thread.run(Thread.java:745)
at de.konnekting.suite.BackgroundTask$1.run(Backgroun dTask.java:59)
Caused by: de.root1.slicknx.KnxException: Can not set address. no device in prog mode
at de.konnekting.mgnt.protocol0x00.ProgProtocol0x00.w riteIndividualAddress(ProgProtocol0x00.java:358)
at de.konnekting.mgnt.KonnektingManagement.writeIndiv idualAddress(KonnektingManagement.java:72)
at de.konnekting.deviceconfig.Program.program(Program .java:103)
... 3 more

[Programmieren] Fertig! Dauer: 24859ms[/]

[tuxedo]

Hey,

Can you explane wat the "parken" button does.

In english, it would be "parking". It's dropping the right most part of the individual address/physical address (not the group address), like in ETS. The IA/PA is then no longer "complete" and the device is "parked" -> not active/not ready for programming.

Programming the IA/PA is done by using the "red led button" in the toolbar.

Is the suite prepared for multi language?

In principle yes. Translating to english is not a problem. But each text must be first linked into a language file.
I think it would be best to have this with the next release --> beta3... but it takes a while.

Another important point of the suite:

The KONNEKTING Device lib runs - currently - in debug mode. This affects timing in the sketch. Therefore the suite must also run in debug mode (see two batch files for starting the suite). Otherwise programming will not be possible.
When sending/posting logs, keep an eye on the log files created in the suite folder. the ".log.0" is always the latest and contains lot more information than the console in the suite itself.

[fluppie]

Did connect a 10k resistor from D3 / pin 3 to ground and then a pushbutton in between 5V and D3.
LED pin = 13 = Arduino nano V3 onboard led
Prog button pin = 3

Softserial output:

Setup KnxTools
createProgComObject
Manufacturer: DEADhex
Device: 1hex
Revision: 0hex
numberOfCommObjects: 7
_deviceFlags: 11111111bin
Using FACTORY
IA: 0x11FE
KnxDevice startup status: 0x2
Knx init ERROR. retry after reboot!!
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
software reset NOW




Setup KnxTools
createProgComObject
Manufacturer: DEADhex
Device: 1hex
Revision: 0hex
numberOfCommObjects: 7
_deviceFlags: 11111111bin
Using FACTORY
IA: 0x11FE
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0
KnxDevice startup status: 0x2
Knx init ERROR. retry after reboot!!
software reset NOW




Setup KnxTools
createProgComObject
Manufacturer: DEADhex
Device: 1hex
Revision: 0hex
numberOfCommObjects: 7
_deviceFlags: 11111111bin
Using FACTORY
IA: 0x11FE

Very weird that I get a 0 instantly after pressing the button. I'm unable to bring the device in programming mode. What should happen to the led? Should it blink or should it burn continously?

[Eugenius]

KnxDevice startup status: 0x2

means NO communictaion between Arduino and BCU

PROGBUTTON toggle
PROGBUTTON 1
PROGBUTTON toggle
PROGBUTTON 0

i have the same problem, if i make it on breadboard => https://www.arduino.cc/en/Tutorial/Debounce

Something like that works better (with capacitor):

[fluppie]

Hmmm, would there be something wrong with the BCU? How can one test the BCU on working correctly?

Is software debouncing a solution? http://www.instructables.com/id/Ardu...rupt-function/ or http://forum.arduino.cc/index.php?topic=45000.0

[Eugenius]

Have you ProMini or Leonardo/ProMico or another Arduino without USB-to-UART Chip on it?

Software solution... it would be possible, but not in your sketch...
You can try to modify lib: https://github.com/KONNEKTING/Konnek...Tools.cpp#L156

[fluppie]

I could try this one, behaves like a Arduino Lilypad USB: https://harizanov.com/wiki/wiki-home/funky-v3/

[Eugenius]

Yes, you can. You have to use D2 or D7 for ProgButton (D3 is not available)

[tuxedo]

Some background on why Eugenius recommends another board:

On Nano board, the RX/TX Pins are shared with the USB port. Especially with CH340G USB chip, we faced massive problems initializing the BCU. Once the CH340G has been "disconnected" from AVRs rx/tx pins, it works (programming is then possible via ICSP).

Now it seems that your Nano, which claims to use "original FTDI" has same or similar issues.
Either try to disconnect the AVR from FTDI chip, or use a AVR 32u4 board, which has a separate UART for this.

Regarding prog-button:

Technically, you can use any pin you want. But it must be interrupt-capable.

Regarding debounce:

on my breadboard, I don't use any capacitor. The bounce is not that problematic. Sometimes I just have to press the button a 2nd time.
Our boards use a debounce capacitor. That's the "safest way". software debounce would be possible, but is not yet done (why having additional code which consumes space and cpu (even if it's less) if a capacitor can do it as well).