I am trying to use kinect v2 with turtlebot and am following this tutorial. Everything works fine except when I enter the command
roslaunch kobuki_slam kobuki_slam.launch
This gives an error namely
[ERROR] [1509445234.825467518]: Error connecting to Hokuyo: Could not open serial Hokuyo: /dev/ttyACM0 # 115200 could not open serial device.
Do you have any idea why I might be getting this error?
Thanks!
Related
I can't print with Kyocera Taskalfa 2200 on my archlinux, it has worked before but now its showing "idle rendering complete" and on localhost its saying "stopped filter failed".
I have deleted and added the printer again multiple times and reinstalled the drivers using yay as well.
any suggestions???
I get this warning when trying to add the printer
In local host it says filter has failed
in queue it says stopped
I've followed the Vapor tutorial to create a hello app. In Xcode, when I run the Run scheme on my Mac, the app starts and runs as I can see by opening http://localhost:8080/. After making some changes in the code, I stop the Run scheme and I expect the Vapor server to shutdown. However, it continues to serve requests.
Message from debugger: The LLDB RPC server has exited unexpectedly. Please file a bug if you have reproducible steps.
Program ended with exit code: -1
Obviously when I make some changes and run the Run scheme again, I get the following runtime error:
Swift/ErrorType.swift:200: Fatal error: Error raised at top level: bind(descriptor:ptr:bytes:) failed: Address already in use (errno: 48)
Program ended with exit code: 9
How do I stop or restart the server?
This is a long standing issue with Xcode/LLDB. You have a few options:
attach to the process and stop it via Xcode
run killall Run
run lsof -i :8080 to find the process connected to port 8080 and then kill <process_id> (this is useful if you're running multiple apps side by side and only want to terminate the orphaned one)
This is quite frustrating and to be honest I dont know why this happens, but I do the following to terminate the process:
In Xcode,
Go to Debug -> Attach to Process
At the very top of the sub-menu is: Likley targets section with an entry Run (nnnn). It will have an icon of the Terminal application
Click to attach
Then stop the Xcode Run in the usual way.
Out of interest, the next time you run your vapor app, if you open the Debug Navigator, at the top you will see the Terminal icon with Run PID nnnn. Where nnnn is the PID. If you go to Debug -> Attach to Process again, you can see this at the top of the sub-menu as before. But you wont be able to attach to it because it is already being debugged.
Hope this helps you or someone in the future.
I get the following error when trying to open my expo project on my iPhone:
There was a problem running the requested app. It looks like you may be using a LAN URL Make sure your device is on the same network as the server or try using a tunnel
Both my phone and laptop are connected to the same WiFi connection.
I'm not sure what I did wrong. All I have done so far is run the following commands:
npm install expo-cli --global
expo init rn-first-app
npm start
Does your URL look like this: exp://192.168.1.2:19000 ?
as opposed to this: exp://84-gd6.malfuckingfurion.rn-first-app.exp.direct:80
If so try this:
expo start --tunnel
Or this:
expo start -m tunnel
I'm a ESP8266 beginner, and I have a ESP8266 devkit. I flash it with esptools and use ESPlorer as IDE.
I classically made the infinite loop error, but I manage to get out of it by erasing flash (erase_flash command from esptools) on whole flash memory (including user space).
To avoid this again, I made the following code
init.lua
dofile('crazy-guard.lua')
crazy-guard.lua
gpio.mode(0,gpio.INPUT)
programPinValue = gpio.read(0)
if(programPinValue == 0) then
print("program mode")
return
else then
print("run mode")
dofile('program.lua')
end
program.lua
while true do
end
This is working as expected : if I low GPIO0, I get "program mode" written on ESPlorer console when I establish connection. If set hig, I get the "run mode" message.
I thought that the return instruction on program mode block (GPIO0 low) would allow me to communicate with my ESP8266 dev kit (editing .lua files) but since I uploaded this code, I can't get any connection on my board... esptools return :
sudo python ./esptool.py erase_flash
esptool.py v2.4.1
Found 1 serial ports Serial port /dev/ttyUSB0
Connecting........_____....._____....._____....._____....._____....._____....._____
/dev/ttyUSB0 failed to connect: Failed to connect to Espressif device:
Timed out waiting for packet header
One the ESPlorer side, here is what I get :
PORT OPEN 115200
Communication with MCU..Got answer! Communication with MCU
established. AutoDetect firmware...
Can't autodetect firmware, because proper answer not received (may be
unknown firmware). Please, reset module or continue.
l�d����#�n�l�#|���2�{���b��no�lNn���cp��$rdrlp�n��dbN�|��䎟�c��oN�d���$�no�s$or���Nrld
p�n�r�����bN��o�l�p��on���l �oN�ln{���o�l
p�N�r�����bN�|l섎p��on���l
�no�{lNs�����{${��o�{$����n�{��n|�lll$b��|{�l�n��n��l��r�l�$�$��{�l�$�l��{�l���dlrl��o��bc��cp|"p���p����lB��N�Nn��ld��l���d��$����$��d
�n�����bl$��2b���"l�crlr
NodeMCU custom build by frightanic.com branch: master commit:
5073c199c01d4d7bbbcd0ae1f761ecc4687f7217 SSL: false modules:
file,gpio,http,i2c,mqtt,net,node,ow,tmr,uart,wifi build built on:
2018-03-22 17:00 powered by Lua 5.1.4 on SDK 2.1.0(116b762)
program mode
Then if I try any command over USB via ESPlorer, or pushing any file edit/creation, I get :
Waiting answer from ESP - Timeout reached. Command aborted.
As far as I can see, my devkit seems bricked. How can I reprogram it? I tried to change bauds, but the NodeMCU header with firmware details makes me think that hardware communication is correctly set.
I need to work with asus xtion pro live to detect hand movements and objects. I am an amateur as far as it concerns programming this camera.
My problem is how to connect them and from where to start.
I work on Ubuntu 12.04. I've downloaded Ros fuerte and both Openni2 and OpenCV. When i plug the camera (usb port) and run the lsusb command, i see this:
"Bus 001 Device 003: ID 1d27:0601 "
Even when i run the command $ roslaunch openni_launch openni.launch
i get:
[ INFO] [1415717730.873978521]: No matching device found.... waiting for devices. Reason: openni_wrapper::OpenNIDevice::OpenNIDevice(xn::Context&, const xn::NodeInfo&, const xn::NodeInfo&, const xn::NodeInfo&, const xn::NodeInfo&) # /tmp/buildd/ros-fuerte-openni-camera-1.8.6/debian/ros-fuerte-openni-camera/opt/ros/fuerte/stacks/openni_camera/src/openni_device.cpp # 61 : creating depth generator failed. Reason: USB interface is not supported!
Can anyone please help? Is there a problem with the camera driver?
Thank you in advance.
you must go to a terminal and do
sudo nano /etc/openni/GlobalDefaults.ini
and there find UsbInterface and make sure it is not a comment (without ; at the beginning) and that is equal to 2
UsbInterface=2
I heard that this may give you problems with Kinect hardware (the same error you are getting now). But, if you use the Kinect later on and gives this problem, just comment it and it should work
;UsbInterface=2
You must reboot every time you change this value!!
I hope this works for you ;)