Добро пожаловать!

Войдите или зарегистрируйтесь сейчас!

Войти

GPS приемник Spectra Precision SP80 проблемы в работе и методы их устранения

Тема в разделе "Spectra Precision", создана пользователем amax32, 26 сен 2014.

  1. SERGO

    Форумчанин

    Регистрация:
    25 янв 2011
    Сообщения:
    224
    Симпатии:
    24
    Адрес:
    Краснодарский край

    Полевой контроллер Spectra Precision T41
    Полевое ПО Spectra Precision Survey Pro 5.5
     
    #61
  2. Sanych1982

    Форумчанин

    Регистрация:
    9 янв 2014
    Сообщения:
    815
    Симпатии:
    370
    Обновите Survey Pro, хуже точно не будет, а может и проблема исчезнет...
     
    #62
  3. SERGO

    Форумчанин

    Регистрация:
    25 янв 2011
    Сообщения:
    224
    Симпатии:
    24
    Адрес:
    Краснодарский край
    Спасибо за ссылку. А какой из вариантов качать? Эта прошивка рус.?
     
    #63
  4. Sanych1982

    Форумчанин

    Регистрация:
    9 янв 2014
    Сообщения:
    815
    Симпатии:
    370
    Эту. Язык выбирается в процессе установки.
     
    #64
  5. SERGO

    Форумчанин

    Регистрация:
    25 янв 2011
    Сообщения:
    224
    Симпатии:
    24
    Адрес:
    Краснодарский край
    После перепрошивки пользовательские настройки слетают и устанавливаются на заводские, пользовательские файлы(проекты с отснятым материалом ) удаляются?
     
    #65
  6. Sanych1982

    Форумчанин

    Регистрация:
    9 янв 2014
    Сообщения:
    815
    Симпатии:
    370
    Это не перепрошивка, а обновление ПО. Ваши старые проекты должны сохраниться, но лучше, всегда нужную информацию предварительно скопировать... и, если создавали какие-либо пользовательские системы координат (СК), скопируйте файл "current.csd" из папки программы, в нем хранятся СК
     
    #66
  7. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    Добрый день!!! Возник вопросик! Почему когда снимаешь в RTK через TCP/IP и виртуальный порт (VSPE) иногда пропадает значение FIXED, но когда просто перезагружаешь порты (т.е. просто выключаешь программу VSPE), значение FIXED появляется.. но если программу не перезагрузить по съемку так и не получится вести
     
    #67
  8. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
    А время последней поправки?

    FIXED пропадает, когда:
    - поправка была слишком давно
    - мало общих спутников на базе и ровере

    В вашем случае, скорей всего, первый вариант.
    Может быть из-за плохого канала связи между базой и ПК или ровером и ПК.

    Где именно проблема - смотреть по активности в VSPE.
    Если байтики на базе бегают, а на ровере нет - значит проблема в ровере (операторе).
     
    #68
  9. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    время поправки может быть и 100 сек. и по всякому, может даже появится DGPS, перезагружаем VSPE и все продолжает работать!
     
    #69
  10. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
    Если у вас время поправки начинает с 3-5 секунд расти - проблема со связью
     
    #70
  11. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    а где именно в VSPE смотреть? байтики которые бегают
     
    #71
  12. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
  13. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    возможно проблемы со связь, но почему тогда приходиться VSPE перезагружать ??? без перезагрузки значение FIXED не получится
     
    #73
  14. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
    Со стороны приемника - соединение может быть активно, а по факту - нет.
    Аналогично - должно помогать переподключение "проблемного"приемника
     
    #74
  15. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    Следовательно проблемы в VSPE не как не должно быть? Все же проблема в сотовой связи приемников ?
     
    #75
  16. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
    Проблема еще может быть в интернет-канале на ПК.
     
    #76
  17. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    Короче так просто проблему выявить не очень то и просто, будем пробовать методами исключений!
    --- Сообщения объединены, 28 апр 2015, Оригинальное время сообщения: 28 апр 2015 ---
    вот еще после пропадания FIXED, приемник пишет DIP connection failed
    --- Сообщения объединены, 28 апр 2015 ---
    04:33:14: Receiver Startup
    04:33:14: RTC read: 21/04/2015
    04:33:14: SP80 SN:5417900065 Ver:1.3
    04:33:14: PCNT read: 1
    04:33:14: Current configuration loaded (CURRENT1.UCF)
    04:33:14: GSM : switched OFF
    04:33:21: GSM : switched ON
    04:33:39: GSM PSD: Connected on GPRS (APN=mts, Login=mts, Password=
    04:35:14: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    04:35:14: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    04:35:14: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    04:35:24: config CURRENT.UCF file saved
    04:35:24: checksum config CURRENT.UCF saved
    04:35:24: Configuration Index 1 saved
    05:15:33: WARN,10(11),Data write error on network
    05:15:33: Port P: DIP connection lost
    05:15:33: WARN,14(0),P,DIP connection lost
    05:15:33: Port P: Disconnected
    05:15:33: Port P: Process automatic Redial
    05:15:33: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:15:33: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:15:34: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:15:34: ClientNetworkIP P: the connection has been gracefully closed by host
    05:15:34: Port P: DIP connection lost
    05:15:34: WARN,14(0),P,DIP connection lost
    05:15:34: Port P: Disconnected
    05:15:34: Port P: Process automatic Redial
    05:15:35: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:15:35: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:15:39: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:15:39: ClientNetworkIP P: the connection has been gracefully closed by host
    05:15:39: Port P: DIP connection lost
    05:15:39: WARN,14(0),P,DIP connection lost
    05:15:39: Port P: Disconnected
    05:15:39: Port P: Process automatic Redial
    05:15:40: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:15:40: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:15:44: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:15:45: ClientNetworkIP P: the connection has been gracefully closed by host
    05:15:45: Port P: DIP connection lost
    05:15:45: WARN,14(0),P,DIP connection lost
    05:15:45: Port P: Disconnected
    05:15:45: Port P: Process automatic Redial
    05:15:45: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:15:45: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:15:50: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:15:51: ClientNetworkIP P: the connection has been gracefully closed by host
    05:15:51: Port P: DIP connection lost
    05:15:51: WARN,14(0),P,DIP connection lost
    05:15:51: Port P: Disconnected
    05:15:51: Port P: Process automatic Redial
    05:15:51: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:15:51: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:15:56: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:15:56: ClientNetworkIP P: the connection has been gracefully closed by host
    05:15:56: Port P: DIP connection lost
    05:15:56: WARN,14(0),P,DIP connection lost
    05:15:56: Port P: Disconnected
    05:15:56: Port P: Process automatic Redial
    05:15:57: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:15:57: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:01: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:01: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:01: Port P: DIP connection lost
    05:16:01: WARN,14(0),P,DIP connection lost
    05:16:01: Port P: Disconnected
    05:16:01: Port P: Process automatic Redial
    05:16:02: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:02: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:05: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:06: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:06: Port P: DIP connection lost
    05:16:06: WARN,14(0),P,DIP connection lost
    05:16:06: Port P: Disconnected
    05:16:06: Port P: Process automatic Redial
    05:16:06: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:06: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:11: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:11: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:11: Port P: DIP connection lost
    05:16:11: WARN,14(0),P,DIP connection lost
    05:16:11: Port P: Disconnected
    05:16:11: Port P: Process automatic Redial
    05:16:12: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:12: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:16: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:16: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:16: Port P: DIP connection lost
    05:16:16: WARN,14(0),P,DIP connection lost
    05:16:16: Port P: Disconnected
    05:16:16: Port P: Process automatic Redial
    05:16:17: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:17: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:26: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:27: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:27: Port P: DIP connection lost
    05:16:27: WARN,14(0),P,DIP connection lost
    05:16:27: Port P: Disconnected
    05:16:27: Port P: Process automatic Redial
    05:16:27: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:27: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:32: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:32: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:32: Port P: DIP connection lost
    05:16:32: WARN,14(0),P,DIP connection lost
    05:16:32: Port P: Disconnected
    05:16:32: Port P: Process automatic Redial
    05:16:33: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:33: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:37: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:38: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:38: Port P: DIP connection lost
    05:16:38: WARN,14(0),P,DIP connection lost
    05:16:38: Port P: Disconnected
    05:16:38: Port P: Process automatic Redial
    05:16:38: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:38: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:38: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:39: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:39: Port P: DIP connection lost
    05:16:39: Port P: Disconnected
    05:16:39: Port P: Process automatic Redial
    05:16:39: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:39: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:42: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:43: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:43: Port P: DIP connection lost
    05:16:43: WARN,14(0),P,DIP connection lost
    05:16:43: Port P: Disconnected
    05:16:43: Port P: Process automatic Redial
    05:16:43: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:43: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:46: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:47: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:47: Port P: DIP connection lost
    05:16:47: WARN,14(0),P,DIP connection lost
    05:16:47: Port P: Disconnected
    05:16:47: Port P: Process automatic Redial
    05:16:47: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:47: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:52: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:52: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:52: Port P: DIP connection lost
    05:16:52: WARN,14(0),P,DIP connection lost
    05:16:52: Port P: Disconnected
    05:16:52: Port P: Process automatic Redial
    05:16:52: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:52: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:16:55: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:16:56: ClientNetworkIP P: the connection has been gracefully closed by host
    05:16:56: Port P: DIP connection lost
    05:16:56: WARN,14(0),P,DIP connection lost
    05:16:56: Port P: Disconnected
    05:16:56: Port P: Process automatic Redial
    05:16:56: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:16:56: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:00: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:01: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:01: Port P: DIP connection lost
    05:17:01: WARN,14(0),P,DIP connection lost
    05:17:01: Port P: Disconnected
    05:17:01: Port P: Process automatic Redial
    05:17:01: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:01: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:02: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:02: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:02: Port P: DIP connection lost
    05:17:02: WARN,14(0),P,DIP connection lost
    05:17:02: Port P: Disconnected
    05:17:02: Port P: Process automatic Redial
    05:17:03: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:03: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:07: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:07: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:07: Port P: DIP connection lost
    05:17:07: WARN,14(0),P,DIP connection lost
    05:17:07: Port P: Disconnected
    05:17:07: Port P: Process automatic Redial
    05:17:08: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:08: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:11: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:11: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:11: Port P: DIP connection lost
    05:17:11: WARN,14(0),P,DIP connection lost
    05:17:11: Port P: Disconnected
    05:17:11: Port P: Process automatic Redial
    05:17:12: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:12: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:12: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:12: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:12: Port P: DIP connection lost
    05:17:12: WARN,14(0),P,DIP connection lost
    05:17:12: Port P: Disconnected
    05:17:12: Port P: Process automatic Redial
    05:17:13: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:13: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:16: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:16: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:16: Port P: DIP connection lost
    05:17:16: WARN,14(0),P,DIP connection lost
    05:17:16: Port P: Disconnected
    05:17:16: Port P: Process automatic Redial
    05:17:17: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:17: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:20: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:20: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:20: Port P: DIP connection lost
    05:17:20: WARN,14(0),P,DIP connection lost
    05:17:20: Port P: Disconnected
    05:17:20: Port P: Process automatic Redial
    05:17:21: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:21: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:25: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    05:17:25: ClientNetworkIP P: the connection has been gracefully closed by host
    05:17:25: Port P: DIP connection lost
    05:17:25: WARN,14(0),P,DIP connection lost
    05:17:25: Port P: Disconnected
    05:17:25: Port P: Process automatic Redial
    05:17:26: Port P: DIP connection requested (IP:31.163.203.42 PRT:3000)
    05:17:26: Port P: Trying to connect to DIP (IP:31.163.203.42 PRT:3000)
    05:17:35: Port P: DIP connected (IP:31.163.203.42 PRT:3000)
    07:22:28: Switch Power from Battery A to Battery B
    08:07:28: Port P: Disconnect requested
    08:07:28: Port P: Disconnected
    08:07:30: GSM : switched OFF
    08:07:31: config CURRENT1.UCF file saved
    08:07:31: checksum config CURRENT1.UCF saved
    08:07:31: Configuration Index 2 saved
    08:07:31: PCNT read: 1
    08:07:31: Receiver Power Off
    --- Сообщения объединены, 28 апр 2015 ---
    ВОТ ОТЧЕТ!
    --- Сообщения объединены, 28 апр 2015 ---
    DIP connection failed не правильно написал DIP connection lost
     
    #77
  18. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
    Вот тут у вас, насколько я понимаю, отпал сотовый интернет.

    А вот тут - проблема с интернетом на ПК.
     
    #78
  19. amax32

    Форумчанин

    Регистрация:
    18 дек 2013
    Сообщения:
    122
    Симпатии:
    8
    Про сотовый интернет разговора нет, я сам соглашусь что бываем в таких местах где интернет действительно очень слабый!! значит есть проблема в сети интернет на ПК, может можете подсказать как это решить? или это просто не решаемое действие
     
    #79
    Vlad2000 нравится это.
  20. Ringo

    Форумчанин

    Регистрация:
    22 мар 2010
    Сообщения:
    718
    Симпатии:
    141
    Привлечь системного администратора, чтобы провел диагностику сети и интернета.
     
    #80

Поделиться этой страницей

  1. Этот сайт использует файлы cookie. Продолжая пользоваться данным сайтом, Вы соглашаетесь на использование нами Ваших файлов cookie.
    Скрыть объявление