Recent content by Ian [P13]

This isn't something I could answer as I've had no need to investigate CANBUS, I only get involved with things technically when I'm hands on using them. Anything developed now, especially using companion computers is going to be done with the Pixhawk 2.1 in mind, likely alongside an Intel Edison.

I've heard a rumour a CANBUS gimbal for Arducopter that'll provide Solo like functionality is in development but you didn't hear that from me. ;) I'm hoping Solo's code becomes entirely open one day, 3DR overall have been good with end of line gear, although Solo isn't seen as end of line yet...

I should add, there's some very positive noises about Solo code in the future, with the suggestion there's some ex-3DR staff willing to help build on the existing non-Arducopter code so that once Solo is on Master it needn't just be the flight controller code that will evolve. So I've got my...

The FETs were the component that was blowing prior to the software change. A capacitor is the component that is replaced on the ESC for Sitescan.

The Sitescan ESCs are the same, albeit a capacitor has been changed. That's all I know. So they take a normal Solo motorpod and they manually make changes to the ESC and the Sitescan Solo also has an M8N put in as well.

The changes that were originally put in are still there, however, there are some other changes in the same motor code and I wouldn't want to speculate on whether they would pose a risk or not, however I'd suspect not. I'd just keep an eye on changes before committing firmware in future. I can...

This was the fix (motor slew rate limiter for current limiting): Release solo-1.2.3 · 3drobotics/ardupilot-solo · GitHub So you need to make sure changes haven't happened recently to the following code that could drive the ESCs harder: ardupilot-solo/libraries/AP_Motors/AP_MotorsMatrix.cpp...

The motors on Solo are perfectly fine, the teathered Solo ran over 40 days 24/7 then at NAB so the motors last well past the suggested replacement time of around 150 hours. Any motor pods failures have been due to ESCs and not motors. It's a FET that is different on the Sitescan Solo ESCs.

It's not a parameter it's the motor slew that is hard coded, so that needs checking. Don't expect an obvious release note as the fix was confidential.

It's happening over on the Ardupilot forum, the code is tied in with the green Pixhawk 2.1 Cube that Philip Rowse is selling as the code will be using the heated IMUs which aren't present in the stock Solo. If the motor code has been changed as is likely for Sitescan the risk is high. I may...

This is one of the discussions here: Facebook

It's been discussed a number of times on the Solo Facebook page, Philip Rowse has discussed this matter, the Solo ESCs could fail causing a brown out, so there was a fix put into Arducopter Solo to hard code less thrust before Solo was launched. Vu has confirmed the SiteScan Solo has improved...

You shouldn't be flashing the Sitescan firmware onto a normal Solo, the Sitescan version uses different ESCs, there's a hard coded power limit in the normal Solo Arducopter so you risk removing that and only bad things will happen if that safeguard goes. Wait for the official Arducopter Master...

No doubt Philip's speed was almost certainly with the wind and he did say you'd lose attitude. The top speed of Solo is software enforced that's part of the reason Arducopter Master can't be put straight onto Solo. With upgraded ESCs it can exceed that. I think we need money on it, if you're...

It has an M8N GPS, likely similar or the same as the one Jordi is selling.