-
Sorry, but it's not possible to reproduce/diagnose the problem based on this description. You may also want to try Calimero NG- it has quite some improvements over 1.x!
Regards, Georg.
2009-10-19 13:24:36 UTC in Calimero
-
Hello,
You mean the "EIB session file" that is created via "File" > "Extract Data (e.g. OPC)..." > "Export to OPC Server" in ETS3, whose 3rd column says things like "Uncertain (2 Byte)", right? If so, this is a tool-specific issue and definitely not covered by the KNX specification. Maybe support@knx.org can help?
Georg.
2009-10-09 14:55:18 UTC in Calimero
-
Matteo,
You're welcome.
The PropClient tool is intended as an example to display the capabilities and usage of the Calimero library, not as a reference implementation of the KNX standard. That is why there are more service invocations than strictly necessary: The property value is not printed after the first PropertyValue\_Response is received, but only after an additional...
2009-10-09 11:10:20 UTC in Calimero
-
> Excuse me for my not perfect English.
No problem, it's just that I cannot answer those parts of your questions that I do not understand.
> if I want to read a property of an application interface object in a device, the sequence of messages exchanged is
... the following, as I said in my first post:
1. Client sends TUNNELLING\_REQUEST (cEMI L\_Data.req...
2009-10-09 08:38:55 UTC in Calimero
-
> There are time limits for responses
> from shrinking?
Sorry, I do not understand.
> Once you receive the message TUNNELLINGREQUEST (CEMI LData.ind: APropertyValueResponse-PDU), the client should print on screen the result of the request, right?
The PropClient tool actually sends two *A_PropertyValue_Read* requests, plus a *A_PropertyDescription_Read* inbetween. Apparently...
2009-10-05 13:58:53 UTC in Calimero
-
Assuming a connectionless(!) *A_PropertyValue_Read*, the remaining messages are (leaving the Tunnelling connection open):
Server sends TUNNELLING_ACK
Server sends TUNNELLING_REQUEST (cEMI L_Data.con: A_PropertyValue_Read-PDU)
Client sends TUNNELLING_ACK
Server sends TUNNELLING_REQUEST (cEMI L_Data.ind: A_PropertyValue_Response-PDU)
Client sends TUNNELLING_ACK
HTH...
2009-10-02 18:09:40 UTC in Calimero
-
Probably, you want to use a "step code" of 1 (i.e., "increase 1")- that's what most (if not all) push buttons send. The "step code" denotes the fraction (!) of the dimming range the actuator should sweep (until stopped by a "break").
Also, this would be a CommandDP (not a StateDP, since there is no state you could possibly read back from this group...
2009-08-24 07:56:43 UTC in Calimero
-
Also, this may help: http://knxnetipdissect.sourceforge.net.
2009-08-20 14:03:08 UTC in Calimero
-
This is mainly a firewall/switch setup issue- depending on how your network is configured (and the security requirements you have!), a VPN may be useful/necessary.
KNXnet/IP Tunnelling uses IP unicast (UDP in all cases known to me), the default port number is 3671; originally, it did not support NAT natively (and many devices still do not), since the IP address is/was included in the...
2009-08-20 13:51:03 UTC in Calimero
-
Houssem,
On KNX/EIB, datapoint values are "pushed" via GroupValue_Write or can be "pulled" via GroupValue_Read, depending on the configuration of the devices in the network. In Calimero, the ProcessCommunicator provides the easiest access to these services. The ProcComm "tool" actually is a code example for this API.
HTH, Georg.
2009-08-20 13:30:39 UTC in Calimero
