Page 8 of 8

Re: Firmware 3.4

PostPosted: April 25th, 2016, 4:02 pm
by glnc222
There was some mention of "improved power management" in v3.4 reducing run time a few minutes to increase the reserve for returning to base. There was an old problem of the bot oddly stopping in front of the dock without docking. This could be because a strict reserve requirement was imposed to insure sufficient charge to withdraw from the dock in case of connection problems. Poor connection could cause damaging heat in the charging contacts, a yet older problem leading to the wiggling behavior when docking, trying to improve connection. Insufficient reserve could be caused by very long returns to base for which the charge usage could not be precisely predicted. Normal aging of the battery could also not be precisely modeled, limiting accuracy of reserve predictions. Hence a larger reserve added to cover contingencies.

Re: Firmware 3.4

PostPosted: May 18th, 2016, 8:08 am
by nadaske
Hello Friends, help me please...
I try to update my neato xv-11
because it have super old version of firmware. Prototype version have only: scheduler, set time, help - menus.
I know now i can update only in offline\manual mode. i use neatoupgrader+driver+firmware file+command file, but after start update procedure , after first copy file to the robot , robot not switched on automaticly. Just shutdown, and upgrade process is stoped. I can show upgrader log in the evening. Thank you for attention.

Re: Firmware 3.4

PostPosted: May 19th, 2016, 2:42 am
by nadaske
i has ben update my xv11 .

Re: Firmware 3.4

PostPosted: May 19th, 2016, 12:59 pm
by glnc222
Old Rev113 Cruz system board cannot be updated past v3.2 -- different cpu. Last online update v3.1.
Putting v3.4 in Cruz will brick it.

Re: Firmware 3.4

PostPosted: July 14th, 2016, 11:02 am
by zhangckid
glnc222 wrote:I think I have located a confusion involved in the Russian instructions for offline firmware updating.

[edit] This material is limited to the newer Rev.64 "Binky" system board processor. For the oldest Rev. 113 "Cruz" boards (on machines with a charging jack on the side) a method using Vorwerk's procedure instead of Neato Robotics was found. It was previously reported Vorwerk and Neato use the same firmware except for unpublished configuration commands set over USB when installing, allowing charging lithium batteries in the Neato robots for example (lithium and NIMh batteries require different charging procedures). See separate thread "Guide: How to Update Neato XV Series With Vorwerk Updater" http://www.robotreviews.com/chat/viewtopic.php?f=20&t=19005. Rev113 board code files from Vorwerk have also been used with the Neato Upgrader here listed for Rev64 only; later post below http://www.robotreviews.com/chat/viewtopic.php?p=134925#p134925.
Remember the old Rev113 Cruz system board is incompatible with firmware beyond v3.1 (online; 3.2 now found working offline per later posts).
[edit] Complete older rev113 Cruz file collection for Neato Upgrader https://github.com/NoahJaehnert/Neato-XV-Series-Cruz-Rev-113-Update courtesy djos post
http://www.robotreviews.com/chat/viewtopic.php?p=134994#p134994
-- know your system board type: old boards have working side jack for charging.
Rev64 Binky picture http://xv11hacking.wikispaces.com/PCB+rev.+64?responseToken=1fde818a4b8987f46d1d464e64e89ca2
Rev113 Cruz http://xv11hacking.wikispaces.com/PCB+rev.+64

[edit] Offline updating is more correct than online, eliminating any internet connection failures. Correct online procedures would first download all files to the PC for an offline procedure and just automatically proceed.
The online procedure might also check the status of the existing firmware in the robot and the system board to insure compatibility. Details of Neato's procedure were not disclosed.

Neato Upgrader Tool and Driver Installation
There are references to both a "NeatoUpgrader" program and a "NeatoUpdaterTool".
The "Updater Tool" is the installation file from the Neato updating website, now discontinued. However, the tool file links are still active, and I have copies of the files if needed. These files are also used to send USB commands to Botvac for which no updating web pages ever existed at the company website, barring access to the files through the web page menus.
As posted for use in the Neato Control Program thread:
Windows 64-bit:
http://www.neatoroboticsupdates.com/Nea ... er_x64.exe
32-bit:
http://www.neatoroboticsupdates.com/Nea ... er_x86.exe
Note in 64 bit Windows 7, and all 8 and later a global setting is needed to over-ride prohibition of unsigned drivers,
regardless of any options presented locally on screen by obsolete code. Instructions on the web, e.g. here
http://www.robotreviews.com/chat/viewtopic.php?p=125431#p125431 Prodcedure varies over different Windows versions as Microsoft moves things around.

The installation files install two different things, a USB driver in Windows for the Neato XV and Botvac devices, identifying them to programs, and also a kind of terminal emulator program "NeatoUpgrader" installed in the Windows Program Files (x86) directory, in a Neato Robotics folder. The Upgrader is used by the second, firmware install step on the company updating website (now discontinued).
[edit] The Updgrade tool also records a log file of its operations which reveals details of the update procedure at C:\Users\YourName\AppData\Local\NeatoUpgrader\Logs\

The Upgrader takes a script file argument. The script file contains commands for the Upgrader which uses a Send command to send USB commands and data to the robot, as well as internal commands such as time delay WAIT etc.
The Upgrader script will reference another file of .enc type containing the firmware to be uploaded to the robot.
These files are supplied by the links in Lewiy's post earlier in this thread
http://www.robotreviews.com/chat/viewtopic.php?p=127302#p127302
(the last file listed, a second v3.0 link to Hex's Neato Control website, is no longer online. Duplicate of the other material not needed)

The robot itself performs the flashing operation given the data.
The risk involved is if the flashing over-writes the flashing program itself, there could be a problem in case of any errors, destroying the ability to re-flash any correction. Many software and hardware techniques are used to arrange these things in a robust, error resistant way which can recover from errors, with duplicate copies etc. We do not know how good the Neato work was. Garmin GPS units get updated all the time for map revisions and never show problems, example of a proper system.

A user above reports success with the process, along with Russian users etc. (Shirgal also reports success). It is important that the robot and PC be in perfect working order, equipped with a good charged battery, and run on battery -- because power management from the dock is under software control, which software is being updated...

Hardware issues
The Russian .enc files supplied are for the newer, v64 "Binky" system board Neato XV series only. v113 "Cruz" boards have a different, incompatible microcontroller and circuits. The newer system boards are in all units lacking the side jack for direct charger connection on original XV's. Some units also had the jack but covered up with a plug. It may be necessary to open the case and examine the system board. See Mods & Repairs main forum page for links to disassembly instructions. Installing the wrong software in a system can render it irrepairable, "bricked" (usable only as a brick...).

Script File and Procedure
I have edited a translation by Lewiy of the Russian instructions. Neato Robotics does not explain details of the Upgrader commands, so it is not clear what would be done just by issuing USB commands manually. Some of the Upgrader commands likely relate to properly exiting and restarting the robot system. It is typically necessary to reboot a system, powering on and off, after flashing firmware. This is similar to rebooting a Windows PC when installing some system software updates. The reboot loads things into memory which are difficult to arrange once the system is already setup in memory and messy to manipulate, while the system is running.

Instructions:
1) Download the firmware .enc file desired
2) Rename the firmware file for easy - file.enc (i.e. filename "file")
3) Create a text script file my.txt with the following content :

send SetLanguage None
getlocal file.enc
wait 5000 (corrected previous typo "5000 wait" per Shirgal following post0
send testmode on (note this USB command must always be set off manually instead of just disconnecting USB or closing a terminal program, or by rebooting the system as done here)
send-nowait setsystemmode PowerCycleCDC (unkown function of upgrader)
wait 22000
upload code reboot
wait 22000
send getversion
send SetLanguage None

4) Copy my.txt file to the folder where you installed NeatoUpgrader.exe (usually "C:\Program Files(x86)\Neato Robotics\" or "C:\Program Files\Neato Robotics\" depending on the operating system) .
5) Connect the robot to the computer in the usual way, and turn it on.
6) Run in the folder where you installed NeatoUpgrader.exe, the following command at a command prompt:
NeatoUpgrader.exe /NoServer my.txt

If the robot has been connected properly (in the list of COM-ports has Neato), then the whole process will take place rather quickly - first, the screen goes blank and the robot will restart the service mode, which will be active only a special boot firmware. Further, the robot will be loaded with firmware from the specified file. If all goes well, the robot will restart again and ask you to select the language as in the first turn. It's all!
The robot then write that he wants to charge - this is normal and has been repeatedly discussed.
User in previous post mentioned needing to power off and restart the Neato to properly reboot.
Perhaps there was an issue merely because Testmode OFF was not included, unknown.



Hi~~~ I have a xv-12 v113 rebot, when I use the neatocontrol connect it the rebot auto reboot,so
I can't connect it,and use github way reboot too.....
have you any comments for this ????
I want offline update my rebot,v2.6 -> v3.2

Re: Firmware 3.4

PostPosted: July 14th, 2016, 12:53 pm
by glnc222
[edit] For the USB driver and updater program install from Neato to use the above updating method, no longer at their site now posted here, see post
http://www.robotreviews.com/chat/viewtopic.php?p=127716#p127716

For Rev113 Cruz system boards only the Vorwerk files can be used. Complete report http://www.robotreviews.com/chat/viewtopic.php?f=20&t=19005
See notes in Mods & Repairs list top of main forum page.
The USB connection can be tested with a terminal emulator such as hyperterminal etc. The command language manual link is given.
I do not know about any resets. There is a defect in capacitor C10 on some system boards (another thread) which fixes a sleep problem, where sometimes inserting a USB connection wakes up the cpu. See Mods & Repairs.

Re: Firmware 3.4

PostPosted: July 19th, 2016, 3:41 am
by zhangckid
glnc222 wrote:For Rev113 Cruz system boards only the Vorwerk files can be used. Complete report http://www.robotreviews.com/chat/viewtopic.php?f=20&t=19005
See notes in Mods & Repairs list top of main forum page.
The USB connection can be tested with a terminal emulator such as hyperterminal etc. The command language manual link is given.
I do not know about any resets. There is a defect in capacitor C10 on some system boards (another thread) which fixes a sleep problem, where sometimes inserting a USB connection wakes up the cpu. See Mods & Repairs.


Make sense. but I can't update my robot used by Vorwerk VR100 Update Software.
it run to 5/5 say "update failed ,please retry....", robot has been reset....

Re: Firmware 3.4

PostPosted: July 19th, 2016, 12:40 pm
by glnc222
The flashing operation is performed by the cpu in the robot. There could be some defect in the hardware for that function, in the memory, whatever. Rev113 boards are very old. I thought some had been updated.

Re: Firmware 3.4

PostPosted: July 20th, 2016, 11:57 am
by zhangckid
glnc222 wrote:The flashing operation is performed by the cpu in the robot. There could be some defect in the hardware for that function, in the memory, whatever. Rev113 boards are very old. I thought some had been updated.


Thanks for your comments~~~
I just buy one for fun~~~
Do you have a github?
glad to meet you~~ :D

Re: Firmware 3.4

PostPosted: August 24th, 2016, 1:10 pm
by bcre3306
Does anyone have the link to 3.2 for blinky board? I upgraded to 3.4 and the performance of my unit was much worse and the unit would constantly get stuck. I downgraded to 3.1 but thought 3.2 was a little better. Any help would be appreciated.

Re: Firmware 3.4

PostPosted: August 24th, 2016, 2:24 pm
by glnc222
We do not have yet here a link for v3.2 Binky Rev64 system board, only v3.1. I do not think there is much difference, just opinion. http://www.robotreviews.com/chat/viewtopic.php?p=134696#p134696

Re: Firmware 3.4

PostPosted: September 4th, 2016, 2:20 pm
by rafidan
Help me please
neato xv signature software update from Firmware 3.2 to Firmware 3.4 how can i do it ???

Re: Firmware 3.4

PostPosted: June 12th, 2019, 5:53 am
by Spary
I would like to update the firmware version of my neato xv robot(board revision is 64) to version 3.4
But apparently the link to the binky 3.4 firmware is dead (http://www.neatoroboticsupdates.com/Com ... .24079.enc).

Does someone could share it please ?

Re: Firmware 3.4

PostPosted: June 16th, 2019, 8:25 am
by glnc222
Links from Lewiy in post above http://www.robotreviews.com/chat/viewtopic.php?p=127302#p127302
to neatoupdates.com may be discontinued, but he posted other links at thread
http://www.robotreviews.com/chat/viewtopic.php?p=151720#p151720
System board Rev64 Binky v3.4 https://yadi.sk/d/O3xXQ8t_NLw9lA
[edit] Lewiy has also supplied v3.0 and 3.1, now identified:
Version 3.0 https://yadi.sk/d/8gRMOkuG0cfbKw
Version 3.1 https://yadi.sk/d/BniHBCs2u_SYTA

These files are for use with the scripted updating program discussed above in this thread
http://www.robotreviews.com/chat/viewtopic.php?p=134710#p134710

v3.1 introduced the "corner clever" behavior for more thorough cleaning in corners.
(for older system board Rev113 Cruz see thread on Vorwerk method updating top of forum)
Later versions add only tweaks to operations such as supposed power management improvements, not clear.
The superseding Botvac models have different firmware and additions for WiFi comm etc.

Re: Firmware 3.4

PostPosted: June 17th, 2019, 5:12 am
by Spary
Thank you so much glnc222. Thanks to you I am able to upgrade my neato.