Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launch rtkrcv at boot of my Linux system #298

Open
afermi opened this issue May 16, 2017 · 12 comments
Open

Launch rtkrcv at boot of my Linux system #298

afermi opened this issue May 16, 2017 · 12 comments
Labels

Comments

@afermi
Copy link

afermi commented May 16, 2017

Hello,
I need to launch rtkrcv at boot of my system with Linux/Debian OS. In order to do that I wrote a bash file containing the following call

rtkrcv -s -o "my_conf_file.conf"

and created the Linux service with update-rc.d. However rtkrcv is not executed.
Have anyone had a similar problem? Any hint how to solve it?

Thank you very much,
Alessandro

@Rjbsnxt
Copy link

Rjbsnxt commented May 23, 2017

I have the same problem under Debian 8. It appears to be due to the segmentation fault error, a result of the b24 release apparently. See thread: #272

The problem is crudely solved by starting rtkrcv manually ("rtkrcv -o my_conf_file.conf" and then "start").
I haven't figured out how to write this into a script yet, so I too am looking for a solution!

@MrYuJing
Copy link

I meet the same problem too. If I turn on outstream into a file in the configure file and then excute "rtkrcv -s -o "my_conf_file.conf" " in my putty terminal, but the terminal immediately closed and I found rtkrcv was not running at backend using "top" command in a new terminal. On the other side, if I turn off outstream into a file in the configure file and then excute "rtkrcv -s -o "my_conf_file.conf" " in my putty terminal, everything is ok. I hope this phenomenon will be a little clue to find out reason.

@Rjbsnxt
Copy link

Rjbsnxt commented Jun 5, 2017

Yes I found that too MrYuLing - outputting to a file was the problem.

@billmaidment
Copy link

Hi. I have a similar problem, but it is with 2.4.2p12. According to the logs it appears that my /etc/rc.local is not completing. It seems to stop partway through the nvsmode instruction on boot.
(/bin/sleep 5 && /usr/bin/nvsctl -v reset)
(/bin/sleep 7 && /usr/bin/nvsmode -v binr)
(/bin/sleep 9 && /usr/bin/binrcmd -v /home/pi/rtk/init.cmd)
(/bin/sleep 11 && /usr/bin/rtkrcv -s -o /home/pi/rtk/rtkrover.conf &)
However, running these instructions manually competes OK.
This may not be the same problem, or it may be a pointer to the source of the problem.
Interestingly, the same setup on the base machine, with the final line:
(/bin/sleep 11 && /usr/bin/rtkbase &)
is working OK on boot.
nvsmode script attached as nvsmode.txt
nvsmode.txt

@sezeryalcin
Copy link

This is a duplicate of #272
Please close this bug and add comments on main bug. No need confusion.
Also as we have p26 now, nobody will fix issues at p12. So upgrade to never version and test.

@sezeryalcin sezeryalcin marked this as a duplicate of #272 Jul 17, 2017
@billmaidment
Copy link

billmaidment commented Jul 18, 2017 via email

@sezeryalcin
Copy link

Sorry, its b26, not p26.
2.4.3 is still beta and there is no problem with using 2.4.2. However, if you are using beta version, you should try newer version.

@billmaidment
Copy link

billmaidment commented Jul 18, 2017 via email

@sezeryalcin
Copy link

This fix works for me with b27. I had several compilation errors with b28 and use b27.
This is on raspberry pi with raspbian (debian jessie mod)
You must do make clean and recompile with make in RTKLIB_2.4.3/app/rtkrcv/gcc folder.

@billmaidment
Copy link

billmaidment commented Jul 19, 2017 via email

@billmaidment
Copy link

billmaidment commented Jul 19, 2017 via email

@windsoryin
Copy link

Hi billmaidment, Thanks for your post. I solved similar problems in my trying to auto-start RTKRCV. It really save my day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants