Will this work for permanent setting rate at 4800?



If I reboot I come back to the default rate.
I use this code to get the info.


I also try it with sudo but it fail to keep the rate after reboot.

Rule #12

make sure it works before you make it permanent.

The gpsd deals with this. We we going down this path because I misunderstood not finding the gps with the gpsd "not finding the gps" rather than the data that comes out is an error.

We need to figure out what driver gpsd is loading that's giving the error and tell it not to use it. Then we need to find the 'right one', then tell the gpsd to use it....then we make things permanent.

Take a breath. Don't jump the gun.

Ok, with the code:

I got some output, what I do now??
Do I connect to internet to update all??
See image name "2016-05-06_084715_1024x768.png"

I run what you ask me before for the gpsd, it all work.
See "gpsd_Info.txt"

I just read

Leave it on for a while.

See it work, you get not far form me, look at the gpsd_Info.txt
it see the uBlox. So what I do now???

I run this code:



And open the GPS Satellites window, it work.
See Image.

Change nothing except this entry

See how it works....and possible check your antennae placement

Hi Moe,

Your code fail, but I understand what you want me to do, so I use the code at the page one of this post.


After I have run the code I start the GPS Satellites and GPS Panel, they all work. So I close them all and reboot
the computer, open again GPS Satellites and GPS Panel, still working. YESSS we got it working

See image.

I will go eat and after I want to run the "Software Updater" and test the GPS after.

My GPS antennae is on the UBlox 6 chip, all is on the right back top of the screen, from there it have some small
cable to go to the motherbord.

Thanks a lot for your time and help.
Best Regards my Moe, owe some beers.

Hi,

I have run the Software Updater and change the language to my native, the GPS is still working good.
I have load my chartes on the harddrive for OpenCPN and run it.


When it open, I got a error message that tell it is impossible to open the file name "rtlsdr".
When I close the message OpenCPN work and see the GPS all ready.

When I reboot, I got a waiting time delay of 30 sec. to select a Navigatrix Generic. I did not have that
delay before. How could I remove or change the delay time?

The GPS is looking to work always, even if I do not open a software that will need it. Could it work only when a software that need it is running??

rtlsdr is a file used when you have a software defined radio installed to decode ais signals. Not significant in this case.
If the error really bugs you, you may find a way to eliminate it for OpenCpn over at the OpenCpn users forum http://www.cruisersforum.com/forums/f134/

Sorry, don't really understand that one, and probably
beyond my pay grade anyway... Sorry


Looking at the unit you have installed, it is hardwired so will look for a lock anytime the laptop is fired up. Looks like it only draws
50-60 milliamps seeking a lock and 40 milliamps after lock. so not a draw to worry about in my opinion

The Other David

Hi CapCouillon,

For the "rtlsdr", it was a plugin, I have deactive it, it have fix the issue.

Still have a boot delay that I did not have before, the boot was create after I have run the Software Updater.
Before that scren in the image1 was display only 5 seconds now it is display 30 seconds.
Where is the setting file to change the boot delay??

See image 1

Off topic, what is the image size to load here for the forum, I notice that my images are to big?? I will have to resize them and load them again.

Keep your screen shots at about a width of 425 or so and you will be fine

The default delay of 30 sec is there to allow you time to make a choice if you want to boot into another mode. If the default startup is good,
just hit enter when the screen comes up and away you go.... No need to wait.

As usual, you can change the delay, but rule #3 says "don't fix something that works"

Both Davids are right. If it's not broke, don't fix it. This applies to upgrades as well.

GRand Unified Bootloader (GRUB) is the bit of code that tells the machine where the bits and pieces to 'boot into' are located. It also gives the human at the keyboard a chance to interact and possible select other options...and configured properly is an amazing tool which allows booting anything that is boot-able.

The downside is if it is badly configured, without special knowledge, you may not get past a black screen, a blinking cursor, and a few confusing letters.

A simple configuration of GRUB looks likeMost of the information is # comments, and/or commented out #instructions that are ignored.

The amount of comments is a indicator that what you are looking at, though possibly simple, can go horribly wrong if not done right. They include directions for further instructionsenter it into a terminal if you are brave enough for a 'Simple configuration' and want a hint, or specific instruction how to modify it.

If you still want to play with fire, edit the fileor for a 'friendlier' text editor.

You could change to any number (-1 to forever) and then, like the instructions sayto implement the changes that may make you happy, or may give you a 3 hour surprise project that makes the 30 second delay seem a tolerable blink of the eye.

Hi Moe,

State=A;
I have reinstall Navigatrix and set the GPS to work only, now it take me only 20 minutes to do that. I did not run the Software Updater. Now it have only one partition line and a memory test on the GRUB splash screen and it display for 30 seconds.

State=B;
Some history, before my Toughbook was running on Navigatrix with Software Updater done, to get the new version of OpenCPN 4.2.0. and all other update. All was working good, in the GRUB splash screen I could see 4 or 5 partitions lines and the screen display for only 3 seconds.

Now why I have a 30seconds delay and not 3 seconds like StateB?
If I check the code of file "grud.cfg".

If "recordfail = 1", it will give me a 30 seconds delay. Now if I check the file "grubenv", I see recordfail=1.

So to fix this 30 seconds delai I need to find what is the recordfail.

Rule #1 = fix bugs before using at sea, remember no internet help at sea.

It's hard telling what happened when you 'updated', or when this change occurred. I have to guess, after a blind update, and a reboot, because something modified your GRUB, but it wasn't a new version of OpenCPN.

Unfortunately, I don't have the mental capacity in this area to figure out why someone else's advice isn't working...my only advice is if it's not working, don't do it and revert the changes.

You can spend 3 hours chasing a problem only to realise sometime before you uncommented a line that sent you on this goose chase...or worse, never remember what the change was, and it will never work with the change.

If my suggestion of changing the GRUB_TIMEOUT to something else didn't work, we can look at other solutions.

Hi Moe,

My Toughbook is at StateA, I did not change the GRUB_TIMEOUT.
What I did is to install the last Version: 0.5 (Août 2015) from my USB key and have select erase the harddrive before install.
And run some stty code to setup the GPS.

So new device GPS and stty code run, are new things. No update was done.

My Grub 30 seconds delay come from the read of the grubenv file.
I have to find what have write a recordfail value of 1.
If I force the delay time with GRUB_TIMEOUT, that will not fix the recordfail. The fail issue will still be there.

What are the test that are run to write the grubenv file?
Where are those test file locate?
Could I run those test one by one and get a output to find what is failling?

If you know this then you will also know Ok, it's my understanding the long delay come after, and from, a failed boot. The cause of the failure is unknown. It might have been something in the update. It might be the human keeps interrupting it. We can't tell. Until that fault has been corrected it will probably continue in that loop, unless you gut the recordfail mechanism. There is no reason for that.

It might be as simple as using your up/down keys and selecting a different listing in the GRUB menu, or reverting to the original listing, and allowing a successful boot to take place. Remember the the boot after the failed boot will pause, so that's two successful boots to confirm if you've 'fixed' the boot problem. It goes on to say That is to say, the stopping at the boot menu is undesirable sometimes, and messing with these files is good sometimes.

I just don't know if it's one of those times.

It sometime helps to visually *see* what is going on to see what is going on.

This GRUB Customizer takes some of the hocus pocus out of the process.and call it withor Menu> System Tools> Grub Customizer.

Like all things, you can fix it, even make it pretty, or make if inoperable, depending on your choices.

Hello
fresh install apt-get update..

i cant get the gps to work..Navibe GM270.
i have done lsusb found gps as, Bus 002 Device 003: ID 067b:2303
Prolific Technology, Inc. PL2303 Serial Port

dmesg.
[ 20.316338] pps pps0: new PPS source usbserial0
[ 20.316348] pps pps0: source "/dev/ttyUSB0" added
[ 23.393339] init: plymouth-upstart-bridge main process ended, respawning
[ 23.401470] init: plymouth-upstart-bridge main process (1721) terminated with status 1
[ 23.401488] init: plymouth-upstart-bridge main process ended, respawning
[ 26.005932] init: plymouth-stop pre-start process (1989) terminated with status 1
[ 45.247288] audit_printk_skb: 129 callbacks suppressed
[ 45.247293] audit: type=1400 audit(1481908629.563:55): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2599 comm="apparmor_parser"
[ 45.247301] audit: type=1400 audit(1481908629.563:56): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2599 comm="apparmor_parser"
[ 45.247785] audit: type=1400 audit(1481908629.563:57): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2599 comm="apparmor_parser"

unplug gps

[ 45.247293] audit: type=1400 audit(1481908629.563:55): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2599 comm="apparmor_parser"
[ 45.247301] audit: type=1400 audit(1481908629.563:56): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2599 comm="apparmor_parser"
[ 45.247785] audit: type=1400 audit(1481908629.563:57): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2599 comm="apparmor_parser"
[ 994.296248] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 994.296538] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 994.463462] usb 2-1.1: USB disconnect, device number 3
[ 994.465519] pps pps0: removed
[ 994.465825] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -19
[ 994.466034] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 994.466067] pl2303 2-1.1:1.0: device disconnected

dpkg-reconfigure gpsd.
changed to ttyusb0 at the Device the gps is attached to ,window

This command opens a empty new file .
sudo gedit /lib/udev/rules.d/60-gpsd.rules

nmea output from cpt shows only GPSD:localhost:2947

anyone have an idea of what i can try next ?

I think you're working too hard and may have undone a setup that would have worked.

This makes my head hurt as it then becomes complicated. Does the gps not work because of an initial system incompatibility, your modifications, or did the Fresh Install contribute to this little delight?

The gps is fairly stock and the Prolific PL2303, is prolific and in most converters..something like 80% use that chip.

What I'd need to know is if it worked out of the box. Depending on the type of "not working' there are some clues to why.

The standard way it doesn't work out of the box is the cool start of a gps. All batteries die, even the new ones in the expensive models, and with them the memory.

A triangulated lock might require a new almanac, by this time (yes, it can be forever) the settings in OpenCPN will have been changed to get it to work...but actual creates a conflict with gpsd. This not a good thing, and we forget.

The gpsd is the application that takes care of your gps needs, and is best to 'just like it' and leave it alone to save aggravation. Having something else touch the gps, like in the screenshot of OpenCPN, is just going to make it mad and cause you problems, among them, baldness, insanity, or death. None of them avoidable, just avoidable from this cause.