NXB KNX problem
Panem
Posts: 10
Hello,
I replaced comm-tec gateways with one NXB KNX using lKNX_value[3000] and AMX_KNX_updater.tko but even though i can control shutters and lights I don't get feedback from thermostats and boilers.. the problem is that the when i compile the program with the .tko file after the download the controller never gets back online so I connect directly through RS232 but then after the download.. the virtual devices are not created... so I do not include the .tko and the program works...BUT without feedback. I saw that the memory of the controller is ok (NI-2000) and the buffers too.
Is there anyone else that has problems with this .tko file?
Any suggestions?? The project has to be finished until Friday... I hope not to return back to the comm-tec gateways...there must be a way....
Thank you.
I replaced comm-tec gateways with one NXB KNX using lKNX_value[3000] and AMX_KNX_updater.tko but even though i can control shutters and lights I don't get feedback from thermostats and boilers.. the problem is that the when i compile the program with the .tko file after the download the controller never gets back online so I connect directly through RS232 but then after the download.. the virtual devices are not created... so I do not include the .tko and the program works...BUT without feedback. I saw that the memory of the controller is ok (NI-2000) and the buffers too.
Is there anyone else that has problems with this .tko file?
Any suggestions?? The project has to be finished until Friday... I hope not to return back to the comm-tec gateways...there must be a way....
Thank you.
0
Comments
For the NXB-KNX no virtual devices are required. Differently to the Comm-Tec solution, there is no module to interact between your program and the gateway in general, all commands go directly to the gateway. The KNX_updater module just receives the value feedbacks from the gateway and fill them into the Long Array, so that it will work similar to the Comm-Tec EIB version 6 solution.
The gateway itself is a regulat bus device for the master, and so it gets a device address in the range <32000.
I compiled and downloaded the original files to a NI3100 (no 3000 on hand). There is not much memory used with that lKNX_value[3000] array against an empty NI3100, so I don't think that there would be a memory problem.
With the updater module in code, please try to get connect to the NI by serial terminal, and do a SHOW LOG ALL, SHOW MEM and SHOW DEVICE, and save the information to a txt file and post it. You may also send the txt file to support@amx.de to my attention, and I will have a look to it.
Today had some problems with handling NXB-KNX Gate channel events. So I got this 2 actors, which are completely same, from one actor I get channel and level messages ( i guess string is somewhere upper than part of screen that I capturded ), and from another actor I get only 'VAL'-string. Pic related.
Problem seems not so big, cause I always can use virtual device linked to lKNX_Array[], or use STRING event, but come on! Why it works perfectly on one actor, and can't on another?
Spent a lot of time remaking my sweat and nice CHANNEL_EVENT to DATA_EVENT with a lot of parcing
The 'VAL' indicates that the group address has only sent an Update of its value, but there was no change of the value.
'SET' and 'VAL' are close to the KNX datagrams, which differ between a value change and a value update.
The channel/level way is close to the NetLinx handling, which means that only changes will create an Event.
Best example may be a temperature sensor. It will be programmed to send a temperature change (of course), and so at the moment the temperature is going up or down, a level_event and a SET response is created (note that a channel event is only created if the change is to or from 0 to/from an value >0).
But it may also be required, for whatever reason within the KNX environment, that the temperature sensor is also sending its value e.g. each minute, altough there was no change. This will not create new channel or level events (because the value has not really changed), but is notified by the 'VAL' response.
Similar with the POLL and GET functions. If e.g. the channel for an address is on, you do a POLL and the value of the address is >0, you will not get a channel event and no SET response, but only a VAL.