[Bill B]

I did some work on Landscape (look at Find My Drone which has landscape mode) but I really need to fix the dashboard, and it’s a lot of work)

[Bill B]

UDP is better, but when creating a bridge TCP works ok, since packet loss is minimal. The the real problem with TCP is with high packet loss can destroy the TCP link due to the number of retries with resultant connection loss, then required reconnection. UDP just drops the missed packets making it more reliable (no connection loss, the app will retry commands at the app level, not at the network level)

[Bill B]

I’ll try and put this in the next update. I do have some features ready to go.. send me your email to bill communistech com and I can add you to the beta list

[Bill B]

Yep.. Find My Drone has that feature in the Map View, its easy to enable it. Its just the default behaviour is not to monitor the user location. Easily changed and a good idea.

Thanks for the suggestion.

[Bill B]

see here https://www.communistech.com/blog/question/how-to-connect-to-3dr-solo/

In the new version to be released soon, it has shortcuts to set setting for SOLO, PIXRACER etc… and they are user definable as well.

Thx

[Bill B]

This one http://ardupilot.org/copter/docs/common-pixracer-overview.html

I don’t have any specific setup instructions other than what is required to enable it here https://pixhawk.org/peripherals/8266

I do have a pixracer here. I pull it out and test that it works and what needs to be done.

[Bill B]

I’ve done some work to get BLE working. A few more days and it should work. But only with the BLE Mini from Red Bear at first. I’ll add other BLE device as I find out there defining ‘characteristics’

[Bill B]

Hi, MAVPilot will work with AC3.4 there is a compatibility option in the Settings for the Severity messages, but everything else will work as before.

MAVLink2 support is a future enhancement not yet implemented if that’s what you mean? but ArduPilot supports both 1.1 and 2.0 at the moment.

[Bill B]

Only issue has been time, send me a email address and I will add you to the beta release.

[Bill B]

iOS only supports Made For iDevices approved products connected to the Lighting Port. I don’t see such a product. This leaves only Bluetooth Low Energy or WiFi as the convenient methods for connecting.

WiFi as a local link to a long range radio bridge works very effectively.

Hope that helps 🙂

[Bill B]

MAV Pilot does have Bluetooth Low Energy support in the code (it’s not in the released version) I did have some discussions about reintroducing the functionality with TBS, but discussions stalled. (other commitments got in the way) I’m not sure BLE support in the CrossFire is fully working as a MAVLink end point.

The android apps use Bluetooth 2.0 (i.e. Classic) so that is a different connection endpoint to Bluetooth 4.0 Low Energy.

I’ll send a message to my contact and see what the status is.

• This reply was modified 8 years, 6 months ago by Bill B.

[Bill B]

Thanks for update.
Adding tlogs is a feature i want to add. Hopefully I get some spare cycles to add it soon.

[Bill B]

I haven’t used or setup the WiFly as UDP for such a long time. I will need to look into that.

For the MAP Data when using TCP, the only solution is to disconnect WiFi and browse the map, and it will cache that area. then reconnect to the vehicle. When connect with UDP the phone will use the LTE connection to download the data. This is one reason UDP is preferred connection mechanism (That said I have always used the WiFly in TCP mode Soft AP mode)

• This reply was modified 8 years, 8 months ago by Bill B.

[Bill B]

I would suggest trying the loopback connection to see if it works without an autopilot involved.

My guess is that the problem you have is the signal from the 3DR Radio are 3v3 compatible. This means the should work to trigger 5V TTL signals that the level convertor needs, but not always. I have had the same issue with the SparkFun Xbee adapter as well. The solution is to bypass the level convertor in the adapter board as the 3DR Radio and the XBee are 3v3 compliant devices.

If you cannot get it fixed by bypassing, I’ll send you ESP8266 with the MAVESP8266 FW on it.

[Bill B]

Hard to say why it is not working. My suggestion would be to connect it directly to the autopilot first and get a connection, then when that works, move to making he bridge to 915MHz. The other option is to connect a FDTI cabel and terminal to the serial port, and then connect using a computer and then telnet to the ip address and port. You should be able to send characters back and forth between the terminal connected to the serial port (via FTDI) and telnet.

To connect via FTDI
screen /dev/cu.cu.usbserial-A1024NRG 57600

To connect via Telnet
telnet 192.168.1.1 2000

If you are still stuck, maybe we can do a quick text chat on gitter or Skype.

• This reply was modified 8 years, 9 months ago by Bill B.

[Author]

Posts