Velos 2025.1 Dairy Farming

This Nedap Velos software version contains new and improved functionalities that provide new solutions, add valuable options to existing solutions and further increase the ease of use of Velos.

Nedap FarmControl

Identification

• Cows were not removed at the end of the rotation on a rotary parlour where the lowest position number was not equal to 1. This issue has now been resolved.

Traffic

• The page 'Settings > Separation rules' displays in the 'Next' column when each separation rule will be executed next. Previously, this column incorrectly showed dates in the past. This issue has now been resolved.

Feeding

• On a rotary parlour where cows are fed on the rotary, feeding issues occurred if the lowest position number on the rotary was not equal to 1. This issue has now been resolved.

• On a rotary parlour where cows are fed on the rotary, the system could not be configured if it needed to support the distribution of 6 different feed types. It was not possible to link V-Packs in this scenario. This issue has now been resolved.

Nedap CowControl

Heat Detection and Health Monitoring

• In large Velos installations connected to Nedap Now, it could sometimes take a long time to send all the heat and health data generated during a temporary internet interruption to Nedap Now. This process has now been optimized, ensuring the data is transmitted more efficiently, and such delays will no longer occur.

• On the monitor page of a behavior component of the type 'SmartTag receiver,' accessible via 'Maintenance > Behavior components,' no data was displayed under the 'Frequencies' tab. This issue has now been resolved.

Cow Locating

• Velos now supports sending cow positions to Nedap Now. Starting with this Velos version, Nedap Now can display cow positions like it is also possible in Velos and it works in parallel.

  Cow Locations in Velos:

  

  Locations of the same cows in Nedap Now:

  

• On the settings page for the behaviour component 'Positioning beacons setup,' the 'Next' button was available to some users, but on the following page, those users were unable to make any changes. This issue has now been corrected.

• Fixed an issue where cow locating beacons are sometimes lost by the VPU. This happened especially at farms with multiple readers where the beacons are detected by multiple readers.

Nedap MilkingControl

• After releasing our modifications for row parlours, we received some complaints from rotary parlour users regarding changes to the prewash (cluster down) mode. Previously, this mode allowed users to perform the action one cluster at a time, but it has now been removed. As a result, transitioning to standby mode was being performed for all clusters simultaneously on rotary parlours, which is not ideal. This could cause clusters to slide on the floor or become stuck at the bridge.

  To address this issue, transitioning to standby mode on rotary parlours is now performed per cluster rather than for all clusters at once, ensuring a smoother and more practical operation.

• The SmartFlow Zero Point Test procedure has been simplified in the user interface because it was complicated due to too many options and unclear messages. Previously after a successful Zero Point Test there were various messages with explanations and various buttons like 'Write result', 'Overwrite value' en 'Store result' to save the result of the test. Now, after a successful Zero Point Test, simply the message 'Test completed' is displayed, and there is a 'Save' button to save the result.

• Previously, it was not possible to create a parlour if the Velos license included 'MQTT' but did not include 'InTouch' and 'Parlour Monitor'. This issue has now been resolved.

• A problem has been resolved in which, in specific cases, the control of an InTouch system was not fully taken over by Velos. This resulted in strange behaviour because Velos was partially controlling the InTouch system while the InTouch system also operated partially in standalone mode.

• The SmartFlow UHF frequency is now also configured correctly for use in Saudi Arabia and Argentina.

• The auto take-off function of the InTouch did not function correctly on InTouch systems installed on a rotary parlour, where the InTouch behaviour components run on a different VPU than the Rotor behaviour component. This has been fixed.

• When a the wash controller is connected to the main VPU and washing is turned off while the main VPU has no connection with the secondary VPU, the InTouch devices connected to that secondary VPU could not get out of washing mode anymore. This has been fixed.

General

• Nedap constantly updates the software to prevent security vulnerabilities. In this version some 3rd party libraries have been updated because of vulnerability: CVE-2025-24970.

• When Velos operates in Nedap Now mode, adjustments were previously made to hide many pages in the Velos user interface. This restriction has now been lifted, ensuring that Velos displays all pages even while in Nedap Now mode. This primarily applies to the heat and health pages. It is important to note, however, that Velos uses different algorithms than Nedap Now, meaning the displayed graphs and alerts may differ from those shown in Nedap Now.

• The data export function, designed to facilitate the transition to Nedap Now, has been improved in several ways:

  • After Velos sends all data to Nedap Now, it takes some time for Nedap Now to process the data. The export is now considered successful only after Nedap Now has completed processing the data. This status is now visible on the export status page.

    

  • Nedap Now does not allow duplicate 'Life numbers,' whereas Velos does. To prevent the export from failing due to this, Velos now performs a pre-check and indicates which animals have duplicate 'Life numbers.'

  • If data was exported from a Velos installation without the 'Health and Management' module in its license, the export would fail. This is now also checked in advance to ensure the export does not fail for this reason.

  • Each data type now has 'Pending' as initial status where previously no status was displayed at all.

  • The export status page can now also be viewed after a user is logged out.

• Velos now utilizes Bootstrap 5. As a result of this update, some elements in the user interface may appear slightly different from their previous design.

• Resolved following issues:

  • If the logical address or section of a VPU was changed, the old certificate was not removed, causing MQTT communication to fail.

  • If uploading an update file failed it was not possible to restart the update.

  • Sometimes secondary VPUs could not be updated.

  • The setup wizard would fail after entering the VPU address.

  • The license update page occasionally displayed no text.

  • In the specific case where a VPU was reset to factory defaults and then configured as a secondary VPU in the setup wizard, it could continuously restart. To resolve the issue, the VPU had to be powered off. A permanent solution has now been implemented to prevent this restarting behaviour from occurring.

  • SmartTag capabilities were sent to Nedap Now each time a SmartTag sends a capabilities message. This could cause performance problems in the cloud due to the high number of requests. Now the SmartTag capabilities are sent only when one or more attributes have changed.

Taurus

• Several changes have been made to the Taurus 6 implementation:

  • The specific check for the DelPro license has been removed; a Taurus license alone is now sufficient.

  • If importing the Taurus file results in errors, a clear message is now provided indicating which line in the file caused the issue.

  • Pregnancy check states 3 (undetermined) and 4 (keep open) are now handled the same way as in Taurus 5. Specifically, states 3 and 4 in the CSV file are converted to 4 in Velos, and states 3 and 4 in Velos are converted to 3 in the CSV file.

  • If a pregnancy check was defined in a csv file no pregnancy check event was added in Velos. This has been fixed.

  • The DelPro import no longer fails in the Chile/Continental timezone when an animal has a birth date that falls on a daylight saving time transition day. This is because the time 0:00 does not exist on such days in the Chile/Continental timezone.

  • The DelPro import did remove the second responder in Velos. This has been fixed.

  • Taurus did not accept calendar date "00000000". This has been fixed.

  • The milking_extended CSV export often showed negative values for detach flow rate. This has been fixed

Firmware

• We have significantly improved the speed of updating firmware for V-Packs. Previously, only one V-Pack could be updated at a time, but now multiple V-Packs can be updated in parallel. For V-Packs connected via Ethernet, there is no limit to the number that can be updated simultaneously. For V-Packs connected via CAN, up to 4 can be updated in parallel per CAN channel (equaling 8 in parallel per VPU). However, for V-Packs connected via UHF, the limit remains 1 device at a time.

• There were 2 VP1801 firmware files

System requirements

Velos version

• An installation needs to run on version 2024.1 SR4 or newer to be able to update to this version. Make sure to update to version 2024.1 SR4 or newer first before installing this version.

Taurus

• When using Taurus for a DelPro integration this Velos version is only compatible with Taurus 2024.1.1 (5.147.25.0)

• For all other integrations this Velos version is compatible with Taurus 2020.1 (5.101.7.0) up to and including Taurus 2024.1.1 (5.147.25.0)

• This Velos version is compatible with Taurus 6.0 (6.0.0.60) for all integrations. Taurus with build numbers 5.x.x.x are deprecated and therefore it is advised to use Taurus 6.0.

Mobile device versions:

• iOS 15 or later

• Android 5.0 or later

Supported browsers:

• Google Chrome

• Microsoft Edge