NeatoControl - program for diagnostic neato robots

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

Re: NeatoControl - program for diagnostic neato robots

Postby heX » April 29th, 2015, 10:25 am

Apollon wrote:It is possible to activate Wifi via USB terminal commands and connect it to a wifi network. There the VR200 listens on port 49001. If you try to connect to that port, the Display of the VR200 shows a message that "App control" is active and the motor starts. However it is not possible to send commands via telnet as the connection immediately gets lost. I have no idea how the api could look like, there's no documentation.

This interesting information. But without instance robot (or official manual), I can not do anything. :(
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

Re: NeatoControl - program for diagnostic neato robots

Postby glnc222 » May 5th, 2015, 10:31 pm

monitoring multi-charge runs

One user observed that when Neato Control runs with the Neato docked, memory of the status within a series of runs for a single cleaning with multiple charging cycles is erased. Understandable as a possible effect of using Test Mode, which is incompatible with cleaning operation (motor control is handed over to test commands instead of cleaning algorithms). The program features required for monitoring cleaning instead of testing equipment may have to be discovered with experience. The wireless connections needed are not in widespread use, and are just particular user's construction projects.
glnc222
Robot Master
 
Posts: 4538
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: NeatoControl - program for diagnostic neato robots

Postby glnc222 » May 21st, 2015, 2:57 pm

Possible Test Mode issues
A German user reported on the VR100 the program shows the sensors but does not display the LDS scan. It appeared that Test Mode was not set on and the lidar spinning command not operating. There might be a bug related to turning Test Mode on and off in recent versions of the program with changes to how the mode is handled. This problem ought to affect Neato models equally. Sensor readout does not require Test Mode. Motor operation requires Test Mode. Test Mode must be terminated before disconnecting the USB. Many procedures are possible to handle this complication and some attempts to improve it were mentioned.
Try older versions if this problem with the Lidar occurs. The only other problem I could imagine is Vorwerk models using German language for USB commands and responses and only the display labeling employed the language selection feature from Microsoft.

Sensor Readings and Test Mode
Lewiy in http://www.robotreviews.com/chat/viewtopic.php?f=20&t=18596#p131179
Without TestMode 'GetAnalogSensors ' gets static sensors values, the dimension of which is unknown (as Brett shows). In TestMode the same command gets the sensors values in the proper dimension (e.g. for WallSensor -- mm) and with proper reaction to obstacle. Finally, 'GetAnalogSensors raw' in TestMode gets the sensors values in mV.
glnc222
Robot Master
 
Posts: 4538
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: NeatoControl - program for diagnostic neato robots

Postby java-jim » July 8th, 2015, 4:17 pm

Apollon wrote:It is possible to activate Wifi via USB terminal commands and connect it to a wifi network. There the VR200 listens on port 49001. If you try to connect to that port, the Display of the VR200 shows a message that "App control" is active and the motor starts. However it is not possible to send commands via telnet as the connection immediately gets lost. I have no idea how the api could look like, there's no documentation.
Apollon.


@Apollon
Hi Apollon, i got yesterday an used VR200. I already read that it´s possible to activate the wlan on the device, but i cánt find an option in the menustructure. How can i let the robot join my accesspoint? My FW Ver is the latest 1.4.21

I also read that a user on the german forum was one of the 500 betatester for the iPhone App which is not available in the appstore. He said, that it really slow, because there is no direct communication to the device. The device connects to a vorwerk server and the app too. probably it is possible to redirect that traffic to a local service. i would have a look via wireshark and mitm proxy.

@HeX
I would be also interested in a support for VR200 via WiFi.
If i could join my ap, i could open a vpn to the device to the developer, for inspecting the IP communication...
java-jim
 
Posts: 3
Joined: July 8th, 2015, 3:46 pm

German language file for version 1.8

Postby java-jim » July 8th, 2015, 4:28 pm

Target = NeatoControl
Autor = Java-Jim
LANGID = 1031

[FrmMain]
00000001 = Neato Control
00000003 = Einstellungen
00000004 = Nachfolger Wand:
00000006 = Ein.
00000007 = Aus.
00000008 = Wochenplan
00000011 = Zeitplan:
00000014 = Tag\nZeit
00000018 = Aktiviert
00000019 = Deaktiviert
00000020 = Geräte-Verbindung
00000021 = COM-Port-Nummer:
00000025 = automatische Port-Erkennung
00000026 = automatisch verbinden
00000028 = Version:
00000031 = Sensoren
00000035 = Sensor\nWert\n
00000036 = Scanner
00000037 = Bedientasten
00000042 = Verbinden
00000043 = Trennen
00000044 = Sprache:
00000046 = Zeitplan speichern
00000047 = Zeitplan laden
00000048 = Zeitplan am Computer bearbeiten
00000049 = über
00000057 = LIDAR-Scanner
00000060 = Fernsteuerung (Pfeiltasten)
00000061 = Akku Auffrischung
00000062 = über
00000080 = 100% Last
00000081 = Schalten Sie den Staubsauger Motor aus und trennen ihn
00000082 = Licht der Bürstenmotor und trennen
00000067 = Roboter-Zeit:
00000068 = 00: 00: 00
00000069 = Schritt 1:
00000070 = Schritt 2:
00000071 = Schritt 3:
00000072 = Schritt 4:
00000073 = Schritt 5:
00000084 = WARNUNG: \nAlle Aktionen erfolgen von Ihnen auf eigene Gefahr. \nWenn Sie dies nicht riskieren möchten, benutzen Sie NICHT diesen Modus - kaufen Sie einfach neue Batterien \nDer Author garantiert für nichts. - Diese Methode garantiert KEINEN Erfolg... \nDie Batterieauffrischung wird erforderlich, wenn Ihr Roboter schon nach 10-20 Minuten entladen ist. Um die Batterie systematisch wiederherzustellen, folgen Sie den Anweisungen in den folgenden Schritten. Wenn im Schritt eine Schaltfläche enthalten ist, klicken Sie diese. \nWenn Sie beim Verbindem im erscheinenden Fenster ein rotes Feld mit dem Wort "Batt V <12 V" erscheint, beenden Sie den Vorgang sofort und laden Sie den Roboter an der Basisstation. Sie können versuchen, den Vorgang zweimal zu wiederholen, um den Effekt zu verbessern.
00000085 = Schalten Sie den Reinigungsroboter ein und warten bis zur Entladung.
00000086 = Klicken Sie auf diese Schaltfläche, und schalten Sie den Reinigungsroboter ein und warten bis zu Entladung. (~ 10,5 Minuten)
00000092 = Schalten Sie den Roboter ein und klicken Sie so schnell wie möglich auf "Connect". Dann drücken Sie diese Schaltfläche - der Saugmotor startet. Warten Sie bis der Roboter von selbst aus geht. (~ 30 Minuten)
00000093 = Schalten Sie den Roboter ein und klicken Sie so schnell wie möglich auf "Connect". Dann drücken Sie die Schaltfläche - der Bürstenmotor startet. Warten Sie bis der Roboter von selbst aus geht. (~ 30 Minuten)
00000095 = Verbinden Sie den Roboter mit der Basisstation \nStellen Sie sicher, dass Sie "Service." -> "New Battery" am Gerät aufführen. \nWarten Sie bis der Roboter voll geladen ist. \nMachen Sie ein paar Reinigungsläufe vor der Beurteilung des Ergebnisses ...
00000096 = Kurzbefehle
00000143 = Hotkey Liste
00000147 = In Logdatei speichern
00000148 = Timer
00000167 = in Sekunden
[$ CONSTANT]
ErrorCantOpenPortCOM = Kann den COM-Port nicht öffnen - Port belegt. Vielleicht ist dies nicht der Anschluss oder das Programm wird bereits ausgeführt wird.
ErrorComPortNotDetect = COM-Schnittstelle wurde nicht gefunden. Verbinden Sie den Roboter. Prüfen Sie die Verfügbarkeit von "Neato Robotics USB-Port" im Geräte-Manager unter "Ports". Überprüfen Sie die Verbindung.
ErrorSetPortState = Fehler Com-Port Status(SetCommState)
Errorevent = WaitCommEvent IOResult = EV_ERR
ErrorClearPort port = Fehlerkompensation. (ClearCommError)
ErrorInvalidComPortNumber = falsche COM-Port Nummer
Monday=Montag
Tuesday=Dienstag
Wednesday=Mittwoch
hursday=Donnerstag
Friday=Freitag
Saturday=Samstag
Sunday=Sonntag
textEnabled=AN
textDisabled=AUS
java-jim
 
Posts: 3
Joined: July 8th, 2015, 3:46 pm

Re: NeatoControl - program for diagnostic neato robots

Postby Apollon » July 8th, 2015, 5:20 pm

java-jim wrote:@Apollon
Hi Apollon, i got yesterday an used VR200. I already read that it´s possible to activate the wlan on the device, but i cánt find an option in the menustructure. How can i let the robot join my accesspoint? My FW Ver is the latest 1.4.21

I also read that a user on the german forum was one of the 500 betatester for the iPhone App which is not available in the appstore. He said, that it really slow, because there is no direct communication to the device. The device connects to a vorwerk server and the app too. probably it is possible to redirect that traffic to a local service. i would have a look via wireshark and mitm proxy.


You have to connect your robot via usb to your computer. The serial driver for the vr100 or the neatos works just fine. VR100-serial driver is included in the vr-updater (http://kobold.vorwerk.de/de/service/software-updates/saugroboter/vr100/#update-box). Then you can connect via a terminal emulator to the robot on port 49001 as described here: http://www.neatorobotics.com/resources/programmersmanual_20140305.pdf It works just like with a neato robot.

Once connected to switch wifi on enter these commands in the terminal emulater:
1.) SetUserSettings WiFi ON
2.) SetWiFi enable
3.) TestMode ON
4.) SetSystemMode PowerCycle

After a reboot you have a new menu entry "configure wifi" (or similar - I only know how its called in German) where you can configure your wifi and should be able to connect to your access point.

After each reboot the robot tries to connect to vr200.ksecosys.com. However, that server seems to be down, at least not responding.

Hope that helps.

Apollon.

P.S: This information I got from here: http://www.roboter-forum.com/showthread.php?10010-VR200_Info-Menue&p=93395&viewfull=1#post93395
User avatar
Apollon
 
Posts: 8
Joined: April 25th, 2015, 1:18 pm

Re: NeatoControl - program for diagnostic neato robots

Postby java-jim » July 8th, 2015, 5:51 pm

Ausgezeichnet !
I will test it tomorrow. So it seems, that we need access to the (beta)app to capture and analyse the data...
java-jim
 
Posts: 3
Joined: July 8th, 2015, 3:46 pm

Update

Postby heX » July 26th, 2015, 9:51 am

Ver 2.0

https://bitbucket.org/heXor/neatocontro ... ol_2.0.zip

Changes:
Migrate to Lazarus!
"Sensors" tab - gray color for inactive sensor.
add new localization system!
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

Re: NeatoControl - program for diagnostic neato robots

Postby heX » July 26th, 2015, 10:01 am

java-jim wrote:@HeX
I would be also interested in a support for VR200 via WiFi.
If i could join my ap, i could open a vpn to the device to the developer, for inspecting the IP communication...

Good idea! Will have to try, but later...
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

Re: Update

Postby shirgal » July 28th, 2015, 9:03 am

heX wrote:Ver 2.0

https://bitbucket.org/heXor/neatocontro ... ol_2.0.zip

Changes:
Migrate to Lazarus!
"Sensors" tab - gray color for inactive sensor.
add new localization system!


hEX : Thank you for the update on Ver 2.0, :cheers:
hence probably due to Lazarus migration most of the tabs data now flip to the right side,
and the battery graphics percentage missing the numbers.
see what can be fixed on next version.
User avatar
shirgal
Robot Addict
 
Posts: 155
Joined: July 8th, 2013, 10:54 am

Re: NeatoControl - program for diagnostic neato robots

Postby heX » August 6th, 2015, 4:11 am

Update. Version 2.1

https://bitbucket.org/heXor/neatocontro ... ontrol.zip

Changes:
Add save same options
Add language manual change
Add German translate (NeatoControl.de.po)
Add online collective translate

You can help translate program to other languages here: https://poeditor.com/join/project/EdLcbGzBsR
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

Re: NeatoControl - program for diagnostic neato robots

Postby heX » August 14th, 2015, 9:34 am

Update. Version 2.2

Changes:
Add page "Motors"
Add page "Log"
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

Re: NeatoControl - program for diagnostic neato robots

Postby shirgal » August 14th, 2015, 1:02 pm

hex , thank you for the great update as always good one :-))),
-Link is missing from the version 2.2 post.
-I think the Motor warning tab should be more clear in English if translate like this :
"Rotate the robot so the wheels are facing up before enable wheels motor!
User avatar
shirgal
Robot Addict
 
Posts: 155
Joined: July 8th, 2013, 10:54 am

Re: NeatoControl - program for diagnostic neato robots

Postby vic7767 » August 14th, 2015, 1:37 pm

shirgal wrote:-Link is missing from the version 2.2 post.
FYI, heX always put the latest update link to NeatoControl to the first page.
Roomba and Neato Mods, come visit: http://www.vic7767.com/

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

Re: NeatoControl - program for diagnostic neato robots

Postby shirgal » August 14th, 2015, 6:25 pm

vic - thank you.

Hex,
Tested the version 2.2 with XV series and BotVac:
scan LDS function and wheels motors are both not working now with this version,
log works with xv only not for Botvac.
User avatar
shirgal
Robot Addict
 
Posts: 155
Joined: July 8th, 2013, 10:54 am

Re: NeatoControl - program for diagnostic neato robots

Postby glnc222 » August 14th, 2015, 8:59 pm

The logs do not exist in Botvac firmware, running on the new OS.
I had found the Botvac would not run motors turned upside down, from protection features built-in. Perhaps I missed some way to fool it (keep the wheel suspension compressed? There is also the accelerometer... [edit] cover cliff sensors).
glnc222
Robot Master
 
Posts: 4538
Joined: January 23rd, 2012, 9:19 pm
Location: North Carolina, U.S.

Re: NeatoControl - program for diagnostic neato robots

Postby Lewiy » August 15th, 2015, 5:04 am

shirgal wrote:scan LDS function and wheels motors are both not working now with this version.

Seems heX forgot to add `testmode on` before starting the motors. The error in the program code. You can do this manually on the Commands tab, before starting the motors. It will work. Do not forget to get out - `testmode off` after disabling the motor.
Lewiy
Robot Master
 
Posts: 143
Joined: September 27th, 2014, 3:33 am

Re: NeatoControl - program for diagnostic neato robots

Postby shirgal » August 15th, 2015, 6:00 am

[/quote]
You can do this manually on the Commands tab, before starting the motors. It will work. Do not forget to get out - `testmode off` after disabling the motor.[/quote]

I have tried this before posting, your tip as well, non works with 2.2 ver, only vacuum and brush motor works.
If i go to scanner tab i can move the robot wheels motor around, hence now the scanner screen will jump to another tab if i turn the wheels right or left instead stay in this screen.
LDS SCAN does not works either way :help:
User avatar
shirgal
Robot Addict
 
Posts: 155
Joined: July 8th, 2013, 10:54 am

Re: NeatoControl - program for diagnostic neato robots

Postby heX » August 15th, 2015, 7:02 am

Lewiy wrote:Seems heX forgot to add `testmode on` before starting the motors

thank you! (no have robot at hand - write without testing)

Update! - version 2.3 =)
Changes: bug fix
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

Re: NeatoControl - program for diagnostic neato robots

Postby heX » August 15th, 2015, 7:04 am

shirgal wrote:LDS SCAN does not works either way :help:

I will look for the cause of the error...
heX
 
Posts: 22
Joined: November 28th, 2014, 5:35 am

PreviousNext

Return to Neato Robotics

Who is online

Users browsing this forum: Harry007x1 and 354 guests