We are trying to get the Intel Realsense D435i to work on our Raspberry Pi with the Raspbian OS and ROS Melodic.
After we configured our Raspberry Pi with Raspbian and installed ROS Melodic on it, we installed the realsense-ros package on our Raspberry Pi. When we connect our Realsense camera to the Raspberry and run the following command:
$ roslaunch realsense2_camera rs_camera.launch
We get the following error:
error: Time is out of Dual 32-bit range
We get some ros topics from the camera but they don't publish any data. Also not all of the topics are displayed. When we plug the camera in to a pc it works fine.
We already googled it and tried the following:
full clean and rebuild of catkin workspace
update and upgrade of all ros packages
delete ros_comm package
But non off the above worked for us.
Is there anybody who has any ideas?
Thanks in advance!
Related
So I am trying to make a virtual machine of a raspios-bullseye-arm64.
By using Qemu on my ubuntu 22.04 Lts x86_64, I was able to see the raspberry terminal.
I could not access to that VM because the default user and pw didn´t work. (but at least I know it launch)
So now my main goal was to get Cockpit to work and integrate the Cockpit-machines.
That part was easy and now I can make the amd64 machines without problem.
Now my goal is to get the arm64 machines to work with cockpit but I am not able to.
I don't know if it will be possible or I will have to get another machine with arm64 architecture to install the cockpit and have the arm64 and amd64 separated in two different machines.
Hope you guys can help me because nothing seems to solve my problem on my research.
I already tried to change the CPU configuration.
Also the boot order.
It keeps getting me the error of no bootable decive.
I am sure this is because of the difference of architecture.
Goal
I was attempting to install Elastix 4.0 on a home PC via a Bootable USB, but never had any luck getting it to install past the CentOS7 part (it kept giving me a "Warning: /dev/root does not exist" error).
What I've Tried
My main PC is Windows 10 Pro, so after downloading the latest Elastix 4.0 .iso from "http://www.elastix.com/en/downloads/" (Elastix-4.0.74-Stable-x86_64-bin-10Feb2016.iso) I used UNetbootin to create my Bootable USB for Elastix 4.0. I put the now Bootable USB into the PC I want to put Elastix 4.0 on and started it up.
It gave me the "Install Elastix 4" menu, so I hit enter and waited. Then the install proceeded to do its checks for CentOS7, but ended up getting stuck and gave me an error message "dracut-initqueue[580]: Warning: Could not boot." and "Warning: /dev/root does not exist".
This is where I am stuck and cannot proceed.
EDIT #1: I signed up for the Elastix forms, and someone else also had this issue. They said they downloaded the .iso and used Rufus to make a Bootable USB, and then booted the installation using the Troubleshooting -> Install CentOS 7 using Basic Graphics ... but according to them, that apparently corrupted something else and then they opted to just use a DVD.
EDIT #2: I tested this, and making a Bootable DVD of the .iso does work great for local machines. Installing it via a VM also seems to work without hassle. As a personal goal, I would like to get this working via a Bootable USB.
Research
I did some research but a lot of the solutions I've noticed are using the dd command in Linux to make a Bootable USB for just CentOS7 because it is (was?) known that UNetbootin did not properly make a Bootable USB for CentOS7, and I can't seem to find anything that would assist in making the Elastix 4.0 .iso work properly via a Bootable USB. I did try other tools such as Rufus 2.7, Win32 Disk Imager, ISO2USB, and dd for Windows, though most rendered my USB not bootable at all (Rufus worked OK, but still got stuck at the CentOS7 part). Also, installing via a CD/DVD is not ideal, as I have no CD/DVD drive (and I want to see if I can get this working via a Bootable USB drive).
There seem to be a few guides out there for trying to create a Bootable USB for Elastix 2.x, but nothing for Elastix 4.0. Reviewing those, it looks like the guides reference some files that do not exist in the new .iso (ex: ks_default.cfg). Still, my issue pertains mainly to the CentOS7 error I'm getting so I don't think this is related.
Any assistance with this is appreciated, and if you require more information from my end just let me know. I'm willing to try / re-try anything.
Thank you in advance.
http://henrysittechblog.blogspot.ru/2014/01/install-elastix-from-usb-step-by-step.html
Look for this line, but it may change:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Change it to:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=sdb1:/dev/sdb1:/ks/anaconda-ks.cfg quiet
Hi there i solve this problem 80%.
i did some manual change at line:
inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Mine:
inst.ks=scsi:/dev/sdb1:/ks/anaconda-ks.cfg quiet
hd is not recogniced by Centos7.
made my usb bootable with rufus 2.9
then open isolinux.cfg with notepad++
just change the line
inst.ks=hd:sdb1:/ks/anaconda-ks.cfg quiet
where sdb1 used to say cdrom
I creating SD card by this guide: Archlinux Raspberry-pi-2 installation.
Previously everything working fine. 2016-01-11 I Archlinux OS with command "pacman -Syu". And it started to fail. And throw errors.
I think that it is becouse of SD card model and it corrupdet (see note "1").
So I tried to reinstall Archlinux and preapere again clean SD card.
Downloaded latest Archlinux and installed be using same guide.
But it on launch still throws same error.
Then I tried to install Archlinux to another newly bought SD card. But same error :(.
2.1 I tried to install Raspbian to same card, and it worked perfectly.
It looks to me for now that the latest Archlinux version is faulty. What is your suggestions, how to fix this, or something now about latest Archlinux release and if it is faulty, maybe know when next version (fixed) will be release?
See attached images with errors.
Note:
My SD card slot (the locking mechanism) in PI is broken so I have some tape to handle it in place.
I am using memory Transcend micro SDHC 32GB w/adapt/class10 ts32gusdu1 SD card.
I tried different 8 GB card and it worked. So this is latest Archlinux version problem with that Transcend micro SDHC 32GB SD card drivers (becouse I tried two new same vendor cards and Archlinux was failing to boot). Previously (installed , updated one month before) the OS worked fine with that card.
I'm working on a debian 6.0 installed on virtualbox 4 hosted by Windows7, and I'm trying to get my STM32VL work using STLINK project that allows programming and debugging STM32 on Linux.
I followed their tutorial and installed all needed dependancies.
But when I run the program ./st-util -1, I get the following error:
tbarry#darkstar:~/stlink$ ./st-util -1
2014-03-20T10:18:48 WARN src/stlink-sg.c: Failed to find an stlink v1 by VID:PID
Error: could not open stlink device
Error: could not open stlink device
I underline that I have already installed Virtualbox extensions, and usb 2.0 is well handled.
Does anyone have an idea of what is blocking me?
I'd same problem. It was driver problem. Windows detected my st-link as mass storage device, so st-util didn't see it. I've used zadig utility in order to change the driver.
Not having found a solution to my problem, I tried with VMware player and it worked nice.
Conclusion: Whatever the problem I had, it was coming from VirtualBox.
I have a Raspberry Pi model B that I just bought. I downloaded and built the complete Mono source code to try to solve the hard float issue because supposedly a developer just committed a fix in the 3.2.7 version.
I have done the build and it worked without errors. I would now like to create a package or tarball or something that I can use to take what I just built and install it on other RPi devices.
Can someone tell me how to do this?