Error unexpected Sopas answer for request sWN SetActiveApplications #11
Comments
|
Hi, we will check this issue next week and give you a detailed feedback. Best regards, Michael
|
|
Hi Chris, in the first step you can ignore the warnings. Some scanner types does not support the full range of commands. Can you receive data from the MRS1xxx? Best regards, |
|
The MRS1xxx does not support some legacy commands. So I changed the command processing similar to the MRS6124. The output starting with V.001.002.002 is like this: [ INFO] [1530430494.072798301]: sick_generic_caller V. 001.002.002 |
|
I will push this version at latest tomorrow morning (2nd of July) after testing. |
|
Hi all, I just pushed a new version in the devel branch, which should solve the mentioned issue. Best regards, |
|
This is my first product with SICKAG and i'm not fully experienced using
this. I downloaded the sick_scan directory and right now i'm facing
different issues:
By the way i'm still getting the error:
INFO Receiving <STX>sEA LMDscandata \x01<ETX>
WARN Timeout during waiting of new datagram
Error Read Error when getting datagram: 1
INFO Start initialising scanner...
ERROR No answer received after 20000ms. Maybe sopas mode is wrong
ERROR sendSOPASCommand: no full reply available for read after 20000ms
SOPAS - Error stopping stream scan data!
WARN Disconnecting TCP-Connection
I also get the following warning:
WARN Device ??? V-1.-1 found and maybe unsupported by this driver.
WARN Full SOPAS answer: Command or Error message not defined.
Also, If the sick_generic_caller is supposed to be V.001.002.002, why i'm i
seeing 001.001.001? I substituted the newly updated sick_scan directory with my older one, re-made everything using the catkin_make build system etc, still seeing V.001.001.001 though.
This happens repeatedly, why is this happening and how can i fix this?
…On Sun, Jul 1, 2018 at 9:45 AM, Michael Lehning ***@***.***> wrote:
Closed #11 <#11>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AmzFJAOdondXcCFaGCk9BJJwB5XAmIUPks5uCPzGgaJpZM4U9VBk>
.
|
|
Did you choose the devel branch? Did you build your app. via catkin_make? Can you ping your device?
--
Am 02.07.18, 17:57, chrisfernam2 <notifications@github.com> schrieb:
This is my first product with SICKAG and i'm not fully experienced using
this. I downloaded the sick_scan directory and right now i'm facing
different issues:
1st) Its failing to open TCP connection.
2nd) I cant even connect to ET tool even though i was able to connect 3
days ago, i custom search for LiDAR by giving ip 192.168.0.1 but its unable
to establish connection.
3rd) If the sick_generic_caller is supposed to be V.001.002.002, why i'm i
seeing 001.001.001?
On Sun, Jul 1, 2018 at 9:45 AM, Michael Lehning ***@***.***> wrote:
Closed #11 <#11>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AmzFJAOdondXcCFaGCk9BJJwB5XAmIUPks5uCPzGgaJpZM4U9VBk>
.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I did build the app via catkin_make, and yes i am able to ping the device
successfully.
However, how can i choose the devel branch? I have been learning ROS for
the past month so some things are new to me.
Thanks for the help by the way!
On Mon, Jul 2, 2018 at 12:00 PM, Michael Lehning <notifications@github.com>
wrote:
… Did you choose the devel branch? Did you build your app. via catkin_make?
Can you ping your device?
--
Am 02.07.18, 17:57, chrisfernam2 ***@***.***> schrieb:
This is my first product with SICKAG and i'm not fully experienced using
this. I downloaded the sick_scan directory and right now i'm facing
different issues:
1st) Its failing to open TCP connection.
2nd) I cant even connect to ET tool even though i was able to connect 3
days ago, i custom search for LiDAR by giving ip 192.168.0.1 but its unable
to establish connection.
3rd) If the sick_generic_caller is supposed to be V.001.002.002, why i'm i
seeing 001.001.001?
On Sun, Jul 1, 2018 at 9:45 AM, Michael Lehning ***@***.***>
wrote:
> Closed #11 <#11>.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#11 (comment)>, or
mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
AmzFJAOdondXcCFaGCk9BJJwB5XAmIUPks5uCPzGgaJpZM4U9VBk>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AmzFJMmQHxPE3GwPois7PLGFqxNlh-jUks5uCm3fgaJpZM4U9VBk>
.
|
|
You can choose the devel branch in the drop down menu on the github page of
the project.
chrisfernam2 <notifications@github.com> schrieb am Mo., 2. Juli 2018, 17:57:
… This is my first product with SICKAG and i'm not fully experienced using
this. I downloaded the sick_scan directory and right now i'm facing
different issues:
1st) Its failing to open TCP connection.
2nd) I cant even connect to ET tool even though i was able to connect 3
days ago, i custom search for LiDAR by giving ip 192.168.0.1 but its unable
to establish connection.
3rd) If the sick_generic_caller is supposed to be V.001.002.002, why i'm i
seeing 001.001.001?
On Sun, Jul 1, 2018 at 9:45 AM, Michael Lehning ***@***.***>
wrote:
> Closed #11 <#11>.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#11 (comment)>, or
mute
> the thread
> <
https://github.com/notifications/unsubscribe-auth/AmzFJAOdondXcCFaGCk9BJJwB5XAmIUPks5uCPzGgaJpZM4U9VBk
>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfwOseWtRtXGQe1IDtEyv5TSYTg8p3jZks5uCkLQgaJpZM4U9VBk>
.
|
|
Here you can see the branches.
Michael Lehning <michael.lehning@googlemail.com> schrieb am Mo., 2. Juli
2018, 21:33:
… You can choose the devel branch in the drop down menu on the github page
of the project.
chrisfernam2 ***@***.***> schrieb am Mo., 2. Juli 2018,
17:57:
> This is my first product with SICKAG and i'm not fully experienced using
> this. I downloaded the sick_scan directory and right now i'm facing
> different issues:
>
> 1st) Its failing to open TCP connection.
> 2nd) I cant even connect to ET tool even though i was able to connect 3
> days ago, i custom search for LiDAR by giving ip 192.168.0.1 but its
> unable
> to establish connection.
>
> 3rd) If the sick_generic_caller is supposed to be V.001.002.002, why i'm i
> seeing 001.001.001?
>
>
>
>
>
>
>
> On Sun, Jul 1, 2018 at 9:45 AM, Michael Lehning ***@***.***
> >
> wrote:
>
> > Closed #11 <#11>.
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > <#11 (comment)>, or
> mute
> > the thread
> > <
> https://github.com/notifications/unsubscribe-auth/AmzFJAOdondXcCFaGCk9BJJwB5XAmIUPks5uCPzGgaJpZM4U9VBk
> >
> > .
> >
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AfwOseWtRtXGQe1IDtEyv5TSYTg8p3jZks5uCkLQgaJpZM4U9VBk>
> .
>
|
|
You can you also the command line:
git checkout devel
Best regards, michael
chrisfernam2 <notifications@github.com> schrieb am Fr., 29. Juni 2018,
18:54:
… Hi everyone i just received the mrs1000 LiDAR and i'm having some
problems. I'm running the launch file by entering: roslaunch sick_scan
sick_mrs_1xxx.launch but i'm facing quite a bit of errors. Could you please
help me?
Here is the behavior within my terminal:
***@***.***:~/catkin_ws/src/sick_scan/launch$ roslaunch sick_scan
sick_mrs_1xxx.launch
... logging to
/home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/roslaunch-ROS-vm-2325.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
xacro.py is deprecated; please use xacro instead
started roslaunch server http://localhost:39475/
SUMMARY
PARAMETERS
- /robot_description: <?xml version="1....
- /rosdistro: melodic
- /rosversion: 1.14.2
- /sick_mrs_1xxx/hostname: 192.168.0.1
- /sick_mrs_1xxx/intensity_resolution_16bit: False
- /sick_mrs_1xxx/max_ang: 2.3998277
- /sick_mrs_1xxx/min_ang: -2.3998277
- /sick_mrs_1xxx/port: 2112
- /sick_mrs_1xxx/scanner_type: sick_mrs_1xxx
- /sick_mrs_1xxx/timelimit: 5
NODES
/
sick_mrs_1xxx (sick_scan/sick_generic_caller)
ROS_MASTER_URI=http://localhost:11311
process[sick_mrs_1xxx-1]: started with pid [2343]
[ INFO] [1530290727.003895157]: sick_generic_caller V. 001.002.001
[ INFO] [1530290727.003985764]: Program arguments:
/home/ros-vm/catkin_ws/devel/lib/sick_scan/sick_generic_caller
[ INFO] [1530290727.004012680]: Program arguments: __name:=sick_mrs_1xxx
[ INFO] [1530290727.004029852]: Program arguments:
__log:=/home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/sick_mrs_1xxx-1.log
[ INFO] [1530290727.016150117]: Start initialising scanner ...
[ INFO] [1530290727.043051528]: Parameter setting for <active_echo: 0>
[ INFO] [1530290727.243853840]: Sending : sMN SetAccessMode
\x03\xf4\x72\x47\x44
[ INFO] [1530290727.255578714]: Receiving: sAN SetAccessMode \x01
[ INFO] [1530290727.458298011]: Sending : sWN EIHstCola \x01
[ INFO] [1530290727.469194857]: Receiving: sWA EIHstCola
[ INFO] [1530290727.670414146]: Sending : sMN LMCstopmeas
[ INFO] [1530290727.703497948]: Receiving: sAN LMCstopmeas \x00
[ INFO] [1530290727.904011287]: Sending : sWN SetActiveApplications
\x01\x20\x46\x45\x56\x4c\x20\x00
[ INFO] [1530290727.916623526]: Receiving: sFA\x00\x45
[ERROR] [1530290727.916850355]: Error Sopas answer mismatch Error
unexpected Sopas Answer for request "sWN SetActiveApplications FEVL
5Answer= >>>sFA\x00\x45<<<
[ERROR] [1530290727.917062333]: Command or Error message not defined
[ INFO] [1530290728.118791900]: Sending : sWN SetActiveApplications
\x01\x20\x52\x41\x4e\x47\x20\x01
[ INFO] [1530290728.131115200]: Receiving: sFA\x00\x45
[ERROR] [1530290728.131560221]: Error Sopas answer mismatch Error
unexpected Sopas Answer for request "sWN SetActiveApplications RANG
7Answer= >>>sFA\x00\x45<<<
[ERROR] [1530290728.131687105]: Command or Error message not defined
[ INFO] [1530290728.332318527]: Sending : sRI 0
[ INFO] [1530290728.343563829]: Receiving: sFA\x00\x03
[ERROR] [1530290728.343697775]: Error Sopas answer mismatch Error
unexpected Sopas Answer for request sRI 0xAnswer= >>>sFA\x00\x03<<<
[ERROR] [1530290728.343803174]: Error reading device ident
[ INFO] [1530290728.544384533]: Sending : sRN SerialNumber
[ INFO] [1530290728.554818372]: Receiving: sRA SerialNumber
\x00\x08\x31\x37\x34\x35\x30\x30\x32\x33
[ WARN] [1530290728.554976773]: Device ??? V-1.-1 found and maybe
unsupported by this driver.
[ WARN] [1530290728.555022895]: Full SOPAS answer: Command or Error
message not defined
[ INFO] [1530290728.756571314]: Sending : sRN FirmwareVersion
[ INFO] [1530290728.767168275]: Receiving: sRA FirmwareVersion
\x00\x09\x56\x20\x31\x2e\x33\x2e\x31\x2e\x30
[ INFO] [1530290728.967667563]: Sending : sRN SCdevicestate
[ INFO] [1530290728.978611015]: Receiving: sRA SCdevicestate \x00
[ INFO] [1530290729.179266167]: Sending : sRN ODoprh
[ INFO] [1530290729.189693093]: Receiving: sRA ODoprh \x00\x00\x00\xf8
[ INFO] [1530290729.391517477]: Sending : sRN ODpwrc
[ INFO] [1530290729.401865706]: Receiving: sRA ODpwrc \x00\x00\x00\x02
[ INFO] [1530290729.604090387]: Sending : sRN LocationName
[ INFO] [1530290729.615077248]: Receiving: sRA LocationName
\x00\x0b\x53\x4e\x20\x31\x37\x34\x35\x30\x30\x32\x33
[sick_mrs_1xxx-1] process has died [pid 2343, exit code -11, cmd
/home/ros-vm/catkin_ws/devel/lib/sick_scan/sick_generic_caller
__name:=sick_mrs_1xxx
__log:=/home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/sick_mrs_1xxx-1.log].
log file:
/home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/sick_mrs_1xxx-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
***@***.***:~/catkin_ws/src/sick_scan/launch$
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfwOsUzCUOz_o6oB1lv6KnRKZ17ysJQjks5uBlvbgaJpZM4U9VBk>
.
|
|
Ok i just downloaded the devel version and remade my file. Although it now shows sick_generic_caller V.001.002.002, and most errors are gone, im still getting the same final error causing a disconnection on TCP-connection, i read in another opened issue that i can simply increase the timeout to 30000 by configuring the sick_scan_common_tcp.cpp , i did this, but still no change. here is the full log : SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[sick_mrs_1xxx-1]: started with pid [23019] [ERROR] [1530561256.660397334]: sendSOPASCommand: no full reply available for read after 20000 ms SOPAS - Error stopping streaming scan data! |
|
Command handling is ok.
But it seems that the scanner does not send the datagram. Can you receive data via sopas et? Could you send me the firmware version? I will discuss this issue with SICK.
--
Am 02.07.18, 21:54, chrisfernam2 <notifications@github.com> schrieb:
Ok i just downloaded the devel version and remade my file. Although it now shows sick_generic_caller V.001.002.002, and most errors are gone, i still getting the same final error causing a disconnection on TCP-connection, here is the full log :
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Actually i think it's almost working now. The final terminal log info printed was:
INFO Receiving:<STX>sEA LMDscandata \x01<ETX>
It hasn't given me the error anymore. To verify, entered rostopic list and
i get the following topics:
/cloud
/diagnostics
/radar
/rosout
/rosout_agg
/scan
/sick_mrs_1xxx/parameter_descriptions
/sick_mrs_1xxx/parameter_updates
I "rostopic echo /cloud" and "rostopic echo /scan" in the terminal and i
can confirm i'm receiving values of some sort.
When i "roslaunch sick_scan sick_mrs_1xxx.launch" , isn't this supposed to
launch rviz for me automatically?
If not how may i see the scanned point clouds in rviz; that is, what
command?
roslaunch sick_scan sick_mrs_1xxx.launch
rosrun rviz rviz
publish to point cloud (how can i do this?) and see point cloud
data on rviz?
I appreciate your patience and support.
…On Mon, Jul 2, 2018 at 1:08 PM, Michael Lehning ***@***.***> wrote:
Command handling is ok.
But it seems that the scanner does not send the datagram. Can you receive
data via sopas et? Could you send me the firmware version? I will discuss
this issue with SICK.
--
Ing.-Büro Dr. Michael Lehning
Schulstraße. 21B
D-31137 Hildesheim
Germany
E: ***@***.***
T: +49 5121 645-70
M: +49 173 37 69 242
Am 02.07.18, 21:54, chrisfernam2 ***@***.***> schrieb:
Ok i just downloaded the devel version and remade my file. Although it now
shows sick_generic_caller V.001.002.002, and most errors are gone, i still
getting the same final error causing a disconnection on TCP-connection,
here is the full log :
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AmzFJFS9NprypGCdy1IVAMSW5iJNilHwks5uCn3IgaJpZM4U9VBk>
.
|
|
Sounds great. Just start rviz and follow the hints I gave in the ticket for
the mrs6124.
chrisfernam2 <notifications@github.com> schrieb am Mo., 2. Juli 2018, 22:19:
… Actually i think it's working now. The final terminal log info printed was:
INFO Receiving:<STX>sEA LMDscandata \x01<ETX>
It hasn't given me the error anymore. To verify, entered rostopic list and
i get the following topics:
/cloud
/diagnostics
/radar
/rosout
/rosout_agg
/scan
/sick_mrs_1xxx/parameter_descriptions
/sick_mrs_1xxx/parameter_updates
I "rostopic echo /cloud" and "rostopic echo /scan" in the terminal and i
can confirm i'm receiving values of some sort.
When i "roslaunch sick_scan sick_mrs_1xxx.launch" , isn't this supposed to
launch rviz for me automatically?
If not how may i see the scanned point clouds in rviz; that is, what
command?
roslaunch sick_scan sick_mrs_1xxx.launch
rosrun rviz rviz
publish to point cloud (how can i do this?) and see point cloud
data on rviz?
I appreciate your patience and support.
On Mon, Jul 2, 2018 at 1:08 PM, Michael Lehning ***@***.***>
wrote:
> Command handling is ok.
> But it seems that the scanner does not send the datagram. Can you receive
> data via sopas et? Could you send me the firmware version? I will discuss
> this issue with SICK.
> --
> Ing.-Büro Dr. Michael Lehning
> Schulstraße. 21B
> D-31137 Hildesheim
> Germany
>
> E: ***@***.***
> T: +49 5121 645-70
> M: +49 173 37 69 242
>
>
> Am 02.07.18, 21:54, chrisfernam2 ***@***.***> schrieb:
>
> Ok i just downloaded the devel version and remade my file. Although it
now
> shows sick_generic_caller V.001.002.002, and most errors are gone, i
still
> getting the same final error causing a disconnection on TCP-connection,
> here is the full log :
>
> —
> You are receiving this because you modified the open/close state.
>
> Reply to this email directly, view it on GitHub, or mute the thread.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AmzFJFS9NprypGCdy1IVAMSW5iJNilHwks5uCn3IgaJpZM4U9VBk
>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfwOsdRl0LZsSiOatoiqWNgEzd2EXlQDks5uCoA0gaJpZM4U9VBk>
.
|
|
Rviz: change the fixed frame under global options to "laser" instead of "map".
|
|
I opened rviz and chose to add a display (by topic), i added /cloud PointCloud2. I specified the topic to be /cloud, but almost instantaneously i get: Status: error Transform[sender=unknown_publisher] For frame[laser]:Fixed Frame[map] does not exist. It should be pretty much plug & play from this point onward, what does this error mean? |
|
Works perfectly. Thank you very much.
…On Mon, Jul 2, 2018 at 2:02 PM, Michael Lehning ***@***.***> wrote:
Rviz: change the fixed frame under global options to "laser" instead of
"map".
--
Ing.-Büro Dr. Michael Lehning
Schulstraße. 21B
D-31137 Hildesheim
Germany
E: ***@***.***
T: +49 5121 645-70
M: +49 173 37 69 242
Am 02.07.18, 21:54, chrisfernam2 ***@***.***> schrieb:
Ok i just downloaded the devel version and remade my file. Although it now
shows sick_generic_caller V.001.002.002, and most errors are gone, i still
getting the same final error causing a disconnection on TCP-connection,
here is the full log :
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AmzFJFYF2-sJ0zl7ZoMJbPDC4hfQDPqVks5uCop_gaJpZM4U9VBk>
.
|
|
You are welcome. We are happy that your laserscanner is up and running. One hint: In addition to subscription of /cloud as a Pointcloud2-Message you can also subscribe Please pay attention to the fact, that points on an elevation angle not equal to 0° lays on If you want to see a single layer with a specific echo you should switch the fixed frame under global options to the wished frame id instead of "map". e.g. for rviz:
It is also a good idea to use "rostopic echo ...." and interrupt the output via ctrl-c to inspect the data in the header. This gives you a good feeling about data organization and naming. Addition to pointcloud2: rosrun tf static_transform_publisher 0 0 0 0 0 0 1 map laser 10 Have fun! |
|
Thank you the hint is very helpful for me for differentiating between each layer! |
|
I'm still receiving the same "Transform[sender=unknown_publisher]" error ; that is, How can i fix this? |
|
You can use the command tf static transform as a node in the launch file.
chrisfernam2 <notifications@github.com> schrieb am Do., 5. Juli 2018, 20:24:
… I'm still receiving the same "Transform[sender=unknown_publisher]" error ;
that is,
For frame[laser_+250_DIST3]:Fixed Frame[laser_+250_DIST1] does not exist.
How can i fix this?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfwOsbS2QOC4zj363-m3Oj9wjuhW5JS8ks5uDlnDgaJpZM4U9VBk>
.
|
|
One remark: We recommend to use pointcloud2 instead of laserscan.
… You can use the command tf static transform as a node in the launch file.
chrisfernam2 ***@***.***> schrieb am Do., 5. Juli 2018,
20:24:
> I'm still receiving the same "Transform[sender=unknown_publisher]" error
> ; that is,
> For frame[laser_+250_DIST3]:Fixed Frame[laser_+250_DIST1] does not exist.
>
> How can i fix this?
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AfwOsbS2QOC4zj363-m3Oj9wjuhW5JS8ks5uDlnDgaJpZM4U9VBk>
> .
>
|
|
Hi, for a better understanding of the ideas and concepts I created today a test launch file and opened a ticket about this issue (Ticket #13). Best regards, |
|
Getting the same error @chrisfernam2 . Nothing is published on scan topic. How you removed this error. can you please help? LOG->ROS_MASTER_URI=http://localhost:11311 process[sick_mrs_1xxx-1]: started with pid [18897] |
|
@anupritdangi What happens after the Are data published in /cloud topic? As a test, please change the timeout for the scanner start in the sick_scan_common.cpp to 40 seconds. int SickScanCommon::init_scanner()
{
...
const int shortTimeOutInMs = 5000; // during startup phase to check binary or ascii
const int defaultTimeOutInMs = 40000; // standard time out 40 sec.
setReadTimeOutInMs(shortTimeOutInMs);
...Best regards, |
|
Are you sure it does not publish LaserScan messages? Mine is. Mine is setup
with a tirtlebot and is currently working fine.
…On Tue, Jul 24, 2018, 8:16 AM Michael Lehning ***@***.***> wrote:
@anupritdangi <https://github.com/anupritdangi>
Which MRS1xxx scanner do you use exactly? For multilayer scanners the
driver does not publish scan messages but only PointCloud2 messages in
topic /cloud. The individual layer of the scans are not in the same
coordinate frame, so the PointCloud2 representation is much more practical.
For the visualization in rviz you should select "laser" as fixed frame or
publish a tf transformation "laser"-->"map".
Best regards,
Michael
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AmzFJKdtRYNCVbVKTyaiuVvB7jAwCPkdks5uJzpFgaJpZM4U9VBk>
.
|
|
On Tue, Jul 24, 2018 at 12:33 PM, Christian Fernandez <
chrisfernam2@gmail.com> wrote:
… Are you sure it does not publish LaserScan messages? Mine is. Mine is
setup with a tirtlebot and is currently working fine.
On Tue, Jul 24, 2018, 8:16 AM Michael Lehning ***@***.***>
wrote:
> @anupritdangi <https://github.com/anupritdangi>
> Which MRS1xxx scanner do you use exactly? For multilayer scanners the
> driver does not publish scan messages but only PointCloud2 messages in
> topic /cloud. The individual layer of the scans are not in the same
> coordinate frame, so the PointCloud2 representation is much more practical.
>
> For the visualization in rviz you should select "laser" as fixed frame or
> publish a tf transformation "laser"-->"map".
>
> Best regards,
> Michael
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#11 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AmzFJKdtRYNCVbVKTyaiuVvB7jAwCPkdks5uJzpFgaJpZM4U9VBk>
> .
>
|
|
Hello, this was a little mix-up in our internal company coordination. You are correct. Two types of messages are published for the MRS1xxx. /cloud as Pointcloud2 message. For more than 4 layers (i.e. MRS6xxx), only the Pointcloud2 message is published. |
|
One additional hint: By comparing the timestamps you can see the "old" values for the timeout in the timestamp difference It is round about 20 sec. |
|
@michael1309 I am having MRS1104c. Nothing is published on /cloud topic also and i changed timeout to 40000ms. No change in the error. started roslaunch server http://localhost:54332/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 core service [/rosout] found [ERROR] [1532499602.852841825]: sendSOPASCommand: no full reply available for read after 40000 ms SOPAS - Error stopping streaming scan data! |
|
Everything is working fine now.I changed nothing just restarted the scanner 2-3 times. |
|
Great to hear. So you have left the timeout time at the set value of 20 seconds? If you can derive any rules when the scanner does not send datagrams, although the initialization sequence was successfully run before, we would be pleased if you could report this briefly. |
Hi everyone i just received the mrs1000 LiDAR and i'm having some problems. I'm running the launch file by entering: roslaunch sick_scan sick_mrs_1xxx.launch but i'm facing quite a bit of errors. Could you please help me?
Here is the behavior within my terminal:
ros-vm@ROS-vm:~/catkin_ws/src/sick_scan/launch$ roslaunch sick_scan sick_mrs_1xxx.launch
... logging to /home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/roslaunch-ROS-vm-2325.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
xacro.py is deprecated; please use xacro instead
started roslaunch server http://localhost:39475/
SUMMARY
PARAMETERS
NODES
/
sick_mrs_1xxx (sick_scan/sick_generic_caller)
ROS_MASTER_URI=http://localhost:11311
process[sick_mrs_1xxx-1]: started with pid [2343]
[ INFO] [1530290727.003895157]: sick_generic_caller V. 001.002.001
[ INFO] [1530290727.003985764]: Program arguments: /home/ros-vm/catkin_ws/devel/lib/sick_scan/sick_generic_caller
[ INFO] [1530290727.004012680]: Program arguments: __name:=sick_mrs_1xxx
[ INFO] [1530290727.004029852]: Program arguments: __log:=/home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/sick_mrs_1xxx-1.log
[ INFO] [1530290727.016150117]: Start initialising scanner ...
[ INFO] [1530290727.043051528]: Parameter setting for <active_echo: 0>
[ INFO] [1530290727.243853840]: Sending : sMN SetAccessMode \x03\xf4\x72\x47\x44
[ INFO] [1530290727.255578714]: Receiving: sAN SetAccessMode \x01
[ INFO] [1530290727.458298011]: Sending : sWN EIHstCola \x01
[ INFO] [1530290727.469194857]: Receiving: sWA EIHstCola
[ INFO] [1530290727.670414146]: Sending : sMN LMCstopmeas
[ INFO] [1530290727.703497948]: Receiving: sAN LMCstopmeas \x00
[ INFO] [1530290727.904011287]: Sending : sWN SetActiveApplications \x01\x20\x46\x45\x56\x4c\x20\x00
[ INFO] [1530290727.916623526]: Receiving: sFA\x00\x45
[ERROR] [1530290727.916850355]: Error Sopas answer mismatch Error unexpected Sopas Answer for request "sWN SetActiveApplications FEVL 5Answer= >>>sFA\x00\x45<<<
[ERROR] [1530290727.917062333]: Command or Error message not defined
[ INFO] [1530290728.118791900]: Sending : sWN SetActiveApplications \x01\x20\x52\x41\x4e\x47\x20\x01
[ INFO] [1530290728.131115200]: Receiving: sFA\x00\x45
[ERROR] [1530290728.131560221]: Error Sopas answer mismatch Error unexpected Sopas Answer for request "sWN SetActiveApplications RANG 7Answer= >>>sFA\x00\x45<<<
[ERROR] [1530290728.131687105]: Command or Error message not defined
[ INFO] [1530290728.332318527]: Sending : sRI 0
[ INFO] [1530290728.343563829]: Receiving: sFA\x00\x03
[ERROR] [1530290728.343697775]: Error Sopas answer mismatch Error unexpected Sopas Answer for request sRI 0xAnswer= >>>sFA\x00\x03<<<
[ERROR] [1530290728.343803174]: Error reading device ident
[ INFO] [1530290728.544384533]: Sending : sRN SerialNumber
[ INFO] [1530290728.554818372]: Receiving: sRA SerialNumber \x00\x08\x31\x37\x34\x35\x30\x30\x32\x33
[ WARN] [1530290728.554976773]: Device ??? V-1.-1 found and maybe unsupported by this driver.
[ WARN] [1530290728.555022895]: Full SOPAS answer: Command or Error message not defined
[ INFO] [1530290728.756571314]: Sending : sRN FirmwareVersion
[ INFO] [1530290728.767168275]: Receiving: sRA FirmwareVersion \x00\x09\x56\x20\x31\x2e\x33\x2e\x31\x2e\x30
[ INFO] [1530290728.967667563]: Sending : sRN SCdevicestate
[ INFO] [1530290728.978611015]: Receiving: sRA SCdevicestate \x00
[ INFO] [1530290729.179266167]: Sending : sRN ODoprh
[ INFO] [1530290729.189693093]: Receiving: sRA ODoprh \x00\x00\x00\xf8
[ INFO] [1530290729.391517477]: Sending : sRN ODpwrc
[ INFO] [1530290729.401865706]: Receiving: sRA ODpwrc \x00\x00\x00\x02
[ INFO] [1530290729.604090387]: Sending : sRN LocationName
[ INFO] [1530290729.615077248]: Receiving: sRA LocationName \x00\x0b\x53\x4e\x20\x31\x37\x34\x35\x30\x30\x32\x33
[sick_mrs_1xxx-1] process has died [pid 2343, exit code -11, cmd /home/ros-vm/catkin_ws/devel/lib/sick_scan/sick_generic_caller __name:=sick_mrs_1xxx __log:=/home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/sick_mrs_1xxx-1.log].
log file: /home/ros-vm/.ros/log/c477f7dc-7bbb-11e8-beb2-0800274a3ab6/sick_mrs_1xxx-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
ros-vm@ROS-vm:~/catkin_ws/src/sick_scan/launch$
The text was updated successfully, but these errors were encountered: