Spacelynk Communication

[Kais_Aljundi]

Hello Team

  I have a site with 10 spacelynks connected to building network, 4 of these units having kind of communication issue, means, if a group address is activated in spacelynk-1, we can see the same group address is activated in spacelynk-2, but it will not activate the circuits/Channels located under this group address.

Example: - (Motion sensor is connected with Spacelynk-1 but the Switch actuator is connected to spacelynk-2 , both in same group address, so if the motion sensor is activated in SL-1 , same Group address is activated in both Units, but the Switch actuator will not be affected by the command in SL-2) 

the issue is in 4 out of 10 units, the command from the (working units) will reach to all other units (including the ones with issues) and will normally activate the Group address and the command, but the command from the faulty units, will reach the other units but without activating commands/swith..etc.

what might be the issue? and how we can solve it?

sorry for the long discerption & thanks in advance

Kais

[Erwin-vd-Zwart]

@Kais_Aljundi Can you post screenshot(s) from the KNX settings on the SL's that are not working according to you? Also attach screenshots from the filters settings IP -> local and local -> IP.

Also post a screenshot of the objects in both SL's that are shared between them..

Also what happens if you manually change an object in a SL that is not activating the switch channel?

At this moment i get the feeling the KNX Mode is not set to TPUART on the failing ones, or the shared object is not present in one of the SL's..

[Kais_Aljundi]

Thanks @Erwin-vd-Zwart 
Please find attached screenshots.
also find a screenshot from ETS,  spacelynks I have issues with are not discovered, I have connected my laptop directly to one of them and it was directly discovered, where now I feel that Port 3671 is not activated for these Units!!
what do you think?

Thanks

[Erwin-vd-Zwart]

@Kais_Aljundi 

They are in a private IP range so 3671 should be not blocked from the controller side, but you said that the change from SL1 is visible in the object view of SL2 so this means it received the telegram, or did i understood this wrong?

[Kais_Aljundi]

HI @Erwin-vd-Zwart 
NO, you got it right.... change is showing but not activating the commands

[Erwin-vd-Zwart]

@Kais_Aljundi  Did you ETS monitor the TP side of this second SL? Best is to connect a USB direct to the TP side and send a command from the other SL, it should be transmitted to the TP when it is set to TPUART and filters are allowing it.. What happens if you set the object manually in this SL, does it activate the actuator in that case?

[Kais_Aljundi]

Dear @Erwin-vd-Zwart 

 after re-checking , I have noticed that the SL with issues are NOT receiving command telegrams from other SL (so any change in another SL is not received), But all commands done in SL (with issue) will reach other SL and Act normally.

Sorry for the wrong info given before.

[Erwin-vd-Zwart]

Do you have multiple routers in the setup? If yes you could try to increase the TTL setting that is default 1 to the amount of routers it needs to pass, TTL is reduced by 1 at each router it passes so make sure it's high enough.

[Cristiano_Carli_Ballola]

@Kais_Aljundi according to their individual addresses, your SL are setted as backbone coupler.
So are there Line Couplers installed under each SL?
Have you checked that the Line Coupler filter tables contain the group addresses that activate the electrical utilities affected by the issue?
Another thing: I assume that the various SLs are connected to different IP switches.
You should verify that all switches are enabled for multicast communications.
You can verify the communication with ETS, by connecting your PC to the switch to which a SL that "does not communicate" is connected and enabling group monitor to connect to 224.0.23.12

[Kais_Aljundi]

Hi @Cristiano_Carli_Ballola 

Thanks for replay
yes, there are couplers for each Line under SL.

and yes, SLs are connected to different switches.

I have connected my laptop directly to SL (with issue) and its showing in ETS normally ( Not showing when connected through Building network ).
So I have dropped a request to IT team to check the multicast & port 3671 for the effected SLs.