The Aldebaran NAO robot suddenly stop moving. It boots properly, and can be accessed webpage and Choregraphe.
However, it shows the strange posture as attached photo, and never moves it's motors.
Tried hard reset, and re-install naoqi, but no luck yet.
Any recommendation for resolving this strange issue?
It seems your robot is decalibrated.
You will need to contact to the support.
Related
I've just started working with NAO on Choreographe and I would like to know if there is a possible way to run behaviors without PC. Can I upload some behaviors to NAO and start running without pressing the run button on Choreographe?
Sure you can !
In Choreographe, find the "robot application" widget and then you can upload your program and define it as a "start at boot" program.
Here's a video showing that:
https://www.youtube.com/watch?v=w9RFkpI4vjo
I have Ubuntu 18.04 installed on my HP laptop. This morning after restart it wasn't able to find my second monitor, which is connected via HDMI. I had those issues before, and fixed them by restarting multiple times, connecting HDMI to my TV etc, but this time it did not work.
I have found the answer on stackoverflow to switch to lightdm as a solution to my problem. I installed lightdm with apt-get, ran sudo dpkg-reconfigure lightdm and restarted the computer.
New appearence was there, other monitor on HDMI was also there. I encountered next problems :
My battery indicator was not showing how much I have left (stuck at 48%) and wasnt showing when I plug charger that it is charging
Title buttons were on the left side of windows, which is not what I am accustomed to since I also have other computer running Windows.
So I started googling to fixing that, I have Tweaks installed, but when selecting right/left position it only affected the Tweaks window, others were still with buttons on left side. I have tried (found it on stackoverflow also)
gsettings set org.gnome.desktop.wm.preferences button-layout ':minimize,maximize,close'
which didnt have the effect, also found on some answer
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/DecorationLayout':<':minimize,maximize,close'>}"
but that also didnt work, the title buttons were still on the left side.
After that I completely removed lightdm, purged, restarted, gdm3 login screen appeared but the desctop appearence was the same as when using lightdm, still battery icon issue and still buttons on the left side. I have tried than installing lightdm and removing/purging gdm3 but the issue remained the same.
Help would be appreciated, since I cannot just accept buttons on the left side and ignore battery icon, and reinstalling OS would be super painful since I have tons of stuff set (I use laptop for sotware development)
I'm working with two Nao robots. Their speech recognition abilities have been working alright so far, but recently they just stopped working altogether.
I am using Choregraphe and I can enter words in the dialog box and the robot will respond as intended, but when I speak out words, the robot will either not even recognize words being spoken, or will just display: Human: <...> and that's it. I have tried using autonomous life on and off, creating a simple dialog that only has one line of functionality, like: "u:(_*) Hello.", and it doesn't do anything.
In autonomous life mode the robot's eyes go blue and Nao nods occasionally as if it would hear words, but I get no response and see nothing in the console.
The robot I have is Nao model 6 (the dark grey one and as far as I know the newest model).
However if I use a speech recognition box, Nao will understand the spoken words, just not in the dialog. Do you have any idea what's going on here?
Hi i had a simmilar issue with Pepper.
I also encountered recognition stopping to work.
In my Choregraph log I had:
[WARN ] Dialog.StrategyRemote.personalData :prepare:0 FreeSpeechToText is not available
So the support let me know that:
The problem you observed happened because Pepper got a timeout from
the Nuance Remote server, she will consider that the server is
unavailable and will not try to contact it again for one hour (during
which Free Speech will not work). This could be because the server is
indeed unavailable, or because of network issues.
Fortunately to workaround a bad network you can change those
parameters, with ALSpeechRecognition.setParameter(parameter_name,
parameter_value)
The parameters that will interest you are:
RemoteTimeout: How long Pepper waits for a response from the Nuance
Remote server, in milliseconds. Default value: 10000.0 (ms)
RemoteTryAgain: Number of minutes before trying to use Nuance Remote
again after a timeout. Default value: 60.0 (minutes)
Note that you will need to reset those values again after each boot.
Maybe that can also help you with Nao.
Also I learned that the Remote ASR seems to have a limit of about 200-250 invocations per day.
I am working on a project for NAO recording and I am trying to analyse the sound data. I set the head yaw as well as the pitch angle to a specified degree first and then start the recording process. A problem comes when somebody is facing to its camera, it will move its head and face to the person which is really annoyed .
It seems that this face contact is run in default, could anybode teach me how to blind it?
ALSO is it possible to stop the robot to shake its body when it rests?
Thankyou.
This is probably due to Autonomous Life - you can disable it from Choregraphe, from robot settings, or simply by pressing the chest button twice - see the documentation.
We are building a kiosk app and noticing some odd behavior with Google Chrome. To debug, we are monitoring all of the incoming events with monitorEvents(document); through the dev console and noticed 2 different kind of scenarios.
Eventually after a few minutes of heavy multi-finger/gesture use, we are stuck in a touchstart/touchend loop where touchend does not propagate down to a mouse/click event (breaking our app as we only handle onClick). It is continuously stuck in touchstart-touchend-touchstart-touchend for every finger click.
A continuation of scenario 1 with heavier use, we are getting absolutely no events in the console, not even a touchstart.
We are using Chrome 62 with Windows 10 with the following flags:
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --kiosk --incognito --disable-pinch --overscroll-history-navigation=0 URL
We have tried to add --touch-events, add --disable-gpu, remove our previous flags, but still facing the same issue. It seems to be an issue between Chrome and Windows as we are able to replicate it on google.com (with getting no events). When we plug in a mouse, we are able to click the buttons so the app is not frozen, we are just not getting any touch events (only mouse works at this point). Touch is still working on the Windows and Chrome App level, just not our app viewport.
The kiosk is a Dell All-in-One machine. Has anyone else experienced this kind of issue?
Thanks!
UPDATE: Using Chrome 68+ I no longer have this issue. I have not tried versions between 62 and 68 to see where it was fixed but I am glad that it is!
It is a little late now, but maybe this will bring some closure. I experienced the same problem and like you, only in Chrome. The best I could determine was that this glitch is dependent on a particular model of touchscreen in the computer.
Check the hardware IDs for the touchscreen in Device Manager. Only the Inspiron 20-3059 models with a touchscreen made by Advanced Silicon (VID_2149&PID_4C39) exhibit this behavior. Other 20-3059 models with a different touchscreen model (VID_0457&PID_1192) work fine.
Oddly enough, later Inspiron 20-3064 models also work fine, though they also had Advanced Silicon touchscreens. The PID was increased to 4C3E so perhaps they discovered this issue and fixed it for the newer model.
I wasn't able to find any combination of driver/firmware/Chrome versions that would fix the problem, but this is as close to a root cause as I could get.