Hello Forum Users,
i have a strange problem with a Spacelynk on a customers site.
The device is running there since 2 years and worked fine all the time (HW is 2.0, FW was 2.3 all the time).
But since last week, there is the problem, that the device is restarting itself every 5 to 90 minutes.
When i look into the system massages, i can see the restarts and the time there.
There are a lot of trends recorded in the device and with any restart the data for the last periode is lost.
The device itself stands in no direct relationship with other ethernet participants and all the data is comming from the KNX connection itself.
The ethernet is only connectet, that the customer can view the visualisation and the trends on the device.
Looking at trends or the visualisation from an other device stands in no direct relationship with the restarts.
What i did was upgrading the firmware to 2.5 with no effect.
I changes the device to a Homelynk (HW 3.1 FW 2.5) with the same effect, still restarting, so i installed the old Spacelynk again.
Then i disconnected the ethernet cable over the night an in the morning there were no restarts in the systemlog, the device was running all the night long.
After connecting the ethernet again, there was the first restart after 20 minutes.
So the problem is, that something comming from the ethernet causes the device to quit its job and resart.
What could that be?
The customers site is a factory with hundreds of ethernet participants.
The only indication i have, is the "Error counter" on the system page for the network connection (see picture attached).
This counter runs up to values over 27000 and i guess this could stand in relationship with the restarts.
I believe that there was some kind of modification in the customers network (a new device connected for example ...),
causing special traffic on the ethernet which can not be handled by Spacelynk.
I am standing in close contact to the customers network administration but they do also not know what could have happened since last week.
Has anyone had a mailfunction like this bevore or does anyone have an idea, what to do to solve the problem?
I thought about using special Software like "Wireshark" to look inside the ethernet traffic but i am not sure if i could interpret well, what i would see there.
Thanks and kind regards
Michael
i have a strange problem with a Spacelynk on a customers site.
The device is running there since 2 years and worked fine all the time (HW is 2.0, FW was 2.3 all the time).
But since last week, there is the problem, that the device is restarting itself every 5 to 90 minutes.
When i look into the system massages, i can see the restarts and the time there.
There are a lot of trends recorded in the device and with any restart the data for the last periode is lost.
The device itself stands in no direct relationship with other ethernet participants and all the data is comming from the KNX connection itself.
The ethernet is only connectet, that the customer can view the visualisation and the trends on the device.
Looking at trends or the visualisation from an other device stands in no direct relationship with the restarts.
What i did was upgrading the firmware to 2.5 with no effect.
I changes the device to a Homelynk (HW 3.1 FW 2.5) with the same effect, still restarting, so i installed the old Spacelynk again.
Then i disconnected the ethernet cable over the night an in the morning there were no restarts in the systemlog, the device was running all the night long.
After connecting the ethernet again, there was the first restart after 20 minutes.
So the problem is, that something comming from the ethernet causes the device to quit its job and resart.
What could that be?
The customers site is a factory with hundreds of ethernet participants.
The only indication i have, is the "Error counter" on the system page for the network connection (see picture attached).
This counter runs up to values over 27000 and i guess this could stand in relationship with the restarts.
I believe that there was some kind of modification in the customers network (a new device connected for example ...),
causing special traffic on the ethernet which can not be handled by Spacelynk.
I am standing in close contact to the customers network administration but they do also not know what could have happened since last week.
Has anyone had a mailfunction like this bevore or does anyone have an idea, what to do to solve the problem?
I thought about using special Software like "Wireshark" to look inside the ethernet traffic but i am not sure if i could interpret well, what i would see there.
Thanks and kind regards
Michael