What is the best way to use GPS NMEA with ekos scheduler? GPS NMEA driver turned off after updating the time (said disconnecting driver due to overflow) I did not care at that point.
When i started my scheduler , it aborted all the jobs stating check the connected indi devices. I do not need GPS after the initial load , so i would have disconnected it anyway. shouldn't the scheduler run anyway?
Does that mean you can have 2 profiles running at the same time? - 1 Normal manually started profile and 1 started in Scheduler using different h/w in each profile. he answer will be no I guess but just thought I would ask
Thanks for reporting this. Currently Scheduler will repeatedly attempt to get all devices connected. I still have to make the number of attempts customizable. Although it may obviously cause issues, would it make sense to optionally let the Scheduler work even if not all the devices are up?
Thank you for chiming on this issue . I am not sure if it would be good idea to let scheduler start if all devices are not up . It could be given as option to user along with number of re-attempt.
I think we should rather focus on fixing the driver overflow problem at the first place .
I guess I'll put my last two cents worth in here. I had some issues with GPS at first because the baud rate for the device I bought was 4800 whereas the linux gpsd default is 9600. I notice you dont show a successful connection at all to the device, no fix data. Assuming you are running on linux, check the baud rate and update like this:
So you need to edit /etc/rc.local and then add this before the line that says exist 0
sudoedit /etc/rc.local
then add this
stty -F /dev/gps <baud rate>
Of course, assuming you used the port mapper to map the GPS.