I have setup a new NetBotz 750 system, a few sensor POD is showing device ID 88.
I have seen this number when the system is starting up, or when it updates the firmware.
The NetBotz is showing the following alarms:
I have noticed that I have to sensor pod with ID 1.
What can be the problem?
The NetBotz 750 A-link communication is built up as the picture shows.
The NetBotz 750 has two A-link connection when the first time I have started the systems I have connected one by one the sensor pods. The sensor pods received the ID numbers. POD 1- POD 6
I have started to connect the A-link cable to the secund A-link port on the NetBotz 750. The POD is getting the ID 1 another ID 88 and then ID 88.
The NetBotz 750 shows error message which was attached in my previous post.
This way can handle the NetBotz 750 the A-link cable and the sensor pods?
Have you tried using 24v power supplies on every 4th sensor pod as you might have overloaded the A Link Bus ?? This has solved promblems like this for me before.
Try connecting them to only 1 port on the 750 and see if this works as you can cascade up to 12 sensor pod 150's
I have started with the pod number 1 and then followed by pod 2 end so on. I extend with 24v power supply every 3th sensor pod, which I connect after I have connected the A-link cable.
Everything was working well. When I have connected the pod 6 this pod has got the ID number 1. I have tried to work with the second A-link line which was started from the other A-link port from the NetBotz 750. In this line the first pod was getting the ID 1. In this point this was the third pod with ID number 1. If you look my previously attached picture the pod 1 ID has pod 1, pod 6, pod 7. Pod 8-10 is getting the 88 ID number.
The Netbotz 750 shows alarm (see my starting post)
I have reset the device and configured the IP parameters. The NetBotz has still alarms. I have updated the firmware, now it runs on 5.2.3 version.
It doesn’t recognize the sensor pod. I have deleted them before the reset.
Question, when I have deleted a sensor pod than can the NetBotz 750 recognize them again?
What can be the problem with this NetBotz 750 system?
It might be no harm to log a ticket with your local support team, this might require some bus level debugging.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!