@brian.crane wrote:
I am new to using Emlid Reach units. I am in the United States, and want to verify what frequency I can use for my base and rover that is allowed in my area (State of Maryland, United States). My guess is 915 MHz, but I’m not sure. Any US users out there who can help?
Posts: 3
Participants: 3
@benefactum.xyz wrote:
Hello friends, I am writing from Colombia.
I have two (2) Emlid Reach RS and I have tried in every way to achieve an optimal correction in RTK mode, transmitting corrections for LoRa radio, but I rarely get a correction in FIX and if this happens I must be less than 20 meters away. base. FLOATING always comes out.
When I transmit the base corrections by NTRIP it works perfectly and I have achieved FIX corrections more than 8 km from the base.
Which for you should be the best configuration to achieve a good transmission by LoRa radio and that at least can achieve the correction up to 1 km away?
Posts: 2
Participants: 2
@farhan wrote:
Hi,
Thanx for continouos support.Is it possible that base and rover communicate through VPN because I dont want to use static ip for rover .Base is connected to a LAN.I want to make a VPN so that rover can join this LAN.I am using 3G device for interne connectivity with rover.
Posts: 3
Participants: 2
@gedwards wrote:
Has anyone been able to connect the Reach RS+ to Trimble’s Terrasync? I have a Nomad 800GLE that Im not having much success with.
Posts: 2
Participants: 2
@michielluijken wrote:
Hello Emlid community,
I am completely new to gps (and no survey background) and just discovered this forum
I have just ordered an Emlid Reach RS+ Base and Rover and it on its way
I am pretty excited and realise there is quite a bit of study to do, but I am confident I could manage.
I want to start using it for stockpile (volume) measurements and bathymetric survey
I only want to use it a local grid and set my base point origin at 0,0,0I am worried that I might have over looked the fact that export is only in lat, long
And that converting co-ordinates to a x,y,z grid in meters is not that simpleI found a thread with exactly the same issue but unfortunately its closed (is it not better to just keep open?)
But I did not really find a simple solution, this is the link to the thread:
Can somebody point me in the right direction? or give some other solutions (i.e. budget is gone after this purchase) Accuracy is not that critical but should be less than 30cm, so I need a correction on a standard GPS
Thanks!
Michiel
Posts: 2
Participants: 2
@rsparihar10 wrote:
Hi,
I am using Emlid Edge as a autopilot for my Quadcopter configuration. I am using Q-ground control station as the GCS. I want to control my gimbal with the joystick instead of RC. Gimbal specification is:- Foxtech FH310Z 1080P Camera 3-axis gimbal.
Can you provide me details of joystick connection for gimbal control to Emlid Edge and settings to Q-GCS. If there is any manual for the same kindly provide that too.
Also, if possible ,please let me know what are the best gimbal controllers beside RC available in market best configurable to Emlid Edge.
Thanks & Regards,
Rakshita Parihar
Posts: 1
Participants: 1
@paul.ebbenga wrote:
Something appears to be wrong with how my Navio 2 is receiving the SBUS signal from receiver. When I go to radio calibration in ground control the channel monitor dots are all over the place and not moving in correspondence with my stick inputs. I am running servo cable from SBUS port (connected in the right direction) on the receiver to the PPM-SB port on servo rail next to channel 1 with bottom pin being ground. Radio is SBUS paired indicated by purple light on receiver and signal bars from transmitter. Channel monitor does move with stick inputs but in extremely erratic fashion.
FC: Navio 2 w/ RPI3 b+ w/ ADP v 3.5
GC: QGroundControl v.3.32
Transmitter: Radio Link AT9S
Receiver: Radiolink R9DS
Posts: 1
Participants: 1
@chrisb wrote:
Hi,
I received a new M+ a few days ago and have been having lots of problems with wifi connections.First experience was positive : I was quickly able to connect to the M+ hotspot, then switch over to my local wifi AP, and update firmware to 2.14.
After that, it’s been nothing but mysterious behaviour. Note : all these tests have taken place in the same room as the AP router, same location where I did the initial setup . I configure the M+ through the reachview webUI served from its hotspot.
sometimes my local wifi doesn’t even appear in the list of available networks; it says “saved (not available)”, showing 0 signal strength.
sometimes my local wifi appears, with full signal, but it can’t connect : when I manually try to connect, I lose the hotspot connection (of course), I see my router give the M+ a DHCP lease, but I can never ping that IP ; the M+ soon restarts in hotspot mode.
sometimes I can connect to the local wifi, then I try to walk outside (10m away) to get better gps signal, but it’s apparently too far for the M+ wifi transceiver so the connection drops out. Walking back inside doesn’t always succeed in restoring the connection. And if it does, the stream for TCP corrections will not restart. This is disappointing but not unexpected.
in hotspot mode, the M+ seems solid. But, I want to use RTCM corrections from a TCP stream, so it’s not really an option, unless I can somehow set up a computer with internet access to pipe the RTCM stream over the hotspot link… not great.
Anybody else having wifi issues ? I thought of trying the 2.15 dev release but I was discouraged by the “cannot downgrade afterwards” warning.
Posts: 3
Participants: 3
@tejones777 wrote:
Hello from a new user:
I just received my REACH RS+ last Friday, and have been having a blast. But a few questions.
My setup is just a single Reach RS+, but my state (Minnesota, USA) has a great free CORS
system, giving GPS and GLONASS corrections throughout the state. Not using the LoRa,
in fact not even using Bluetooth (I had planned to use LeFebure NTRIP and then mock
locations to my cell, then to Mobile Topographer but the Reachview application, with built in
NTRIP, and simple survey program, works better.) With CORS, I’m able to get a few
centimeters accuracy when measuring several government Geodetic monuments nearby.But a few questions/concerns:
Turning on Galileo satellites seems to crash the engine:
I can’t reproduce this well, but if I have GPS, and Galileo, and Glonass, possibly when
battery is a bit low, something bad happens. The number of satellites on the STATUS
display falls to about 4-5 GPS satellites, and while green, it won’t calculate even a low
quality position. But also the signal strength bars stay up about 5-6 seconds, then collapse
down, then come back, then collapse, over and over again, like some internal error or
electrical fault makes an internal error and reset. I spent about 4-5 hours yesterday, trying
to figure it out, and when I plugged in my Reach RS+ to charge it, I noticed I got a few more
satellites, and then when I turned off Galileo satellites, all the GPS satellites and Glonass
satellites came back, and it started to generate positions again.
Has anyone else had a problem like this? I may have had a position update rate too fast
for so many satellites. But again, I haven’t been able to reproduce this well. Has anyone
else seen this? I’m trying to reproduce it, and it may even only occur when I’m using
correction data, as turning off corrections made it work.Reachview App on my Phone usually can’t find my Device:
When my Reach RS+ is supplying it’s own hot-spot, my Android Reachview App seems to
find it quite well, but when I have a local network that my RS+ joins, the Android Reachview
App doesn’t seem to be able to find any devices. I tried turning on and off mobile data,
but that doesn’t help. I’m using a Galaxy S9+ phone. I know my RS+ device is there, and
if I can figure out the IP address, I can connect to it via a web browser.
My main workaround is that I usually use my phone as a mobile hotspot, so it sets up a local
network that the RS+ can attach to, then I can see all the IP addresses of devices attached
to my hotspot, so figure out the RS+'s local IP address (192.168.0.XXX). Then I just open it
in a web browser on my phone, and bypass the Application.Kinetic/Static switching:
I have two needs: I need to survey existing locations, and get accurate position descriptions,
and I have to track toward known locations, and place markers there.
I had been using exclusively Kinetic RTK positioning to find position of markers, but it seems
to take long occupy times, and due to trees, I often lose a FIX lock while waiting. Then I found
that the STATIC RTK positioning really works great. I go to my location, turn on STATIC, and very
quickly I get a high quality lock, even if signals aren’t perfect, and trees in area. Then I can do a
collection in just a short occupy time, as the FIX is super stable. The problem comes when I go
to my next location while in STATIC mode, it takes forever for the RS+ to let go of the old position
fix, and realize I actually moved. So I have to switch back to Kinetic mode, go to new position, then
switch back to STATIC. This this how we have to do it? Keep switching to Kinetic mode to let go
of the old position, then switch back to STATIC once I’m ready to occupy the new location? Is there
a better way to do this without switching back and forth?No Warranty?
When my Reach RS+ was malfunctioning yesterday, and couldn’t get hardly any satellites, and not
able to lock even a float position, I thought I had a bad device, and worried I was going to have to
ship it off to Emlid in Hong Kong for a replacement. I figured that may cost me a ton even with
economy shipping, and At best, I’m going to be without my device for a couple weeks. Then I wished
I wouldn’t have bought direct from EMLID, and would have gotten from RobotShop.com (a US/Canada
based dealer) as I may have been able to return to them. But then I realized “there’s no warranty!”
I looked over RobotShop’s web site, they say most items don’t have warranties, and you gotta contact
manufacturer. But then I searched this entire FORUM and realized nobody knows what to do when
these stop working. If the battery goes bad, maybe you can try to replace it yourself, otherwise you
have to toss it, and buy another? It seems like there should at least be a 30-day replacement warranty
in case a device goes dead right away. But I’m terrified, after spending half the day yesterday to get it
to pick up satellites, that this thing is going to turn into a brick, no matter how much I baby it, and it’s
trash. Yes, it’s cheaper than a LEICA or TOPCON, doesn’t mean I can afford for it to die, and just buy
another.Any thoughts or comments would be appreciated. I’m new to this, but so far can get high accuracy
positions with some work-arounds. I’m very happy with my device.
- Thomas.
Posts: 4
Participants: 3
@electricblue wrote:
I’m setting up my new Reach RS+ with my local VRS RTN (it says connected under correction input) then under position output I connected it to an android phone with ESRI Collector on it and changed the GPS receiver to the RS+. I took it outside and its using 16 satellites mostly green bars but my PDOP in Collector is well over 18 feet. What could I be doing wrong here and how do I troubleshoot it? In the ReachView status screen it says LLH ± 0.0000000m which seems wrong, and I have no idea if/how the corrections are being applied. Thank you and sorry for the newbie question
Posts: 1
Participants: 1
@panthony wrote:
Just received two new RS+ devices. Followed all directions precisely. Can see Wifi on both devices however cannot connect to one and the other connects but ReachView hangs indefinitely.
ReachView App - V1.4
Any advice would be appreciated.
Posts: 13
Participants: 4
@redsoxgs12 wrote:
I am new to Raspberry Pi and Navio2. I have successfully built and run most of the sample code documented here:
https://docs.emlid.com/navio2/common/dev/
My project requires that I send both GPS data (Lat, Long, Altitude, Velocity, Track angle, etc…) and IMU data (pitch, roll, heading) over TCP to another piece of hardware on the network. The AHRS example sends IMU data over TCP, and the GPS w/uCenter example sends GPS data over TCP. Is it possible to access both sets of data from the same C++ code? It’s not obvious to me how the two sets of code could be combined to put everything I need into a single executable. If anybody has done something similar, I would love to see some sample code.
Posts: 2
Participants: 2
@tejones777 wrote:
Hello:
I have a Reach RS+, the newer model which reportedly can be turned on and off through supplying power on the 9-pin circular connector on the bottom. I’ve seen in the docs that this feature, being able to turn the receiver on when power is applied, and off when power removed, is available through the Reachview software, but for the life of me, I can’t find it anywhere in the program. Does anyone know where that control is?
Second problem, the 9-pin circular connector, which contains serial data input/output, and external power supply input (5-40 volts, I think) seems to be similar to a LEMO connector, model 0B, but I’m not certain, and it doesn’t specify anywhere what the exact connector compatibility is. Is it true that this is a LEMO 0B compatible connector?
I know, I shouldn’t care, and just buy the adapter off of the EMLID store, but after shipping costs, it’s about $65.00, and I can probably get one much cheaper elsewhere. My local EMLID dealer (Robotshop.com) does not have such accessories.
Any help on the connector type/size/standard, and where you control external power on/power off in Reachview, would be appreciated.
- Thomas E. Jones
Posts: 2
Participants: 2
@vincityhn1 wrote:
I have developed drifters using Reach modules and successful in measuring Rip currents. I want to check the position of drifter in real-time. Presently I’m logging the data in the reach modules and post processing the data after retrieval.
Can anyone suggest whether Reach is able to transfer the data in real-time either with additional GPRS module or through satellite link. Still raw data can be logged in the modules for post processing for accurate position. I don’t want to use NTRIP or in RTK mode as they have their own limitations. I want to utilize them in measuring River currents. There are chances of getting lost. Real-time position facility would help to monitor it’s movement and can help in retrieval in case of lost.
Thanks in advance.
Posts: 2
Participants: 2
@dmitriy.ershov wrote:
We are thankful to everyone who has been sharing photos with the #emlidreach hashtag for the past month! Today we announce the results of Emlid Photo Contest 2018.
We’ve got entries from 18 countries from users working in 8 various industries. Special thanks to Drone Mapping Pilots for being very active in sharing the projects!
Main Prize: Reach RS+
The main prize goes to Archaeo Perspectives for the photo from the maritime archaeological site in Italy.
Winning Entries of Emlid Photo Contest 2018
We’ve also selected ten Emlid T-Shirt Winners!
- Bathymetric survey by HELImetrex
- Irrigation channel survey by Santy Arteaga
- Mapping the structure of volcanic pit craters by @nuttabomber
- Archaeological survey in the urban environment by Mjesto Pod Suncem
- Sea depth survey by Sayorn Dim
- Tractor autosteering by Pierre Sartena
- Landslide mapping by Karl Wegmann
- Land survey and documentation by Ferry Aristanto
- Mines and quarries mapping by Colminerals S.A.S
- Potato fields drone survey by Keith Geary
Check the list of the contest winners and see more stunning photos in our blog!
To claim the prize please contact us on info@emlid.com.
Congratulations to the winners! We truly appreciate everyone who had taken the time and effort to participate!
Posts: 2
Participants: 1
@Fisek wrote:
I bought the following transmitter and receiver ( https://hobbyking.com/nl_nl/frsky-2-4ghz-accst-taranis-x9d-x8r-plus-telemetry-radio-system-mode-2-eu-version.html ). The receiver is x8r.
But currently i am having issues connecting to Navio2. Could you please let me know what are the configurations (hardware & software) you did both on transmitter, receiver and Navio2 side?
Kind regards.
Posts: 2
Participants: 2
@Ben_Evans wrote:
I am seeing drift in fix positions when my rover is static. This is processed in RTKLib against a Leica base station RINEX. The Reach was static for about 20 minutes and the XY positions show a drift in the order of a metre with fix solutions. The Z is (almost) acceptable in terms of stability). See attached plot.
I am using a new Reach M+ which wasfired up for the first time and updated a couple of weeks ago (sorry, I don’t have it to hand to post the reachview version but I assume it is the latest).
The antenna (shipped with M+) is on a 100mm aluminium base plane on a mast on a quadrotor drone (all switched off during test - see photo). Interestingly I didn’t see drift when I tried last week in almost the same location with the antenna not attached to the drone (or base plane).
I’ve tried fiddling with config parameters and get varying proportions Q1, but whenever I get fix solutions I see the drift. Interestingly, when the values only achieve float the drift is less pronounced/non-existent but, as expected, there is more ‘noise’.
I attach the log files and the config I’m using in RTKLib.
Any suggestions or help would be greatly appreciated, since 1m drift over 20 minutes might not be noticeable in a moving survey but would definitely ruin the results.
raw_201810011519.nav (21.6 KB)
raw_201810011519.pos (581.7 KB)
raw_201810011519.obs (6.6 MB)
Config_921_WithXYdrift.zip (1.6 KB)
1407274p18.zip (4.5 MB)SystemReport.zip (105.5 KB)
Posts: 2
Participants: 1
@geoetudes3d wrote:
is it possible to take a tilted and precise reading with Emlid Reach RS GNSS RTK, like the corners of a building for example?
Posts: 1
Participants: 1
