-
Firmware image and ReachView version.
Reachview 2.9.0 -
System report.
How do I get it? -
Detailed problem description. How does observed behavior differ from the expected one?
Reach gets 5V regulated power from DF13 and is connected through USB OTG to an ethernet to USB from D-Link model DUB-E100; USB 2.0 Fast Ethernet Adapter (10/100Mbps) and plugged to a router with a fixed IP address for the DUB-E100 MAC address.
The system randomly boots peacefully and ReachView boots up. Sometimes Reach boots, and we can SSH into it but ReachView returns a HTTP 403 error forbidden. -
Your step by step actions.
Turn off any source of Wifi known to Reach
Boot reach
Go to webpage. If this doesn’t work, ssh root@FIXED_IP always works.
Click the setting icon in ReachView (the little gear), then you will see it on that page.
The first thing to ask is did you wait long enough for ReachView to get started? The second thing to ask is if the times when ReachView is not available correlate to times when satellite visibility is poor or non-existent? (If you can ssh in, then can you run time_sync
successfully and see the current time?)
Simple system report
app version: 2.11.0-r0
'wifi_status, interface: wlan0':
- Client state
- IP address: 192.168.1.200
mac address: 90:b6:86:02:f2:7b
ssid: SRV_UW
base mode:
base coordinates:
accumulation: '2'
antenna offset:
east: '0'
north: '0'
up: '0'
coordinates:
- '0'
- '0'
- '0'
format: llh
mode: single-and-hold
output:
enabled: true
format: rtcm3
path: tcpsvr://:9000#rtcm3
type: tcpsvr
rtcm3 messages:
'1002':
enabled: true
frequency: '1'
'1006':
enabled: true
frequency: '0.1'
'1008':
enabled: false
frequency: '1'
'1010':
enabled: true
frequency: '1'
'1019':
enabled: false
frequency: '1'
'1020':
enabled: false
frequency: '1'
'1097':
enabled: false
frequency: '1'
'1107':
enabled: false
frequency: '1'
'1117':
enabled: false
frequency: '1'
'1127':
enabled: false
frequency: '1'
bluetooth:
discoverable: false
enabled: false
pin: '***'
camera:
duty cycle: 20
enable: false
period: 2
polarity: true
correction input:
input2:
enabled: true
format: rtcm3
path: srvgroup:***@www.euref-ip.net:80/MALL0
send position to base: 'off'
type: ntripcli
input3:
enabled: false
format: rtcm3
path: srvgroup:***@www.euref-ip.net:80/BCLN0
type: ntripcli
logging:
base:
format: RTCM3
started: true
version: null
correction:
format: RTCM3
started: true
version: null
interval: 24
overwrite: true
raw:
format: UBX
started: true
version: null
solution:
format: LLH
started: true
version: null
position output:
output1:
enabled: true
format: llh
path: :9001
type: tcpsvr
output2:
enabled: true
format: llh
path: :2013
type: tcpsvr
output3:
enabled: true
format: llh
path: :2014
type: tcpsvr
output4:
enabled: true
format: llh
path: :2015
type: tcpsvr
rtk settings:
elevation mask angle: '15'
glonass ar mode: 'off'
gps ar mode: fix-and-hold
max horizontal acceleration: '1'
max vertical acceleration: '1'
positioning mode: kinematic
positioning systems:
compass: false
galileo: false
glonass: true
gps: true
qzs: true
qzss: true
sbas: true
snr mask: '35'
update rate: '5'
I just ugraded everything to last version, 2.11 through USB & Wifi. I’ll test the board now with the “field setup” using a ethernet to USB and see if its working.
Regarding the question of waiting time, yes. I was with a team of people working for 4-5 hours in the field and emlid did not get to the ReachView. We tried to power cycle it several times to no avail.
If it does happen again, I’ll print the time_sync.
Our setup involves using Emlid Reach ontop of a mooring buoy in the sea. It has unobstructed sky view, that can be partially covered by nearby mountains when working close to shore. However, I don’t think that’s an issue.
Now in 2.11 I can connect through USB and Wifi directly, but not using the Ethernet to USB cable.
I’m trying the system indoors, and its booting with direct USB connection and also using DB13 power and wifi. However, I cannot connect to it using the DUB-E100 anymore.
The command time_sync (when on usb or wifi) does not return anything.
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.