I've been using a temporary JUNG IPS 100 REG IP interface on bOS, and it was working fine.
But I had to change that temporary IP interface for a BAOS 771 from WEINZIERL.
As you may know, BAOS actually let's you use IP tunneling for programming / visualization, and also to use it as Bus Access Object Server, for prototyping, third party integration etc.
As soon as I started using the BAOS with bOS, I've noticed that bOS is extremely slow reading / writing.
In fact, when the KNX connection becomes true, bOS tries to read every feedback and it shows "No response to read from..." in every address. While this happens, I can see on ETS bOS trying to read the feedbacks almost with a 2 to 3 second delay between them.
If I run a scene for example, it tries to execute the scene at the same very slow speed, 2 to 3 seconds in every group address of the scene.
If using the BAOS on ETS for programming, it works at a "regular" read / write speed.
If using the BAOS with the internal DPT server, it works fast at reading / writing.
If I use it on bOS and click in two or three lights very quick for example, it turns the first one, 2 to 3 seconds and turns the next one, and so one.
I know that BAOS 771 is "old" and with a 10BaseT ethernet connection, but it's a very strange behavior.
Ant tips on that?
Customer support service by UserEcho