Problem with send message from c-bus to knx

[m.j.sorokin]

I use Bus translator configurator V1.0.1.0
for testing knx commands i used ETS4 and Logic Machine 5
From web interface logic machine i set value for group witch send from knx to c-bus its work fine.
But when i try change value c-bus group from toolkit its dont translate to knx.
Configuration witch download from cbus knx transator in attachment. 


In broshure (https://www.cytech.biz/download_files.php?item_id=296) says that device can translate Aircondition cbus aplication, how i can translate data from cbus thermostat, witch dont have address for each parametrs but have address communication group?

[m.j.sorokin]

On the knx module (PC01-035B) on the other side there is no element С108. Is it Ok?

[slychiu]

Do you mean that you cannot send any cbus commands to KNX, or are you referring to the Airconditioning Application only?
In fact there is an error in the brochure. The Cbus airconditioning application is not supported directly, as there is not a KNX type that can receive all the airconditioning application commands so it is not possible to directly convert to KNX
I understand that you can change the application to Lighting using Cbus toolkit

What do you want to achieve

Do not worry about C108

[m.j.sorokin]

Thanks for the answer. These are two different issues. Regarding the thermostats everything is clear.
The main problem is that group addresses of c-bus not transferred to the knx network. 
I tried to translate group adress from diferent aplication (standart light aplication 56, and custom alication 70). 
I tried to change the values of group addresses from the toolkit software and through key switches, but the changes dont transmit to knx...
I also tried to use the \"learn\" function, the device receives the correct addressing of c-bus aplication and group address. 

[admin]

Your test_ctrl file only has custom application 70 in Cbus to KNX
Forget about custom application for now. Just try a Lighting application, select a Cbus group address and map to a KNX lighting group address
This should definately work

[m.j.sorokin]

i test that variant, it\'s dont work... in attachment last tested config.

[admin]

Please check the state of the diagnostic leds on the module below. This should give an idea what is wrong. perhaps a power supply issue on the cbus or KNX side

• D4 \"RDY\" (Green) - Indicates Power On.
• D5 \"IN0\" (Red) - Blinks when CBUS telegram is received from CBUS.
• D6 \"OUT0\" (Red) - Blinks when CBUS telegram is sent to CBUS. Remains on  when no acknowledgment is received from CBUS after outgoing telegram.
• D7 \"ERR0\" (Red) - Steady when CBUS is not connected or CBUS power supply is not on, or when the CBUS interface is not initialised or has an initialisation error. D7 flashes continuously when the EEPROM is blank, ie unprogrammed. Both D7 and D10 both flash continuously if the U2 EEPROM is not present.
• D8 \"IN1\" (Red) - Blinks when KNX telegram is received from KNX.
• D9 \"OUT1\" (Red) - Blinks when KNX telegram is sent to KNX. Steady when no acknowledgment is received from CBUS after outgoing telegram.
• D10 \"ERR1\" (Red) - Steady when KNX is not connected or KNX power supply is not on, or when the KNX interface is not initialised or has an initialisation error. Both D7 and D10 both flash continuously if the U2 EEPROM is not present.
• D11 (Green) - blinks when data is received from the USB Port.
• D12 (Red) - blinks when data is sent to the USB Port.
• LD1 (Red) on CBUS Submodule. On when Burden is enabled
• LD2 (Red) on CBUS Submodule. ON Steady when idle, Blinks during CBUS communication.
• LD3 (Green) on CBUS Submodule. OFF when Network Voltage is low or Clock is not present. ON Steady when Voltage and Clock are present. Flashing when  Bus Voltage is marginal (15-20V)

[m.j.sorokin]

D4 \"RDY\" (Green) - Always ON     //Indicates Power On.
D5 \"IN0\" (Red) - Blink when send data from c-bus network     //Blinks when CBUS telegram is received from
CBUS.
D6 \"OUT0\" (Red) - Blink when send data from c-bus network     //Blinks when CBUS telegram is sent to CBUS. Remains on  when no acknowledgment is received from CBUS after outgoing telegram.
D7 \"ERR0\" (Red) - Steady when CBUS is not connected or CBUS power supply is not on, or when the CBUS interface is not initialised or has an initialisation error. D7 flashes continuously when the EEPROM is blank, ie unprogrammed. Both D7 and D10 both flash continuously if the U2 EEPROM is not present.
D8 \"IN1\" (Red) - Blink when send data from c-bus network     //Blinks when KNX telegram is received from KNX.
D9 \"OUT1\" (Red) - Blinks when KNX telegram is sent to KNX. Steady when no acknowledgment is received from CBUS after outgoing telegram.D10 \"ERR1\" (Red) - Steady when KNX is not connected or KNX power supply is not on, or when the KNX interface is not initialised or has an initialisation error. Both D7 and D10 both flash continuously if the U2 EEPROM is not present.
D11 (Green) - blinks when data is received from the USB Port.
D12 (Red) - Blink when send data from c-bus and KNX networks     //blinks when data is sent to the USB Port.
LD1 (Red) - Always ON (but burden on this module is off)     // on CBUS Submodule. On when Burden is enabled
LD2 (Red) - Always ON, Blink when send data from c-bus network    //on CBUS Submodule. ON Steady when idle, Blinks during CBUS communication.
LD3 (Green) - OFF (but clock ON on this module, and network voltage via toolkit network diagnostic 30,1V)     //on CBUS Submodule. OFF when Network Voltage is low or Clock is not present. ON Steady when Voltage and Clock are present. Flashing when  Bus Voltage is marginal (15-20V)

[m.j.sorokin]

I test only liting aplication, i delete in config group address from another application. It worked! but how to be with other applications?

[slychiu]

Zones, Lighting, Security, Clocks and Timekeeping, Trigger applications are supported directly by Cbus to KNX. Custom, applications  may also be used depending on what they are
However you have entered Application 70 and 71. These are not known applications in Cbus. There are no such applications so they may be causing problems in Cbus
Note that the application numbers are in Decimal in Cbus to KNX for example Lighting application is 56 in decimal

application 70 is $46, and 71 is $47 are not defined

Which applications are you trying to use?