Willkommen im Loxone Community Forum. Um alle Funktionen nutzen und sehen zu können, registriere dich bitte zuerst. Dies gilt auch für das herunterladen von Dateien.
I've been busy trying to configure a KNX device via the Loxone miniserver but not succeeded in it yet. I've got an error: "The application program cannot be loaded into this device (a required property, eg. PortADDR, has a wrong value". What could be the cause of this problem and how can you debug this setup?
Did it ever work before?? You mentioned no KNX Powersupply....do you have one????
There are some users (me included) where programming via Loxone is not working (anymore). The first months it worked without problems. Start the group monitor in the ETS. Can you see the normal packages on the bus if you press a button?? Start programming...do you see yellow line inbetween?...these are Errors. To many errors will stop the procedure of programming.
I bougt a USB programming device for the ETS... no problems anymore and the process of programming is now MUCH quicker.
Dear It's a new setup containing the MaxInBox66, a KNX power supply off course (without power supply you can't do anything). Programming the individual address succeeds. I can find the device using the loxone config tool (search EIB device). I can't see any packets on the KNX bus via the group monitor but none of the KNX devices is programmed so it's normal that I can't see anything. However if I do a scan, I can see the device to send an KNX-EIB A ACK. I've added once a zennio lumento X4 device. This device programs successfully. The MaxInBox66 device still fails (see attachment) Best regards Pieter
Sorry for the question with the power supply...Sometimes it is so easy
I found your error in a german forum. Here it was a wrong application program (wrong hardware or software revision/ labelling/ wrong actor chosen).
Did you update your ETS?
Thanks for the replies. Due to the reply of Nobbi75, I've seen that my supplier has given me module Maxinbox FC 0-10V FAN instead of Maxinbox66. This module looks identical but isn't identical!
Wir verarbeiten personenbezogene Daten über Nutzer unserer Website mithilfe von Cookies und anderen Technologien, um unsere Dienste bereitzustellen, Werbung zu personalisieren und Websiteaktivitäten zu analysieren. Wir können bestimmte Informationen über unsere Nutzer mit unseren Werbe- und Analysepartnern teilen. Weitere Einzelheiten finden Sie in unserer Datenschutzrichtlinie.
Wenn Sie unten auf "Einverstanden" klicken, stimmen Sie unserer Datenschutzrichtlinie und unseren Datenverarbeitungs- und Cookie-Praktiken wie dort beschrieben zu. Sie erkennen außerdem an, dass dieses Forum möglicherweise außerhalb Ihres Landes gehostet wird und Sie der Erhebung, Speicherung und Verarbeitung Ihrer Daten in dem Land, in dem dieses Forum gehostet wird, zustimmen.
Kommentar