Solve System Attentions : Nedap Livestock

Attention	Cause	Possible solution(s)
Other output busy	Wrong configuration	1. Check your behaviour component configuration. 2. Check wires on breaks, connection and possible corrosion.
Low current	Cable problem (poor contact or no connection)	1. Check wires on breaks, connection and possible corrosion. 2. Check the connector. 3. Check cables in the connector.
Input contact	A: Cable problem (poor contact or no connection) B: Nedap Feed Motor only: The motor does not respond to the given command	A 1. Check wires on breaks, connection and possible corrosion. 2. Check the connector. 3. Check cables in the connector. B For Nedap Feed Motor, check if there is too much or too little grease.
High current	Short circuit, overload or stuck.	1. Check wires on breaks, connection and possible corrosion. 2. Check cables in connector. Nedap Feed Motor: check if it is stuck
Motor configuration	Motor is incorrectly configured, inverse versus normal.	Nedap Feed Motor only: 1. Check configuration. 2. Check wiring, they might be the wrong way around.
Current off	The motor continues to draw current when it should be switched off.	1. Check configuration. 2. Check wiring.
Safeguard	Safeguard has intervened. Possible causes: long runtime, excessive total IO current, or motor driver error. It serves as an independent check if the main controller fails and responds more quickly to peak loads.	Nedap Feed Motor only: 1. Check if something is stuck. 2. Check the configuration of behaviour component.
Output busy	Output hasn't finished executing the previous command.	Check the configuration of behaviour component.
No half turn time	Not possible to calculate the half turn time. Interruption in communication, possibly due to a reboot.	1. Restart the V-pack. 2. Check wires on breaks, connection and possible corrosion. 3. Check the connector. 4. Check cables in connector. For Nedap Feed Motor, check if there is too much or too little grease.
Low current safeguard	Safeguard has intervened. The current is too low while motor is running. It could be a cable problem (poor contact or no connection).	1. Check wires on breaks, connection and possible corrosion. 2. Check the connector. 3. Check cables in the connector.
Cause unknown	An unknown error occurred that is not defined in the system.	Reboot the system. If problem persists, contact your dealer.
The current that was measured is too low	Cable problem (poor contact or no connection)	1. Check wires on breaks, connection and possible corrosion. 2. Check the connector. 3. Check cables in the connector.
The current that was measured is too high	Short circuit, overload or stuck.	1. Check wires on breaks, connection and possible corrosion. 2. Check cables in connector. Nedap Feed Motor: check if it is stuck.

Attention

Cause

Possible solution(s)

Other output busy

Wrong configuration

1. Check your behaviour component configuration.
2. Check wires on breaks, connection and possible corrosion.

Low current

Cable problem (poor contact or no connection)

1. Check wires on breaks, connection and possible corrosion.
2. Check the connector.
3. Check cables in the connector.

Input contact

A: Cable problem (poor contact or no connection)

B: Nedap Feed Motor only: The motor does not respond to the given command

1. Check wires on breaks, connection and possible corrosion.

2. Check the connector.

3. Check cables in the connector.

B
For Nedap Feed Motor, check if there is too much or too little grease.

High current

Short circuit, overload or stuck.

1. Check wires on breaks, connection and possible corrosion.
2. Check cables in connector.

Nedap Feed Motor: check if it is stuck

Motor configuration

Motor is incorrectly configured, inverse versus normal.

Nedap Feed Motor only:
1. Check configuration.
2. Check wiring, they might be the wrong way around.

Current off

The motor continues to draw current when it should be switched off.

1. Check configuration.
2. Check wiring.

Safeguard

Safeguard has intervened.

Possible causes: long runtime, excessive total IO current, or motor driver error.

It serves as an independent check if the main controller fails and responds more quickly to peak loads.

Nedap Feed Motor only:

1. Check if something is stuck.

2. Check the configuration of behaviour component.

Output busy

Output hasn't finished executing the previous command.

Check the configuration of behaviour component.

No half turn time

Not possible to calculate the half turn time. Interruption in communication, possibly due to a reboot.

1. Restart the V-pack.
2. Check wires on breaks, connection and possible corrosion.
3. Check the connector.
4. Check cables in connector.

For Nedap Feed Motor, check if there is too much or too little grease.

Low current safeguard

Safeguard has intervened. The current is too low while motor is running.

It could be a cable problem (poor contact or no connection).

1. Check wires on breaks, connection and possible corrosion.

2. Check the connector.

3. Check cables in the connector.

Cause unknown

An unknown error occurred that is not defined in the system.

Reboot the system. If problem persists, contact your dealer.

The current that was measured is too low

Cable problem (poor contact or no connection)

1. Check wires on breaks, connection and possible corrosion.

2. Check the connector.

3. Check cables in the connector.

The current that was measured is too high

Short circuit, overload or stuck.

1. Check wires on breaks, connection and possible corrosion.
2. Check cables in connector.

Nedap Feed Motor: check if it is stuck.

Attention	Cause	Possible solution(s)
Antenna disconnected or needs an adjustment (tuning)	Cable problem (poor contact or no connection). Tuning of the antenna is set incorrectly. There is interference of the antenna's signal.	Check wires on breaks, connection and possible corrosion. Check the connector. Check cables in the connector. Check the tuning of the antenna.
Antenna communication failure (check wiring)	Cable problem (poor contact or no connection).	Check wires on breaks, connection and possible corrosion. Check the connector. Check cables in the connector.

Attention

Cause

Possible solution(s)

Antenna disconnected or needs an adjustment (tuning)

Cable problem (poor contact or no connection).

Tuning of the antenna is set incorrectly.

There is interference of the antenna's signal.

Check wires on breaks, connection and possible corrosion.
Check the connector. Check cables in the connector.
Check the tuning of the antenna.

Antenna communication failure (check wiring)

Cable problem (poor contact or no connection).

Check wires on breaks, connection and possible corrosion.
Check the connector. Check cables in the connector.

Attention	Cause	Possible solution(s)
We are working on a proper explanation for you...	...	...

Attention

Cause

Possible solution(s)

We are working on a proper explanation for you...

...

Attention	Cause	Possible solution(s)
No connection	There is no connection or a bad connection between the VPU and one or more of the V-packs that are part of the setup of the system.	1. Check all cables, connectors and connections: - Inspect the cables for any damage. - Check for short circuits by touching wires. 2. Go to Maintenance > Monitoring> Behavior Comonent. Check if the correct V-pack is selected. 3. When using multiple V-packs/VPUs, ensure each V-pack has its a unique logic address. Go to Settings > Devices >V-packs. Change addresses if necessary. 4. When all above does not help, contact your dealer for possible replacement of the V-pack or VPU.
Unstable connection	There is no connection or a bad connection between the VPU and one or more of the V-packs that are part of the setup of the system.	1. Check all cables, connectors and connections: - Inspect the cables for any damage. - Check for short circuits by touching wires. 2. Go to Maintenance > Monitoring> Behavior Comonent. Check if the correct V-pack is selected. 3. When using multiple V-packs/VPUs, ensure each V-pack has its a unique logic address. Go to Settings > Devices >V-packs. Change addresses if necessary. 4. When all above does not help, contact your dealer for possible replacement of the V-pack or VPU.

Attention

Cause

Possible solution(s)

No connection

There is no connection or a bad connection between the VPU and one or more of the V-packs that are part of the setup of the system.

1. Check all cables, connectors and connections:
- Inspect the cables for any damage.
- Check for short circuits by touching wires.

2. Go to Maintenance > Monitoring> Behavior Comonent. Check if the correct V-pack is selected.

3. When using multiple V-packs/VPUs, ensure each V-pack has its a unique logic address. Go to Settings > Devices >V-packs. Change addresses if necessary.

4. When all above does not help, contact your dealer for possible replacement of the V-pack or VPU.

Unstable connection

There is no connection or a bad connection between the VPU and one or more of the V-packs that are part of the setup of the system.

1. Check all cables, connectors and connections:
- Inspect the cables for any damage.
- Check for short circuits by touching wires.

2. Go to Maintenance > Monitoring> Behavior Comonent. Check if the correct V-pack is selected.

3. When using multiple V-packs/VPUs, ensure each V-pack has its a unique logic address. Go to Settings > Devices >V-packs. Change addresses if necessary.
4. When all above does not help, contact your dealer for possible replacement of the V-pack or VPU.

Attention	Cause	Possible solution(s)
Channel 1 input voltage too high	- Power supply defective - The incoming voltage on the VPU (Vin 1) is too high. - The power supply that is used (possibly not from Nedap), delivers too much power.	Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.
Channel 1 input voltage too low	- Power supply too weak - Cabling too thin (<1.5 mm2) - Cabling too long	1. Check the wiring for Vin 1. 2. Reboot the system to check if the attention remains. If the attention remains: 1. Disconnect 1 or more devices. 2. Replace cabling with 2mm2 (15AWG) or thicker. 3. Use shorter cabling. 4. Contact your dealer to replace the fuse of or the entire power supply
Channel 1 output voltage too high	- Power supply defective - The incoming voltage on the VPU (Vin 1) is too high. - The power supply that is used (possibly not from Nedap), delivers too much power.	Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.
Channel 1 output voltage too low	- Power supply too weak - Cabling too thin (<1.5 mm2) - Cabling too long - Too many devices connected	1. Check the wiring for Vout 1. 2. Reboot the system to check if the attention remains. If the attention remains: 1. Disconnect 1 or more devices. 2. Replace cabling with 2mm2 (15AWG) or thicker. 3. Use shorter cabling. 4. Contact your dealer to replace the fuse of or the entire power supply.
Channel 1 input current too high (peak)	Overload or short circuit.	1. Check wires on breaks, connection and possible corrosion. 2. Check cables in connector.
Channel 1 input current too high	Cabling issue or too many devices connected.	1. Check cabling, connectors and attached devices for corrosion and other defects. 2. Too many V-packs and / or devices connected.
Channel 2 input voltage too high	- Power supply defective - The incoming voltage on the VPU (Vin 2) is too high. - The power supply that is used (possibly not from Nedap), delivers too much power.	Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.
Channel 2 input voltage too low	- Power supply too weak - Cabling too thin (<1.5 mm2) - Cabling too long	1. Check the wiring for Vin 2. 2. Reboot the system to check if the attention remains. If so the attention remains: 1. Disconnect 1 or more devices. 2. Replace cabling with 2mm2 (15AWG) or thicker. 3. Use shorter cabling. 4. Contact your dealer to replace the fuse of or the entire power supply
Channel 2 output voltage too high	- Power supply defective Te incoming voltage on the VPU (Vin 2) is too high. - The power supply that is used (possibly not from Nedap), delivers too much power.	Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.
Channel 2 output voltage too low	- Power supply too weak - Cabling too thin (<1.5 mm2) - Cabling too long - Too many devices connected	1. Check the wiring for Vout 2. 2. Reboot the system to check if the attention remains. If so the attention remains: 1. Disconnect 1 or more devices. 2. Replace cabling with 2mm2 (15AWG) or thicker. 3. Use shorter cabling. 4. Contact your dealer to replace the fuse of or the entire power supply
Channel 2 current too high	Overload or short circuit.	1. Check wires on breaks, connection and possible corrosion. 2. Check cables in connector.
Channel 2 current too high (peak)	Cabling issue or too many devices connected.	1. Check cabling, connectors and attached devices for corrosion and other defects. 2. Too many V-packs and / or devices connected.

Attention

Cause

Possible solution(s)

Channel 1 input voltage too high

- Power supply defective

- The incoming voltage on the VPU (Vin 1) is too high.

- The power supply that is used (possibly not from Nedap), delivers too much power.

Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.

Channel 1 input voltage too low

- Power supply too weak
- Cabling too thin (<1.5 mm2)
- Cabling too long

1. Check the wiring for Vin 1.

2. Reboot the system to check if the attention remains.

If the attention remains:

1. Disconnect 1 or more devices.

2. Replace cabling with 2mm2 (15AWG) or thicker.

3. Use shorter cabling.

4. Contact your dealer to replace the fuse of or the entire power supply

Channel 1 output voltage too high

- Power supply defective

- The incoming voltage on the VPU (Vin 1) is too high.

- The power supply that is used (possibly not from Nedap), delivers too much power.

Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.

Channel 1 output voltage too low

- Power supply too weak
- Cabling too thin (<1.5 mm2)
- Cabling too long
- Too many devices connected

1. Check the wiring for Vout 1.

2. Reboot the system to check if the attention remains.

If the attention remains:

1. Disconnect 1 or more devices.

2. Replace cabling with 2mm2 (15AWG) or thicker.

3. Use shorter cabling.

4. Contact your dealer to replace the fuse of or the entire power supply.

Channel 1 input current too high (peak)

Overload or short circuit.

1. Check wires on breaks, connection and possible corrosion.
2. Check cables in connector.

Channel 1 input current too high

Cabling issue or too many devices connected.

1. Check cabling, connectors and attached devices for corrosion and other defects.

2. Too many V-packs and / or devices connected.

Channel 2 input voltage too high

- Power supply defective

- The incoming voltage on the VPU (Vin 2) is too high.

- The power supply that is used (possibly not from Nedap), delivers too much power.

Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.

Channel 2 input voltage too low

- Power supply too weak
- Cabling too thin (<1.5 mm2)
- Cabling too long

1. Check the wiring for Vin 2.

2. Reboot the system to check if the attention remains.

If so the attention remains:

1. Disconnect 1 or more devices.

2. Replace cabling with 2mm2 (15AWG) or thicker.

3. Use shorter cabling.

4. Contact your dealer to replace the fuse of or the entire power supply

Channel 2 output voltage too high

- Power supply defective

Te incoming voltage on the VPU (Vin 2) is too high.

- The power supply that is used (possibly not from Nedap), delivers too much power.

Reboot the system to check if the attention remains. If so, contact your dealer to replace the fuse or the entire power supply.

Channel 2 output voltage too low

- Power supply too weak
- Cabling too thin (<1.5 mm2)
- Cabling too long
- Too many devices connected

1. Check the wiring for Vout 2.

2. Reboot the system to check if the attention remains.

If so the attention remains:

1. Disconnect 1 or more devices.

2. Replace cabling with 2mm2 (15AWG) or thicker.

3. Use shorter cabling.

4. Contact your dealer to replace the fuse of or the entire power supply

Channel 2 current too high

Overload or short circuit.

1. Check wires on breaks, connection and possible corrosion.
2. Check cables in connector.

Channel 2 current too high (peak)

Cabling issue or too many devices connected.

1. Check cabling, connectors and attached devices for corrosion and other defects.

2. Too many V-packs and / or devices connected.

Attention	Cause	Possible solution(s)
No Vpacks detected or addressing is not correct	No V-packs are detected, communication with one or more V-packs is interrupted, or one or more V-packs have an incorrect logic address.	1. When using multiple V-packs/VPUs, ensure each V-pack has a unique logic address. Go to Settings > Devices > V-packs. Change addresses if necessary. 2. Check wires on breaks, connection and possible corrosion. 3. Reboot the system. In Nedap Velos, go to Maintenance > Vpacks > Select VPU > Reboot.
Vpack firmware is not up to date	Vpack firmware is not up to date.	1. Select the V-packs that must be updated. - System with one VPU: First update the VPU. Then update the V-packs simultaneously. - System with multiple VPUs: First update the main VPU and corresponding V-packs. Then update secondary VPUs with its V-packs one by one. 2. Select Actions > Update 3. Select I agree to confirm.

Attention

Cause

Possible solution(s)

No Vpacks detected or addressing is not correct

No V-packs are detected, communication with one or more V-packs is interrupted, or one or more V-packs have an incorrect logic address.

1. When using multiple V-packs/VPUs, ensure each V-pack has a unique logic address. Go to Settings > Devices > V-packs. Change addresses if necessary.

2. Check wires on breaks, connection and possible corrosion.

3. Reboot the system. In Nedap Velos, go to Maintenance > Vpacks > Select VPU > Reboot.

Vpack firmware is not up to date

Vpack firmware is not up to date.

1. Select the V-packs that must be updated.
- System with one VPU: First update the VPU. Then update the V-packs simultaneously.
- System with multiple VPUs: First update the main VPU and corresponding V-packs. Then update secondary VPUs with its V-packs one by one.
2. Select Actions > Update
3. Select I agree to confirm.

Attention	Cause	Possible solution(s)
Power supply error	The voltage feed for a beacon is too low. Several causes are possible: - Power cable is too long. - One or more connectors are broken. - There are too many beacons connected to one power supply	1. Check the length of the power cable (max. 180m / 591 ft.) 2. Check the connectors of all beacons. Replace broken ones. 3. Max 12 beacons can be connected to a VP2001.
High temperature	The temperature of the beacon is too high due to external factors.	Check if the beacon is exposed to direct sunlight. When this is the case, protext the beacon from the sunlight.
Beacon transmitting error	The beacon is not able to tune its antenna. This system attentions often appears with the beacon tune error.	Turn the power of the beacon(s) off, and turn the power on again.
Beacon tune error	The beacon is not able to tune its antenna.	1. Reboot the system. Go to Maintenance > V-packs>Select VPU > Reboot. 2. Turn the power of the beacon(s) off, and turn the power on again.

Attention

Cause

Possible solution(s)

Power supply error

The voltage feed for a beacon is too low. Several causes are possible:
- Power cable is too long.
- One or more connectors are broken.
- There are too many beacons connected to one power supply

1. Check the length of the power cable (max. 180m / 591 ft.)
2. Check the connectors of all beacons. Replace broken ones.
3. Max 12 beacons can be connected to a VP2001.

High temperature

The temperature of the beacon is too high due to external factors.

Check if the beacon is exposed to direct sunlight. When this is the case, protext the beacon from the sunlight.

Beacon transmitting error

The beacon is not able to tune its antenna. This system attentions often appears with the beacon tune error.

Turn the power of the beacon(s) off, and turn the power on again.

Beacon tune error

The beacon is not able to tune its antenna.

1. Reboot the system. Go to Maintenance > V-packs>Select VPU > Reboot.
2. Turn the power of the beacon(s) off, and turn the power on again.

Attention	Cause	Possible solution(s)
Sensor is not detecting animals	Sensors are either dirty and/or incorrectly adjusted regarding the detection distance.	1. Clean the sensors and check their performance 2. Adjust the distance of the sensor when it detects the floor. Use the instruction manual of the sensor's manufacturer.

Attention

Cause

Possible solution(s)

Sensor is not detecting animals

Sensors are either dirty and/or incorrectly adjusted regarding the detection distance.

1. Clean the sensors and check their performance
2. Adjust the distance of the sensor when it detects the floor. Use the instruction manual of the sensor's manufacturer.

Attention	Cause	Possible solution(s)
Gate not open	The gate could not be opened.	1. Clean the sensors and check their performance 2. Check the position of the sensors 3. Check wires on breaks, connection and possible corrosion. 4. Check the walkway and gate for obstruction (iron work is not blocked).
Gate not closed	The gate could not be closed.	1. Clean the sensors and check their performance 2. Check the position of the sensors 3. Check wires on breaks, connection and possible corrosion. 4. Check the walkway and gate for obstruction (iron work is not blocked).

Attention

Cause

Possible solution(s)

Gate not open

The gate could not be opened.

1. Clean the sensors and check their performance
2. Check the position of the sensors
3. Check wires on breaks, connection and possible corrosion.
4. Check the walkway and gate for obstruction (iron work is not blocked).

Gate not closed

The gate could not be closed.

Attention	Cause	Possible solution(s)
No messages received for too long	Messages from the SmartFlow are not received by the VP4102. Possible causes: lack of power, cabling issue, network issue, BC configuration	1. Check power supply to the VP4102. 2. Check wires on breaks, connection and possible corrosion. 3. Check the connector. 4. Check cables in connector. 5. Check network, see the System attention No data exchange; Unstable internet connection. 6. Check behaviour component configuration.
System setup does not allow Auto Calibration calculation	The configuration is not according the specifications. On a parlor with more than 60 milk places, a secondary VPU is mandatory. When it is not this way, the system is not able to execute the auto calibration calculation task.	Make sure that an installation with more than 60 milk places has more than one VPU. Possibly a VPU has to be added and a reconfiguration needs to take place. When this is improved, the attention will be resolved after a reboot.

Attention

Cause

Possible solution(s)

No messages received for too long

Messages from the SmartFlow are not received by the VP4102.
Possible causes: lack of power, cabling issue, network issue, BC configuration

1. Check power supply to the VP4102.
2. Check wires on breaks, connection and possible corrosion.
3. Check the connector.
4. Check cables in connector.
5. Check network, see the System attention No data exchange; Unstable internet connection.
6. Check behaviour component configuration.

System setup does not allow Auto Calibration calculation

The configuration is not according the specifications. On a parlor with more than 60 milk places, a secondary VPU is mandatory. When it is not this way, the system is not able to execute the auto calibration calculation task.

Make sure that an installation with more than 60 milk places has more than one VPU. Possibly a VPU has to be added and a reconfiguration needs to take place. When this is improved, the attention will be resolved after a reboot.

Attention	Cause	Possible solution(s)
One or more VPUs are missing	The connection between the main and secondary VPU is interrupted or broken. 1 or more VPUs are not seen for 10 mins.	1. Open the IP address in your browser to see if it is connected. 2. Check the version of the VPUs. 3. Reboot the VPU. 4. Check wires on breaks, connection and possible corrosion 5. Check the connector. 6. Check cables in connector. 7. Check network, see the System attention No data exchange; Unstable internet connection.
One or more VPUs are missing too often	The connection between the main and secondary VPU is or was interrupted or broken. This happened 5 times or more within 24 hours. A common cause is an unstable network or an IP-conflict.	1. Open the IP address in your browser to see the VPU is connected. 2. Check the version of the VPUs. 3. Reboot the VPU. 4. Check wires on breaks, connection and possible corrosion 5. Check the connector. 6. Check cables in connector. 7. Check network, see the System attention No data exchange; Unstable internet connection. 8. Login to your router and check settings or possible IP conflicts. Re-assign the IP addresses for the connected devices. You can do this yourself or ask a network specialist.
A secondary VPU has a higher version than the main VPU. Update the main VPU.	A secondary VPU has a higher version than the main VPU.	1. Check the connection between the VPUs 2. Reboot the secondary VPU. 3. Update the main VPU.

Attention

Cause

Possible solution(s)

One or more VPUs are missing

The connection between the main and secondary VPU is interrupted or broken. 1 or more VPUs are not seen for 10 mins.

1. Open the IP address in your browser to see if it is connected.
2. Check the version of the VPUs.
3. Reboot the VPU.
4. Check wires on breaks, connection and possible corrosion
5. Check the connector.
6. Check cables in connector.
7. Check network, see the System attention No data exchange; Unstable internet connection.

One or more VPUs are missing too often

The connection between the main and secondary VPU is or was interrupted or broken. This happened 5 times or more within 24 hours.

A common cause is an unstable network or an IP-conflict.

1. Open the IP address in your browser to see the VPU is connected.

2. Check the version of the VPUs.

3. Reboot the VPU.

4. Check wires on breaks, connection and possible corrosion

5. Check the connector.

6. Check cables in connector.

7. Check network, see the System attention No data exchange; Unstable internet connection.

8. Login to your router and check settings or possible IP conflicts. Re-assign the IP addresses for the connected devices. You can do this yourself or ask a network specialist.

A secondary VPU has a higher version than the main VPU. Update the main VPU.

A secondary VPU has a higher version than the main VPU.

1. Check the connection between the VPUs
2. Reboot the secondary VPU.
3. Update the main VPU.

Attention	Cause	Possible solution(s)
Unstable internet connection	The connection to the server is not stable enough to send and receive data reliably. This can cause messages to remain in the queue and cloud synchronization to fail.	Check the network connection: - Ensure the installation and the PC are connected to the same network. - Check that the PC has a working internet connection. - Prefer a wired network connection instead of Wi-Fi. - Check the router, modem, switch, and network cables for errors or loose connections. - Ensure that firewall, proxy, or security software is not blocking the connection. - Restart the application, router, or modem if necessary.
Optional network test (Windows) 1. Select Start, type cmd, and press Enter. 2. Run ipconfig and verify that a Default Gateway is shown. 3. Run ping <gateway address> to test the local network. 4. Run ping 8.8.8.8 to test the internet connection. 5. Run nslookup google.com to verify DNS resolution. If the connection remains unstable, contact the network administrator or internet provider.

Attention

Cause

Possible solution(s)

Unstable internet connection

The connection to the server is not stable enough to send and receive data reliably. This can cause messages to remain in the queue and cloud synchronization to fail.

Check the network connection:

- Ensure the installation and the PC are connected to the same network.

- Check that the PC has a working internet connection.

- Prefer a wired network connection instead of
Wi-Fi.

- Check the router, modem, switch, and network cables for errors or loose connections.

- Ensure that firewall, proxy, or security software is not blocking the connection.

- Restart the application, router, or modem if necessary.

Optional network test (Windows)

1. Select Start, type cmd, and press Enter.

2. Run ipconfig and verify that a Default Gateway is shown.

3. Run ping <gateway address> to test the local network.

4. Run ping 8.8.8.8 to test the internet connection.

5. Run nslookup google.com to verify DNS resolution.

If the connection remains unstable, contact the network administrator or internet provider.

Solve System Attentions

Velos webhelp

Quick links

Information and privacy