SL & W4K bacnet app very slow

[domotiqa]

Hello,
we have 18 area with fancoil bacnet IP with 5 points each to link to KNX.

Every time we try to map a knx adress to an bacnet point it takes 30sec to 60 sec to link it.
I had this issue in the past too on majority of bacnet ip device.

The bad too is that sometimes it fail:
Device with ID = 4002 or its object with ID = 28_5 doesn't exist

Then try again one or two times and then it work....

so 15*5points* 2 times * 1 minute = 150 minute only to link

any idea how to make it faster ? link by script (read/write), update app...

[Thomas_Rohde]

Hello Domotiqa,

can you please share more details related to your used device and software status please?
Do you phase the same problems with a W4K as well as with a SL?
Which FW-Version you are using and which version of the App you have installed?

[domotiqa]

20210218 client

Spacelynk LSS100200 V2.8.3

As far as I remember, the mapping process was "always" such a pain (at least my 10 last project use).

But in general it s only some point I need.

This time I needed more point and it s horrible. Sometimes I nedd to put the buttun 10 times (error object don't exist) before a press that work and then long delay between 20s to 2 min max...

Sometimes also the discovering don't show all object, need to refresh.

Thks for help

[Thomas_Rohde]

Hello Domotiqa,

I am very sorry but your topic disapeard from my radar. Sorry!
Did you managed in between or is it still open?

[Neskettani]

Hello @domotiqa have you found a solution to your problem? 

[domotiqa · Accepted solution]

no. But for next time, someone on a known forum create a script to auto map.

But no, the app should need more stability I guess

[domotiqa]

in the past i success adding a bacnet exporer in a new tab of the scada main. would be great , so this way we can add a script. because bacnet client is such a pain on each project.... and as explain the old bacnet client integrate in scada main was very quick

[Thomas_Rohde]

Hi Domotiqa!

Is the Spacelogic KNX BACnet Gateway (LSS100300) not suitable for you?

[domotiqa]

maybe but always hard to sell more product to the customer.

For example another example. here we have a party building for a city in france. All knx+dali+modbus. and 3 HVAC ventilation Thereco (SE as-p each). They give us the bacnet datatable. we can scan devices but someone we need to scan 2,3 or 4 time to see all variable. And it is very time consumming.

After we need to link the bacnet point to knx. I need to press the save buton so many times to link it !! and there is a huuuuuuge delay between each press.

If i use script to map the variable it is very quick (but less easy)... also the scan with the old tabs bacnet was very quick !

Can't you improve it (maybe keep latest point discovererd and add a buton full scan again...) ?

Because once it is mapped no problem it works well..

[domotiqa]

also can i have the bacnet lua package ?

[Erwin-vd-Zwart]

@domotiqa 

If you have 3 AS-P’s then why do you make the Wiser the client?

You should make it server and use the AS-P as client and make the mapping / bindings in the AS-P side, this is how it’s designed by us.

The BACnet client app is designed for residential so you can onboard a heat pump or airco for example with a total max of 50 points.

The client app is not meant for full HVAC integration on a small building with a higher amount of devices as that slows down the discovery process big time as you now experience..

[Erwin-vd-Zwart]

No, we don’t distribute separate packages, supported features are in the FW or included in our Apps.  

All other available packages are unsupported and not publicly shared.

[domotiqa]

On most integration, it don't work like that ! Peiople for these kind of Hvac come when they want, put their product, enable BMS communication and leave. Spacelynk is using as server when it is EBO that need KNX point. On building <5000m2, speclynk feat well...

but the bacnet client is a pain ... you say it is for residential only... even on it it is sooo long to use.

Really don't understand why your discover process is so long !!! I ask you why when using the old bacnet tab in scada-main, it is so quick !! Also when mapping with script it is so quick too...

So please, after many message on bacnet client problem,  answer why it is not possible to improve it and make it more quick and stable... Maybe add option to scan/discover new object, but keep in meme the last object discovered....

In this forum, lots of time people explain how to bypass the problem we have on multiple product, despite of fixing our problem.

I have a list from multiple years of problem, change, bug... never fixed. 

So please, help Integrator that use SE product since years and are in pain with problem

[domotiqa]

SE blocked so many function usefull in LM product (package install, bacnet ipk, zerotier....). you should make a warning to enbale advanced feature instead of restiction for your installer