Neato upgrade fails

News and information about the Neato XV-11 Robotic Vacuum. All discussion and troubleshooting questions go here.

Re: Neato upgrade fails

Postby ginagina » April 11th, 2013, 6:41 am

I'm trying to update Neato's software from 2.6 to 3.1 but the browser (Chrome, Firefox, Safari) freezes at "http://www.neatorobotics.com/support/update-details/#!prettyPhoto[iframe]/0/"

I have Mac OS X 10.6.8 and Neato XV-21 (private import to Europe).

Is it normal that the NeatoUpgrader software does nothing visible when started?

Any advice about what to do?
ginagina
 
Posts: 2
Joined: April 11th, 2013, 4:19 am

Re: Neato upgrade fails

Postby invenio » April 25th, 2013, 4:53 pm

ginagina wrote:I'm trying to update Neato's software from 2.6 to 3.1 but the browser (Chrome, Firefox, Safari) freezes at "http://www.neatorobotics.com/support/update-details/#!prettyPhoto[iframe]/0/"

I have Mac OS X 10.6.8 and Neato XV-21 (private import to Europe).

Is it normal that the NeatoUpgrader software does nothing visible when started?

Any advice about what to do?


I had difficulty with Opera browser. Try Internet Explorer on a PC (windows 7), that worked for me.
Robot: Neato Robotics XV-11 (with Vic's HEPA filter mod)
User avatar
invenio
Robot Addict
 
Posts: 175
Joined: March 19th, 2013, 6:16 pm

Re: Neato upgrade fails

Postby toronto-neato » May 11th, 2013, 11:56 pm

Just upgraded to 3.1 (from version 1.x). Important notes:

Used an Intel PC (I've read there may be problems with AMD chipsets and USB ports, but I couldn't test that) with Windows 8 (using this trick to get Neato Updater 2.0 to install properly: http://capirgotech.wordpress.com/2013/0 ... windows-8/ )

Had to *disconnect* my router and use a direct Ethernet connection to the computer from the cable modem.

I used Firefox.

It went flawlessly, and quickly (just a couple of minutes) when nothing else worked. I spent probably four hours on this to get this going. Please, Neato: add these tips to your updater website at least, to minimize the grief of your proud Neato owners? We're a tech-savvy bunch here, but most consumers really aren't.

Glad to add my 2 cents' worth on this very vexing problem...
toronto-neato
 
Posts: 3
Joined: September 1st, 2011, 11:51 pm

Re: Neato upgrade fails

Postby Barleyman » April 13th, 2014, 7:46 am

Yup, neato robotics has not bothered to get a driver signature for the upgrade software so you have to jump thru hoops on any 64-bit windows.

The instructions are not quite valid for windows 8.1, when it tells you to choose "general", you really want "update and recovery", then "recovery" and from there you'll find the "advanced startup" button.
Barleyman
 
Posts: 16
Joined: May 12th, 2011, 6:07 am

Re: Neato upgrade fails

Postby glnc222 » July 17th, 2014, 5:19 pm

The Neato Updater Tool on the company website, for Windows 64 bits will not install in Windows 8.1 on an Intel Celeron machine.
After running, the installer runs its own uninstaller, very strange.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby glnc222 » July 17th, 2014, 9:36 pm

It turns out this version of Windows 8.1 Updated is a slightly reduced form recently introduced for OEM's only, Windows 8 With Bing. The driver does not install because it lacks a "Signature" authentication feature used for certifying safe drivers. A dialog box is presented to over-ride this, and the installer reports it is installed, but apparently the over-ride did not work, and nothing about that was reported. Nothing is listed in the Windows program list.

A file at Neato's website and others report how Windows 8 64-bit only, requires a deep system setting to over-ride a more restrictive safety requirement for signatures. http://neatorobotics.com/content/uploads/2014/04/Windows_PC1.pdf
The old dialog-boxes are obsoleted, with a more restrictive global setting.
However, in this reduced Windows 8 the system menus are different than shown in the instructions and lack the required options to adjust the setting. Probably a registry editor would work but the relevant items are unknown.

Attempting to install another driver hackers have posted on the web for the XV11, using the Device Manager driver install method, reports the driver cannot be installed because of missing signature. So the restriction does seem to be present in this Windows version, despite lack of the features to over-ride it.

Protecting systems against faulty drivers is important because of how extensively they can mess up a system and cause freezes. There are complicated requirements proper drivers need to meet and they warrant proper testing.

Bottom line: Neato vacuums cannot be updated on systems with this version of Windows 8 64 bit.
Virtually all PC's made for several years have expanded to 64 bits and only old machines are 32 bit.

A full version of Windows 8 could be installed on the machine but is hardly worth the expense just to update a vacuum robot. It is easier to find another machine somewhere with which to do the updates. It is performed at only annual intervals at most, and it actually looks like there might not be any more, given the new model BotVacs.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby glnc222 » July 18th, 2014, 1:03 am

Advanced Options in Windows 8 With Bing (OEM)

Correction: the advanced configuration features in Windows 8 can be found on the Windows With Bing through a slightly different method found on the web, among the alternative accesses:

The trick is to use the Start Screen power options icon in the upper right for restarting the machine: Press Shift when clicking Restart, and the menu for system troubleshooting will appear.

There is an Advanced Feature option not immediately displayed; Right Click on Troubleshooting and the Advanced Features icon appears below. Using this gets into deep settings which include disabling the block on installing unsigned drivers. Best used only one device at a time, restoring the block after. You never know what junk some software may try and install, including malware.

This should allow the Neato Updating Tool to be installed per the regular Windows 8 document referenced.
It is unlikely at this late time that old chipset drivers from Nvidia or ATI which did not work with Neato's method of using USB are involved in any of these newer machines with this version of Windows, though I have not tested it. I only have an Intel system to test, so cannot tell. But bigger and faster cpu's of recent years all have different chipsets and system board drivers.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby glnc222 » September 29th, 2014, 1:19 pm

New Release V3.4 September 2014
http://www.robotreviews.com/chat/viewtopic.php?f=20&t=18064
Neato Robotics expresses concerns with faulty update operations, while users report successful updates. With recent new model BotVac a wider array of incompatible firmware exists, and the updating website is upgraded various ways.
Vacuums must be registered by serial number in order to update.

[edit]Received reply from Neato Customer Service they can delete bot registrations at the website by supply the info to customer service, account ID email and serial number. Caution they also offer to delete entire accounts, so be very clear in instructions.

Note the entire bot serial number is registered, not anything on the system board inside (which could be replaced routinely in repairs). The serial number appears to be used to identify which type of board was originally installed, to present the menu of available updates even without connecting the bot.
(deletion needed when transferring ownership so a new owner can update it in future; the web site might not allow registering a unit already registered in its database. Request must be sent to Customer Service instead of entered online. The whole procedure stems from registration also used for warranty coverage, requiring ownership tracking etc.)
Last edited by glnc222 on November 10th, 2014, 1:05 am, edited 1 time in total.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby botvac75owner » October 20th, 2014, 12:30 pm

Is there any upgrade for Botvacs available? When I check on the website they say no updates are available. A bit strange I think.
botvac75owner
 
Posts: 1
Joined: October 18th, 2014, 12:24 pm

Re: Neato upgrade fails

Postby vic7767 » October 20th, 2014, 12:56 pm

Presently, there are no firmware upgrades available for download from the NeatoRobotics.com website.

botvac75owner wrote:Is there any upgrade for Botvacs available? When I check on the website they say no updates are available. A bit strange I think.


Why do you make this statement ? Is there something happening with your Botvac that makes you seek an upgrade ?
Roomba and Neato Mods, come visit: http://www.vic7767.com/

http://www.Robot-Doc.com/
User avatar
vic7767
Robot Master
 
Posts: 14408
Joined: January 14th, 2006, 8:31 pm
Location: Haughton Louisiana - USA

Re: Neato upgrade fails

Postby glnc222 » October 20th, 2014, 3:04 pm

With the BotVac introduced only a few months ago it is way too soon to expect any software updates. The latest 3.4 update for XV's probably brings to that line some things from the new work done for the new model (usable only newer XV's without the direct power jack on the vacuum, newer system boards and processors). I would not expect further updates for at least a year, if even then.

General purpose PC programs get more updates because they must work with other, changing programs and products, and a great many operating system features subject to endless little fixes (not to mention the arms race with hackers). The limited function robot software changes only at long intervals, at least after the original product release maybe leaving a few initial bugs to fix.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby glnc222 » March 3rd, 2015, 2:43 pm

Windows Neato Update Log
In Windows PC's at least Win7+ the log of Neato's upgrade process can be found in the file NeatoUpgrader.log, which is located in the folder C:\Users\UserName\AppData\Local\NeatoUpgrader\Logs\NeatoUpgrader.log. info courtesy member Lewiy. Might help identify sources of various updating failures.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby mmm2000 » March 4th, 2015, 12:05 am

Hello all,

After fixing my green dim issue by replacing the C10 capacitor, now my XV-14 won't update properly.
I have win 7, 64 and I tried with 2.0 usb cable, like neato recomnmends.I also tried this update on 2 different computers with no success. Here is one of the logs. It always gets stuck with a timeout, as seen from the log. Does anybody know what the problem might be? I also have new batteries.

Now I have 3.2 and I want to upgrade to 3.4, because of the "better battery performance" promised in 3.4
I edited a few lines in the log where serial number was shown.

[3/3 19:38:21] ********************* Neato Upgrader Started *********************
[3/3 19:38:21] Upgrader Build Number: [NeatoUpgrader 3.0.24118]
[3/3 19:38:21] USING 8KB BLOCKS TO WRITE DATA TO THE ROBOT
[3/3 19:38:21] App executed from [C:\Program Files\Neato Robotics\NeatoUpgrader.exe]
[3/3 19:38:21] Log file = [C:\Users\bea\AppData\Local\NeatoUpgrader\Logs\NeatoUpgrader.log]
[3/3 19:38:21] Windows OS version. Major: [6], Minor: [1]
[3/3 19:38:21] Command line: ["neato://www.neatoroboticsupdates.com/CommandScripts/step_start.txt?reply-to=http://www.neatoroboticsupdates.com/UpgradeResults.aspx?ID=757d83a7-8fdd-499f-8dde-7fcd2939323d&step=checkupdates&os=win7&culture=en"]
[3/3 19:38:21] RunMain Reply Url [http://www.neatoroboticsupdates.com/UpgradeResults.aspx?ID=757d83a7-8fdd-499f-8dde-7fcd2939323d&step=checkupdates&os=win7&culture=en]
[3/3 19:38:21] Script file HTTP URL = [http://www.neatoroboticsupdates.com/CommandScripts/step_start.txt]
[3/3 19:38:21] Reply Url [http://www.neatoroboticsupdates.com/UpgradeResults.aspx?ID=757d83a7-8fdd-499f-8dde-7fcd2939323d&step=checkupdates&os=win7&culture=en]
[3/3 19:38:21] Downloading script file [http://www.neatoroboticsupdates.com/CommandScripts/step_start.txt]...
[3/3 19:38:23] Script file downloaded successfully. Executing commands...
[3/3 19:38:23] Run: [send getversion]
[3/3 19:38:23] Robot connected on: [COM7]
[3/3 19:38:23] Returned: [OK]
[3/3 19:38:23] Run: [send testmode on]
[3/3 19:38:23] Robot connected on: [COM7]
[3/3 19:38:24] Returned: [OK]
[3/3 19:38:24] Run: [send testlds cmd getversion]
[3/3 19:38:24] Robot connected on: [COM7]
[3/3 19:38:24] Returned: [OK]
[3/3 19:38:24] Run: [send testmode off]
[3/3 19:38:24] Robot connected on: [COM7]
[3/3 19:38:24] Returned: [OK]
[3/3 19:38:24] Run: [send getschedule]
[3/3 19:38:24] Robot connected on: [COM7]
[3/3 19:38:25] Returned: [OK]
[3/3 19:38:25] Run: [send getwarranty]
[3/3 19:38:25] Robot connected on: [COM7]
[3/3 19:38:25] Returned: [OK]
[3/3 19:38:25] Run: [send gettime]
[3/3 19:38:25] Robot connected on: [COM7]
[3/3 19:38:25] Returned: [OK]
[3/3 19:38:25] Script execution complete.
[3/3 19:38:25] Posting status to Reply URL...
[3/3 19:38:25] Url:
{
http://www.neatoroboticsupdates.com/Upg ... culture=en
}
ContentType:[multipart/form-data, boundary=N34T0HGQHP]
Body:
{
--N34T0HGQHP

Content-Disposition: form-data; name="Version"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 23



NeatoUpgrader 3.0.24118

--N34T0HGQHP

Content-Disposition: form-data; name="Log"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 28



OK

OK

OK

OK

OK

OK

OK



--N34T0HGQHP

Content-Disposition: form-data; name="Robot"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 1292



getversion

Component,Major,Minor,Build

ModelID,-1,XV14,

ConfigID,2,,

Serial

Software,3,2,18755

BatteryType,1,NIMH_12CELL,

BlowerType,1,BLOWER_ORIG,

BrushSpeed,1200,,

BrushMotorType,1,BRUSH_MOTOR_ORIG,

SideBrushType,1,SIDE_BRUSH_NONE,

WheelPodType,1,WHEEL_POD_ORIG,

DropSensorType,1,DROP_SENSOR_ORIG,

MagSensorType,1,MAG_SENSOR_ORIG,

WallSensorType,1,WALL_SENSOR_ORIG,

Locale,1,LOCALE_USA,

LDS Software,V2.6.15295,0000000000,

LDS Serial,

LDS CPU,F2802x/c001,,

MainBoard Vendor ID,543,,

MainBoard Serial

BootLoader Software,18119,P,p

MainBoard Software,18077,1,

MainBoard Boot,16219,

MainBoard Version,4,0,

ChassisRev,2,,

UIPanelRev,1,,

testmode on

testlds cmd getversion

Sending getversion...

getversion


GetVersion...3 ESCs or BREAK to abort...:)

Piccolo Laser Distance Scanner

Copyright (c) 2009-2011 Neato Robotics, Inc.

All Rights Reserved



Loader V2.5.15295

CPU F2802x/c001

Serial

LastCal [5371726C]

Runtime V2.6.15295

OK

#testmode off

getschedule

Schedule is Enabled

Sun 00:00 - None -

Mon 13:45 H

Tue 00:00 - None -

Wed 00:00 - None -

Thu 10:30 H

Fri 10:30 H

Sat 00:00 - None -

getwarranty

0006d012

0145

b5d4a56b

gettime

Tuesday 19:39:31



--N34T0HGQHP--


}

DataSize:[1796]
[3/3 19:38:25] httpPost - SendRequest returned status code = 200
[3/3 19:38:25] ************ Neato Upgrader Ended - ret code = 0 *****************

[3/3 19:38:36] ********************* Neato Upgrader Started *********************
[3/3 19:38:36] Upgrader Build Number: [NeatoUpgrader 3.0.24118]
[3/3 19:38:36] USING 8KB BLOCKS TO WRITE DATA TO THE ROBOT
[3/3 19:38:36] App executed from [C:\Program Files\Neato Robotics\NeatoUpgrader.exe]
[3/3 19:38:36] Log file = [C:\Users\bea\AppData\Local\NeatoUpgrader\Logs\NeatoUpgrader.log]
[3/3 19:38:36] Windows OS version. Major: [6], Minor: [1]
[3/3 19:38:36] Command line: ["neato://www.neatoroboticsupdates.com/CommandScripts/step_upload.txt?reply-to=http://www.neatoroboticsupdates.com/UpgradeResults.aspx?ID=757d83a7-8fdd-499f-8dde-7fcd2939323d&step=upload&fname=XV11App.Prod.Box.24079.enc&osver=18755&oldsver=15295&nsver=24079&nldsver=15295&os=win7&ut=1&modelid=XV14&cr=2&hardwarename=Binky&commandscript=step_fetch_Binky_3_1_nosetconfig.txt&lang=undefined"]
[3/3 19:38:36] RunMain Reply Url [http://www.neatoroboticsupdates.com/UpgradeResults.aspx?ID=757d83a7-8fdd-499f-8dde-7fcd2939323d&step=upload&fname=XV11App.Prod.Box.24079.enc&osver=18755&oldsver=15295&nsver=24079&nldsver=15295&os=win7&ut=1&modelid=XV14&cr=2&hardwarename=Binky&commandscript=step_fetch_Binky_3_1_nosetconfig.txt&lang=undefined]
[3/3 19:38:36] Script file HTTP URL = [http://www.neatoroboticsupdates.com/CommandScripts/step_upload.txt]
[3/3 19:38:36] Reply Url [http://www.neatoroboticsupdates.com/UpgradeResults.aspx?ID=757d83a7-8fdd-499f-8dde-7fcd2939323d&step=upload&fname=XV11App.Prod.Box.24079.enc&osver=18755&oldsver=15295&nsver=24079&nldsver=15295&os=win7&ut=1&modelid=XV14&cr=2&hardwarename=Binky&commandscript=step_fetch_Binky_3_1_nosetconfig.txt&lang=undefined]
[3/3 19:38:36] Downloading script file [http://www.neatoroboticsupdates.com/CommandScripts/step_upload.txt]...
[3/3 19:38:36] Script file downloaded successfully. Executing commands...
[3/3 19:38:36] Run: [send getversion]
[3/3 19:38:36] Robot connected on: [COM7]
[3/3 19:38:36] Returned: [OK]
[3/3 19:38:36] Script execution complete.
[3/3 19:38:36] Posting status to Reply URL...
[3/3 19:38:36] Url:
{
http://www.neatoroboticsupdates.com/Upg ... =undefined
}
ContentType:[multipart/form-data, boundary=N34T0HGQHP]
Body:
{
--N34T0HGQHP

Content-Disposition: form-data; name="Version"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 23



NeatoUpgrader 3.0.24118

--N34T0HGQHP

Content-Disposition: form-data; name="Log"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 4



OK



--N34T0HGQHP

Content-Disposition: form-data; name="Robot"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 727



getversion

Component,Major,Minor,Build

ModelID,-1,XV14,

ConfigID,2,,

Serial

Software,3,2,18755

BatteryType,1,NIMH_12CELL,

BlowerType,1,BLOWER_ORIG,

BrushSpeed,1200,,

BrushMotorType,1,BRUSH_MOTOR_ORIG,

SideBrushType,1,SIDE_BRUSH_NONE,

WheelPodType,1,WHEEL_POD_ORIG,

DropSensorType,1,DROP_SENSOR_ORIG,

MagSensorType,1,MAG_SENSOR_ORIG,

WallSensorType,1,WALL_SENSOR_ORIG,

Locale,1,LOCALE_USA,

LDS Software,V2.6.15295,0000000000,

LDS

LDS CPU,F2802x/c001,,

MainBoard Vendor ID,543,,

MainBoard Serial

BootLoader Software,18119,P,p

MainBoard Software,18077,1,

MainBoard Boot,16219,

MainBoard Version,4,0,

ChassisRev,2,,

UIPanelRev,1,,



--N34T0HGQHP--


}

DataSize:[1205]
[3/3 19:38:36] httpPost - SendRequest returned status code = 200
[3/3 19:38:36] Run: [reply-to http://www.neatoroboticsupdates.com/Upg ... cr=2&cid=2]
[3/3 19:38:36] Returned: [OK]
[3/3 19:38:36] Run: [send SetLanguage None]
[3/3 19:38:36] Robot connected on: [COM7]
[3/3 19:38:37] Returned: [OK]
[3/3 19:38:37] Run: [get http://www.neatoroboticsupdates.com/Com ... .24079.enc]
[3/3 19:38:41] Returned: [OK]
[3/3 19:38:41] Run: [wait 5000]
[3/3 19:38:46] Returned: [OK]
[3/3 19:38:46] Run: [send testmode on]
[3/3 19:38:46] Robot connected on: [COM7]
[3/3 19:38:47] Returned: [OK]
[3/3 19:38:47] Run: [send-nowait setsystemmode PowerCycleCDC]
[3/3 19:38:47] Robot connected on: [COM7]
[3/3 19:38:47] Returned: [OK]
[3/3 19:38:47] Run: [wait 22000]
[3/3 19:39:09] Returned: [OK]
[3/3 19:39:09] Run: [upload code reboot]
[3/3 19:39:09] Robot connected on: [COM7]
[3/3 19:39:09] sendFile - file size = 4784128 bytes
[3/3 19:39:13] Writing checksum = 609966723
[3/3 19:39:13] Sending file to robot took: 1 seconds
[3/3 19:39:13] INFO - ACK Char 15[3/3 19:39:13] INFO - ACK Char 1a[3/3 19:39:13] INFO - ACK Char 1a[3/3 19:39:13] INFO - ACK Char 1a[3/3 19:39:13] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:14] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:15] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:16] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:17] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:18] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:19] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:20] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:21] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:22] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:23] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:24] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:25] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:26] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:27] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:28] INFO - ACK Char 1a[3/3 19:39:29] INFO - ACK Char 1a[3/3 19:39:29] ERROR - sendFile timed out while reading ACK
[3/3 19:39:29] Exiting doUpload with success
[3/3 19:39:29] Returned: [OK]
[3/3 19:39:29] Run: [wait 25000]
[3/3 19:39:54] Returned: [OK]
[3/3 19:39:54] Run: [wait 9000]
[3/3 19:40:03] Returned: [OK]
[3/3 19:40:03] Run: [send getversion]
[3/3 19:40:03] Robot connected on: [COM7]
[3/3 19:40:03] Returned: [OK]
[3/3 19:40:03] Script execution complete.
[3/3 19:40:03] Posting status to Reply URL...
[3/3 19:40:03] Url:
{
http://www.neatoroboticsupdates.com/Upg ... cr=2&cid=2
}
ContentType:[multipart/form-data, boundary=N34T0YAEMU]
Body:
{
--N34T0YAEMU

Content-Disposition: form-data; name="Version"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 23



NeatoUpgrader 3.0.24118

--N34T0YAEMU

Content-Disposition: form-data; name="Log"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 44



OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK



--N34T0YAEMU

Content-Disposition: form-data; name="Robot"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 815



SetLanguage None

UI Language: None

testmode on

Upload code reboot Size 4784132

getversion

Component,Major,Minor,Build

ModelID,-1,XV14,

ConfigID,2,,

Serial

Software,3,2,18755

BatteryType,1,NIMH_12CELL,

BlowerType,1,BLOWER_ORIG,

BrushSpeed,1200,,

BrushMotorType,1,BRUSH_MOTOR_ORIG,

SideBrushType,1,SIDE_BRUSH_NONE,

WheelPodType,1,WHEEL_POD_ORIG,

DropSensorType,1,DROP_SENSOR_ORIG,

MagSensorType,1,MAG_SENSOR_ORIG,

WallSensorType,1,WALL_SENSOR_ORIG,

Locale,1,LOCALE_USA,

LDS Software,V2.6.15295,0000000000,

LDS

LDS CPU,F2802x/c001,,

MainBoard Vendor ID,543,,

MainBoard Serial

BootLoader Software,18119,P,p

MainBoard Software,18077,1,

MainBoard Boot,16219,

MainBoard Version,4,0,

ChassisRev,2,,

UIPanelRev,1,,



--N34T0YAEMU--


}

DataSize:[1334]
[3/3 19:40:03] httpPost - SendRequest returned status code = 200
[3/3 19:40:03] Run: [reply-to http://www.neatoroboticsupdates.com/Upg ... cr=2&cid=2]
[3/3 19:40:03] Returned: [OK]
[3/3 19:40:03] Run: [send SetConfig ModelID XV14 ConfigID 2 BatteryType NIMH_12CELL BlowerType 1 BrushSpeed 1200 BrushMotorType 1 SideBrushType SIDE_BRUSH_NONE WheelPodType 1 DropSensorType 1 MagSensorType 1 WallSensorType 1 ChassisRev 2 UIPanelRev 1 Locale 1 ]
[3/3 19:40:03] Robot connected on: [COM7]
[3/3 19:40:03] Returned: [OK]
[3/3 19:40:03] Run: [send testmode on]
[3/3 19:40:03] Robot connected on: [COM7]
[3/3 19:40:03] Returned: [OK]
[3/3 19:40:03] Run: [send-nowait setsystemmode hibernate]
[3/3 19:40:03] Robot connected on: [COM7]
[3/3 19:40:03] Returned: [OK]
[3/3 19:40:03] Run: [wait 10000]
[3/3 19:40:13] Returned: [OK]
[3/3 19:40:13] Run: [send getversion]
[3/3 19:40:13] Robot connected on: [COM7]
[3/3 19:40:14] Returned: [OK]
[3/3 19:40:14] Script execution complete.
[3/3 19:40:14] Posting status to Reply URL...
[3/3 19:40:14] Url:
{
http://www.neatoroboticsupdates.com/Upg ... cr=2&cid=2
}
ContentType:[multipart/form-data, boundary=N34T0DFLNL]
Body:
{
--N34T0DFLNL

Content-Disposition: form-data; name="Version"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 23



NeatoUpgrader 3.0.24118

--N34T0DFLNL

Content-Disposition: form-data; name="Log"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 24



OK

OK

OK

OK

OK

OK



--N34T0DFLNL

Content-Disposition: form-data; name="Robot"

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Length: 1442



SetConfig ModelID XV14 ConfigID 2 BatteryType NIMH_12CELL BlowerType 1 BrushSpeed 1200 BrushMotorType 1 SideBrushType SIDE_BRUSH_NONE WheelPodType 1 DropSensorType 1 MagSensorType 1 WallSensorType 1 ChassisRev 2 UIPanelRev 1 Locale 1

ConfigID = 2 (Illegal value (2) for Enum type ESCBConfigID.)

BatteryType = 1 (NIMH_12CELL)

WheelPodType = 1 (WHEEL_POD_ORIG)

DropSensorType = 1 (DROP_SENSOR_ORIG)

MagSensorType = 1 (MAG_SENSOR_ORIG)

WallSensorType = 1 (WALL_SENSOR_ORIG)

Locale = 1 (LOCALE_USA)

UIPanelRev = 1 (UI_PANEL_ORIG)

ChassisRev = 2 (CHASSIS_LOWERED_DROP)

BlowerType = 1 (BLOWER_ORIG)

BrushMotorType = 1 (BRUSH_MOTOR_ORIG)

SideBrushType = 1 (SIDE_BRUSH_NONE)

BrushSpeed = 1200

testmode on

getversion

Component,Major,Minor,Build

ModelID,-1,XV14,

ConfigID,2,,

Serial

Software,3,2,18755

BatteryType,1,NIMH_12CELL,

BlowerType,1,BLOWER_ORIG,

BrushSpeed,1200,,

BrushMotorType,1,BRUSH_MOTOR_ORIG,

SideBrushType,1,SIDE_BRUSH_NONE,

WheelPodType,1,WHEEL_POD_ORIG,

DropSensorType,1,DROP_SENSOR_ORIG,

MagSensorType,1,MAG_SENSOR_ORIG,

WallSensorType,1,WALL_SENSOR_ORIG,

Locale,1,LOCALE_USA,

LDS Software,V2.6.15295,0000000000,

LDS

LDS CPU,F2802x/c001,,

MainBoard Vendor ID,543,,

MainBoard Serial

BootLoader Software,18119,P,p

MainBoard Software,18077,1,

MainBoard Boot,16219,

MainBoard Version,4,0,

ChassisRev,2,,

UIPanelRev,1,,



--N34T0DFLNL--


}

DataSize:[1942]
[3/3 19:40:14] httpPost - SendRequest returned status code = 200
[3/3 19:40:14] ************ Neato Upgrader Ended - ret code = 0 *****************
mmm2000
 
Posts: 29
Joined: February 8th, 2015, 3:14 am

Re: Neato upgrade fails

Postby glnc222 » March 4th, 2015, 12:37 am

Looks accumulating all updates, not just latest. Can't see edited marks to show where interrupted.
I notice one line after a big data block:
[3/3 19:39:29] Exiting doUpload with success

suggesting flashed something. Maybe it is flashing the same old version again?
I notice replies to a URL given. If that web address isn't responding that could hang up something.
Some of the older reports apply to difficulty communicating with the website over local WiFi networks instead of direct connection to the modem. Fussy website. (Vorwerk supposedly does this more correctly with downloads of the firmware and robot comm independent of website. Yet the log shows script downloads.)
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby vic7767 » March 4th, 2015, 12:59 am

There was another post in this forum that has the 3.4 flash contained in a file that can be used to flash your Neato if it is the Rev 64 board. For some reason I can't find it right now but you might try using the advanced search option. There were also the 3.0 and 3.1 file folders so you could go back to earlier versions.
Roomba and Neato Mods, come visit: http://www.vic7767.com/

http://www.Robot-Doc.com/
User avatar
vic7767
Robot Master
 
Posts: 14408
Joined: January 14th, 2006, 8:31 pm
Location: Haughton Louisiana - USA

Re: Neato upgrade fails

Postby Lewiy » March 4th, 2015, 1:42 am

mmm2000
In your log -- Sending file to robot took: 1 seconds. Seems too quick. It takes 12 sec on my unit. Probably the firmware file (4784128 bytes) is not sent to unit completely, but the updater tool receives the wrong signal about the successful update from the robot. Try to ask in support and send them the log.
Lewiy
Robot Master
 
Posts: 143
Joined: September 27th, 2014, 3:33 am

Re: Neato upgrade fails

Postby mmm2000 » March 4th, 2015, 1:51 am

Lewiy wrote:mmm2000
In your log -- Sending file to robot took: 1 seconds. Seems too quick. It takes 12 sec on my unit. Probably the firmware file (4784128 bytes) is not sent to unit completely, but the updater tool receives the wrong signal about the successful update from the robot. Try to ask in support and send them the log.


Yeh, I will be trying to send them (manufacturer) the log and see what they say... I was hoping someone can pinpoint the issue and maybe a fix.

One second for a 4MB files does seem too fast at first, but at the same time the theoretical speed for the 2.0 usb is about 60MB/s, so sending that file in one second might be within normal limits. My computer is 1 year old only. But I am not sure how fast the robot board can receive. They say to use a 2.0 USB cable.

But at the same time you can see that is sending some packets for about 15 seconds then it stops with the "error sending file time out"
mmm2000
 
Posts: 29
Joined: February 8th, 2015, 3:14 am

Re: Neato upgrade fails

Postby glnc222 » March 4th, 2015, 2:13 am

The offline updating files are in the version 3.4 thread (linked as a continuation of this updating thread)
http://www.robotreviews.com/chat/viewtopic.php?p=127302#p127302

[edit]Caution old Rev 113 system boards (units with side charging jacks and old LCD clamped cable instead of plug), cannot be updated beyond version 3.1. The website registration procedure prevents going further but not the hacked offline stuff. Loading later versions will destroy the system's ability to correct, re-flash: toast.

I'd consider it a risky business except in the hands of experts (of which many participate here). Flashing software the wrong way, in the wrong kind of system, might disable the parts needed to flash, and it's toast. Hopefully they used a robust design. It does have dual copies and some sort of reversion feature, though I notice that is supposed to not work in newer boards at least by the old buttons.

Some users getting interruptions traced them to faulty USB cables. Had that with a Kindle once. Delicate things they are (at least the spring wind up ones). NeatoControl Program should show if good.

Reverting to Prior Software Version
Per other posts a temporary reversion to a backup copy of the previous software is possible, until the system is later rebooted. On older Rev113 boards (units with side charging jacks) hold down the "back" and "start" button together for a few seconds. In rev64 boards you should press the left bumper corner to the center direction (both micro switches -- front and side -- should be pressed) instead of BACK button. It might take 30 seconds for reboot.
Last edited by glnc222 on March 16th, 2015, 10:32 pm, edited 2 times in total.
glnc222
Robot Master
 
Posts: 4613
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: Neato upgrade fails

Postby Lewiy » March 4th, 2015, 3:32 am

mmm2000 wrote:One second for a 4MB files does seem too fast at first, but at the same time the theoretical speed for the 2.0 usb is about 60MB/s

May be the flash memory, on which the firmware must be saved, limits the file transfer speed.
You can try to connect to another USB port. After the command -- setsystemmode PowerCycleCDC -- the Neato main processor switches to DFU-mode (for receiving the firmware from PC). This changes the comm port number. On your case it does not, it looks strange.
Lewiy
Robot Master
 
Posts: 143
Joined: September 27th, 2014, 3:33 am

Re: Neato upgrade fails

Postby JohnGalt » March 7th, 2015, 11:09 am

Solved it for my machine, please send me my "You're only stupid if you don't figure out your mistake" award. I've been wrestling with this problem off and on for about a year and a half on XP and Win 7 64 bit with 2 different AMD based motherboards.

Long story short, I had tried every USB port my computer has - on the front panel. Yeah, you know where this is going. Imagine my embarrassment when I tried someone's advice from this forum and hooked it up to my USB3 port in back directly attached to the motherboard. Well, no, it didn't work via the USB 3 port, but when I switched to a neighboring USB2 port on the motherboard, Bingo!! everything worked fine. Hopefully this helps at least one other person.
JohnGalt
 
Posts: 1
Joined: March 7th, 2015, 11:02 am

PreviousNext

Return to Neato Robotics

Who is online

Users browsing this forum: a1robotrepair, aarolar and 467 guests