Comment by kiki boy on September 13, 2016 at 7:57am

Of course ! There is issue you don't want to solve ...

Comment by DROTEK on September 13, 2016 at 8:07am

We are working on the issues, it is a lot of work and you cannot expect us to release a new version for every issue. We try to offer a large range of products, from the open source projects to the high-end final user boards and this needs high human and technical resources. Open-source does not mean posting an issue and expect it to be resolved fast, it also means contributing actively and constructively. So please take this into consideration.

Comment by kiki boy on September 13, 2016 at 8:15am

I took it into consideration. I work since 10 years with opensource projects ...

You put it on github and you say it's opensource but not all the conf files are on it. And now you will remove it that's why I said that. by the way good luck !

Comment by DROTEK on September 13, 2016 at 8:17am

@kiki boy :

Only the wiki has been moved to our website for a better visibility. The project remains open-source and all the files are on Github.

Comment by kiki boy on September 13, 2016 at 8:19am

No platform dependant from yocto are not on github ...

Comment by DROTEK on September 13, 2016 at 8:34am

@ kiki boy :

Yes they are. You will find all the files (SmartNav's file system) inside tar.gz archive under Update folder + installation scripts. Anyway, we don't think this is the best place to discuss this so we will contact you through our support platform.

Comment by satapathy on September 14, 2016 at 5:36am

Is there an option with PATCH Antenna on the PCB itself? I don't want to connect to an external antenna.

Comment by Nikola Rabchevsky on September 14, 2016 at 7:46am

Having played with the developer kit for a few months, I can tell you that this is a pretty cool product.  The correction messages could easily be encapsulated in other wireless protocols (I've done it) so secondary radio links aren't necessary.  That said, there is one issue to be aware of.  It can take 3-6 minutes to obtain an RTK fix and the solution can wander around a lot before it gets a fix.  So it probably wouldn't be a practical product for UAVs with limited flight time.  Also, the output rate is only 5 Hz so you'd need to rely more heavily on the INS code in an autopilot to predict positions particularly at high speeds.  If this ran at 10 Hz or better, that would be really cool.  As to the fix time issue, I can envision a power umbilical on the ground with a large battery that would run the electronics until it gets a fix without drawing from the onboard power supply.  It would be a bit like rockets topping off fuel tanks right up until launch.

Comment by AJ152 on September 14, 2016 at 8:13am

@DROTEK It looks awesome guys, still wondering though how is this new module (either the base or station) going to interface with a Pixhawk. Thanks.

Comment by Olivier on September 14, 2016 at 7:10pm

@Nikola Glad you've had a positive experience, looks like a very attractive new product. Regarding 3-6 minutes to get a fix, not sure what you mean by "probably wouldn't be a practical product for UAVs with limited flight time"? Without motors running autopilot current draw is typically 250ma, maybe 500ma-1A for everything  tops if loaded with peripherals. At least with something like PixHawk.  A drop in the bucket compared to current draw while flying, so no issue waiting 5 minutes or more. Or maybe I am missing something.

With respect to 5HZ updates limitation, yes would be nice if faster updates were possible. Wonder how much of a difference it would actually make, though. Ardupilot for instance expects and implements 5HZ, even with GPSs capable of more, and my understanding is that faster updates don't actually result in better performance with current EKF and typical non RTK GPSs. With cm precision GPS the game of course changes, I am just wondering by how much.

Comment

• ‹ Previous
• 1
• 2
• 3
• 4
• Next ›
• Page