Wiser bacnet server enabled, but no objects showing on the bacnet side
SpaceLogic KNX Forum
Schneider Electric SpaceLogic KNX forum to get support and share knowledge including selection, installation and troubleshooting for spaceLYnk, Wiser for KNX, eConfigure KNX, SpaceLogic KNX Hybrid module and other topics.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
2025-02-2003:12 AM
Wiser bacnet server enabled, but no objects showing on the bacnet side
Hello!
I have a Wiser for knx HW 1 with SW 3.0.0 and want to expose some KNX adresses (room occupied on/off) to bacnet (Siemens DXR2.E18 roomcontroller).
I tick "export" for the KNX adresses, enable the bacnet server and start YABE to monitor the bacnet objects, but nothing is showing (not even finding the Wiser as a unit on the bacnet network). If I start wireshark with a bacnet filter, and then run "Send whois" from YABE, I see my computer sending the whois and the Wiser is responding "i i´m devide id", so it seems the bacnet server on the wiser is up and running, but no unit or objects is seen in YABE.
If i start the "demo server" or "bacnet room simulator", both installed with YABE, those objects is showing up in YABE.
If I open the "Bacnet object" on the Wiser, I see them there, but not on the bacnet side.
Link copied. Please paste this link to share this article on your social media post.
2025-02-2004:26 AM
Solved: As stated above, ineed the server was up and running, but windows firewall prevented the telegrams from reaching the YABE bacnet browser. The example program was running locally, bypassing the firewall. As soon as the wirewall was disabled both the Wiser and the objects turned up in YABE.