Replies

  • We try to use ublox m8x chip to discover a base-rover trk system. and the result is good . from system on to get fix time usually use only 2min,,And wo want to provide some board for DIYs to test the system in different country.You can visit the www.i-rtk.com to submit you information for demo.

  • We did a RTK base, based on M8T for remote monitoring purposes. It includes a long range radio (>8 km with directional antennas) and solar power management (10W panel). The device can communicate each other to do a mesh network. We use the same device as base and rover and we achieved sub-centimeter (in some case sub-millimeter on 24h series) accuracy in quasi real time. RTK SW is proprietary but you can use RTKLIB for cm accuracy. We have 5 devices on a mountain in Italy since last august.

  • I'm playing around with emlid.com's stuff, the NEO-6T USB dongles. I bought two for my laptop to get started. I get fixes using very cheap antennas and I'm going to upgrade to some better ones to improve the performance. Improving the performance mostly means that the time to get a fix is reduced.

    With these not-so-good antennas, I lose the fix the moment I nudge the antenna a bit. If you look online on topics relating to RTK, RTKLib and some applications, they often state that L1+L2 is a requirement for moving vehicles... maybe it will track ok if you move slow enough. L1+L2 receivers and antennas perform much better, but immediately move out of a comfortable price range ($2k?). Good, small antennas for L1/L2 start at $350. But if you set up a base with such a system and put one on your car, it tracks really great. The reason why is that L2 provides more information to the receiver and uses a slightly different frequency as well, so that it's easier to resolve ambiguities and get the fix back (i.e., you need less time in a specific position to know where you are and this is important when you're moving at a certain speed).

    The way I see it is that L1 is good if you want a dirt-cheap solution for doing measurements in the field using static rovers and bases. So when you do surveys you can take ground control points with good accuracy too. If you don't have time to wait around for the base station's position to converge really well, you can still *use* the fixes from the rover, but the positions will all be shifted by a certain amount. However, this already helps you to provide a photo in the correct scale and the geo control points help your processing software to resolve camera parameter ambiguities, so you get better looking photos. I don't really use GPS data in camera's because the ground control method is so much better in terms of accuracy.

    Resuming: for DIY and cheap stuff, I don't think RTK works yet, because it only uses L1 band. It's possible that the piksi however greatly improved on this (uses galileo and some other satellite systems), but at the same time I haven't seen people bragging about their piksi RTK drones with super high accuracy.

    You need computer power onboard as well to process the raw data. But some modules have multiple uart's, so they can produce NMEA data on one to the AP and then raw data to the onboard computer. A very interesting project then would be to dynamically filter the two using their relative certainty. So you always fall back on the normal GPS, but when the RTK fix improves, it helps to get a better fix position. On multirotors this is probably easier, because they can hover and therefore make it less prone to errors due to the vehicle's constant velocity.

This reply was deleted.

Activity

DIY Robocars via Twitter
yesterday
DIY Robocars via Twitter
RT @SmallpixelCar: @a1k0n @diyrobocars I learned from this. This is my speed profile. Looks like I am too conservative on the right side of…
yesterday
DIY Robocars via Twitter
RT @a1k0n: @SmallpixelCar @diyrobocars Dot color is speed; brighter is faster. Yeah, it has less room to explore in the tighter part, and t…
yesterday
DIY Robocars via Twitter
RT @a1k0n: I'm gonna try to do proper offline reinforcement learning for @diyrobocars and throw away all my manual parameter tuning for the…
Friday
DIY Robocars via Twitter
RT @circuitlaunch: DIY Robocars & Brazilian BBQ - Sat 10/1. Our track combines hairpin curves with an intersection for max danger. Take tha…
Thursday
DIY Robocars via Twitter
RT @SmallpixelCar: Had an great test today on @RAMS_RC_Club track. However the car starts to drift at 40mph. Some experts recommended to ch…
Sep 11
DIY Robocars via Twitter
RT @gclue_akira: 世界最速 チームtamiyaのaiカー https://t.co/1Qq2zOeftG
Sep 10
DIY Robocars via Twitter
RT @DanielChiaJH: Always a good time working on my @diyrobocars car at @circuitlaunch. Still got some work to do if I’m to beat @a1k0n howe…
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: My new speed profile for @RAMS_RC_Club track https://t.co/RtLb7TcgIJ
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: Practiced at @RAMS_RC_Club today with my new @ARRMARC car https://t.co/AEu2hCx89T
Aug 28
DIY Robocars via Twitter
Aug 24
DIY Robocars via Twitter
RT @gclue_akira: 柏の葉で走行させてるjetracerの中身 #instantNeRF #jetracer https://t.co/giVvuE4hP7
Jul 4
DIY Robocars via Twitter
Cool web-based self-driving simulator. Click save when the AI does the right thing https://github.com/pncsoares/self-driving-car
Jul 4
DIY Robocars via Twitter
RT @donkey_car: Human-scale Donkey Car! Hope this makes it to a @diyrobocars race https://www.youtube.com/watch?v=ZMaf031U8jg
Jun 25
DIY Robocars via Twitter
Jun 25
DIY Robocars via Twitter
Jun 16
More…