Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

Autopilot + COM freq. over BT to RS232


Author
Message
zooyork
z
Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)
Group: Forum Members
Posts: 4, Visits: 5
Tim Dawson - 3/23/2026 10:32:12 AM
The AT-1 has BLE built in, you shouldn't need any wired connection or any intermediate RS232 device.

If you do choose to use such a device, you'll need to match the baud rate and ensure that the AT-1 is configured to output NMEA data including GPS and traffic on that specific port.

Hello Tim,

thank you for responding. According to Air Avionics Support the AT-1 has built in BLE if the hardware part# is something like AT1-7xxx with a 7 as first digit. Unfortunateley my AT-1 is quite old and has the hardware without BLE capability. Therefore I need to stick with this approach.

In the AT1 RS232 Port 2 settings I posted, RS-232 data port 2 Protocol is set to NMEA:
TITLE: RS-232 data port 2 Protocol
# DESC: Selects the data protocol for this data interface.
# VALUES: NMEA, GARMINTIS, GDL90, ABSTXT
# DEFAULT: NMEA
PROTOCOL2=NMEA


Traffic is enabled:
# TITLE: RS-232 data port 2 Flarm Traffic
# DESC: Activates or deactivates the output of Flarm traffic for this data
# DESC: interface.
# VALUES: ON, OFF
# DEFAULT: ON
FLARMTRAFFIC2=ON

# TITLE: RS-232 data port 2 ADS-B Traffic
# DESC: Activates or deactivates the output of ADS-B traffic for this data
# DESC: interface.
# VALUES: ON, OFF
# DEFAULT: ON
ADSBTRAFFIC2=ON


GPS is enabled
# TITLE: RS-232 data port 2 GPRMC
# DESC: Activates the output of the $GPRMC dataset. GPRMC is a GPS dataset.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAGPRMC2=ON

# TITLE: RS-232 data port 2 GPGGA
# DESC: Activates the output of the $GPGGA dataset. GPGGA is a GPS dataset.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAGPGGA2=ON

# TITLE: RS-232 data port 2 GPGSA
# DESC: Activates the output of the $GPGSA dataset. GPGSA is a GPS dataset.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAGPGSA2=ON


Baudrate
# TITLE: RS-232 data port 2 RS-232 Data Rate
# DESC: Selects the RS-232 data rate (baud rate) for the RS-232 data port 2.
# VALUES: 4800, 9600, 19200, 28800, 38400, 57600, 115200
# DEFAULT: 19200
BAUD2=9600


You said, I need to match the baudrate. Stupid Question... what is the matching baudrate? I'm pretty sure I went through all of the baudrate options on the AT-1, without succes. But I'll verify that again.

Do I miss anything in the settings here or set something wrong?

Tim Dawson
Tim Dawson
SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)
Group: Forum Members
Posts: 8.3K, Visits: 9.9K
The AT-1 has BLE built in, you shouldn't need any wired connection or any intermediate RS232 device.

If you do choose to use such a device, you'll need to match the baud rate and ensure that the AT-1 is configured to output NMEA data including GPS and traffic on that specific port.

zooyork
z
Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)Junior Member (23 reputation)
Group: Forum Members
Posts: 4, Visits: 5
Hello,

did anyone have successfully established a bluetooth connection for NMEA (FLARM or GPS) - Receive GPS position and traffic information to an Air Avionics Air Traffic AT1? 
When I press flying and select "Use AirTrafficAT1" 
It's connecting to the bluetooth device
and then
forever.

My setup is:
Using AT1 RS232 Port 2 transmit data (TXD2) to MAX3232 RS232 RX_IN and MAX3232 TTL RX_OUT to RX DSD TECH HM-18

AT1 RS232 Port 2 settings:
# RS-232 data port 2

# TITLE: RS-232 data port 2 Flarm Traffic
# DESC: Activates or deactivates the output of Flarm traffic for this data
# DESC: interface.
# VALUES: ON, OFF
# DEFAULT: ON
FLARMTRAFFIC2=ON

# TITLE: RS-232 data port 2 ADS-B Traffic
# DESC: Activates or deactivates the output of ADS-B traffic for this data
# DESC: interface.
# VALUES: ON, OFF
# DEFAULT: ON
ADSBTRAFFIC2=ON

# TITLE: RS-232 data port 2 Range [m]
# DESC: Horizontal range limit. Targets outside of this range are not transmitted
# DESC: over this data output.
# VALUES: integer value, 0 - 1000000
# DEFAULT: 25000
RANGE2=25000

# TITLE: RS-232 data port 2 Vertical Range [m]
# DESC: Vertical range limit. Targets outside of this vertical range (differential
# DESC: altitude) are not transmitted over this data output.
# VALUES: integer value, 0 - 1000000
# DEFAULT: 1000
VRANGE2=1000

# TITLE: RS-232 data port 2 Non-Bearing Range [m]
# DESC: Horizontal range limit. Non-bearing targets outside of this range are not
# DESC: transmitted over this data output.
# VALUES: integer value, 0 - 1000000
# DEFAULT: 3000
MODESRANGE2=3000

# TITLE: RS-232 data port 2 Non-Bearing Vertical Range [m]
# DESC: Vertical range limit. Non-bearing targets outside of this range are not
# DESC: transmitted over this data output.
# VALUES: integer value, 0 - 1000000
# DEFAULT: 500
MODESVRANGE2=500

# TITLE: RS-232 data port 2 Protocol
# DESC: Selects the data protocol for this data interface.
# VALUES: NMEA, GARMINTIS, GDL90, ABSTXT
# DEFAULT: NMEA
PROTOCOL2=NMEA

# TITLE: RS-232 data port 2 RS-232 Data Rate
# DESC: Selects the RS-232 data rate (baud rate) for the RS-232 data port 2.
# VALUES: 4800, 9600, 19200, 28800, 38400, 57600, 115200
# DEFAULT: 19200
BAUD2=9600

# TITLE: RS-232 data port 2 GPRMC
# DESC: Activates the output of the $GPRMC dataset. GPRMC is a GPS dataset.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAGPRMC2=ON

# TITLE: RS-232 data port 2 GPGGA
# DESC: Activates the output of the $GPGGA dataset. GPGGA is a GPS dataset.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAGPGGA2=ON

# TITLE: RS-232 data port 2 GPGSA
# DESC: Activates the output of the $GPGSA dataset. GPGSA is a GPS dataset.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAGPGSA2=ON

# TITLE: RS-232 data port 2 PGRMZ
# DESC: Activates the output of the $PGRMZ dataset. PGRMZ is a dataset for
# DESC: pressure altitude.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPGRMZ2=ON

# TITLE: RS-232 data port 2 PFLAU
# DESC: Activates the output of the $PFLAU dataset. PFLAU is a warning dataset in
# DESC: the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAU2=ON

# TITLE: RS-232 data port 2 PFLAA
# DESC: Activates the output of the $PFLAA dataset. PFLAA is a traffic information
# DESC: dataset in the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAA2=ON

# TITLE: RS-232 data port 2 PFLAO
# DESC: Activates the output of the $PFLAO dataset. PFLAO is an alert zone info
# DESC: dataset in the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAO2=ON

# TITLE: RS-232 data port 2 PFLAQ
# DESC: Activates the output of the $PFLAQ dataset. PFLAQ is a progress
# DESC: information dataset in the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAQ2=ON

# TITLE: RS-232 data port 2 PFLAE
# DESC: Activates the output of the $PFLAE dataset. PFLAE is a failure/error
# DESC: annunciation dataset in the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAE2=ON

# TITLE: RS-232 data port 2 PFLAN
# DESC: Activates the output of the $PFLAN dataset. PFLAN is a CARP range analyzer
# DESC: dataset in the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: OFF
NMEAPFLAN2=ON

# TITLE: RS-232 data port 2 PFLAM
# DESC: Activates the output of the $PFLAM dataset. PFLAM is a messaging dataset
# DESC: in the FLARM data protocol.
# VALUES: ON, OFF
# DEFAULT: OFF
NMEAPFLAM2=ON

# TITLE: RS-232 data port 2 PAAVQ
# DESC: Activates the output of the $PAAVQ dataset. PAAVQ is a progress
# DESC: information dataset in the AAV data protocol.
# VALUES: ON, OFF
# DEFAULT: OFF
NMEAPAAVQ2=OFF

# TITLE: RS-232 data port 2 PAAVE
# DESC: Activates the output of the $PAAVE dataset. PAAVE is an error dataset in
# DESC: the AAV data protocol.
# VALUES: ON, OFF
# DEFAULT: OFF
NMEAPAAVE2=OFF

# TITLE: RS-232 data port 2 PAAVS
# DESC: Activates the output of the $PAAVS dataset. PAAVS is an status dataset in
# DESC: the AAV data protocol.
# VALUES: ON, OFF
# DEFAULT: OFF
NMEAPAAVS2=OFF

# TITLE: RS-232 data port 2 GDL90
# DESC: Activates the output of the $GDL90 dataset. This is an NMEA dataset
# DESC: encapsulating the GDL90 data protocol.
# VALUES: ON, OFF
# DEFAULT: OFF
NMEAGDL902=OFF

# TITLE: RS-232 data port 2 PFLAU ID
# DESC: Appends an identification data field to warning datasets in the FLARM data
# DESC: protocol.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAUID2=ON

# TITLE: RS-232 data port 2 PFLAU Non-Bearing Targets
# DESC: Selects how traffic warnings from non-bearing targets are transmitted over
# DESC: the data interface. 'Empty Bearing Field' is recommended. Only set to
# DESC: 'Rotate Bearing' if the connected traffic display on this interface does
# DESC: not support datasets with empty bearing data fields.
# VALUES: OFF, EMPTYBRG, ROTATE
# DEFAULT: OFF
NMEAPFLAUNONDIR2=OFF

# TITLE: RS-232 data port 2 PFLAU Alert Zones
# DESC: Activates warnings from FLARM alert zones.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAUZONES2=ON

# TITLE: RS-232 data port 2 PFLAU Advisory Alerts
# DESC: Activates FLARM Advisory Alerts. Advisory Alerts (also referred to as
# DESC: 'Info Alerts') are short traffic warning messages indicating that a target
# DESC: has been received for the first time within the vicinity of the own
# DESC: aircraft.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAUADVISORY2=ON

# TITLE: RS-232 data port 2 PFLAA Non-Bearing Targets
# DESC: Activates data output of 'non-bearing targets' in PFLAA datasets. This is
# DESC: recommended if the connected traffic display on this interface does
# DESC: explicitly support such datasets.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAAMODES2=ON

# TITLE: RS-232 data port 2 PFLAA No-Track Flag Output
# DESC: Activates the data output of the FLARM no-track status flag in all PFLAA
# DESC: datasets.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAANOTRACK2=ON

# TITLE: RS-232 data port 2 PFLAE Error Messages
# DESC: Activates the output of error messages within the $PFLAE dataset. In
# DESC: addition to the error itself, an error message is transmitted over the
# DESC: data port.
# VALUES: ON, OFF
# DEFAULT: ON
NMEAPFLAEMSG2=ON

# TITLE: RS-232 data port 2 GDL90 Send Own MSL Altitude
# DESC: The GDL90 protocol description specifies an output of the ownship GPS
# DESC: altitude, relative to the WGS-84 ellipsoid. The output can be changed to
# DESC: be relative to MSL, by activating this setting.
# VALUES: ON, OFF
# DEFAULT: OFF
GDL90SENDMSLALT2=OFF


Maybe I'm doing something completely wrong. Thankful for any hint to get it working.

Regards

Rob

vikino
v
Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)
Group: Forum Members
Posts: 39, Visits: 89
vikino - 3/5/2026 6:24:19 PM
Tim Dawson - 3/3/2026 11:11:36 AM
I've no idea. But I don't think there was any change in SkyDemon to the BLE stuff in 4.2.3, and plenty of people are using SkyDemon's BLE stuff in 4.2.3 on Android.

Made some more tests today and problem is only on Samsung devices with Android 16
Today tested with Samsung S26 Ultra and same problem, seeking for satellites...


vikino
v
Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)
Group: Forum Members
Posts: 39, Visits: 89
Tim Dawson - 3/3/2026 11:11:36 AM
I've no idea. But I don't think there was any change in SkyDemon to the BLE stuff in 4.2.3, and plenty of people are using SkyDemon's BLE stuff in 4.2.3 on Android.

Made some more tests today and problem is only on Samsung devices with Android 16

Mikael Markow
M
Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)Junior Member (10 reputation)
Group: Forum Members
Posts: 10, Visits: 0
vikino - 3/4/2026 4:57:10 PM
Tim Dawson - 3/3/2026 11:11:36 AM
I've no idea. But I don't think there was any change in SkyDemon to the BLE stuff in 4.2.3, and plenty of people are using SkyDemon's BLE stuff in 4.2.3 on Android.

Strange...because ive tryied Android 4.2.3 also 4.2.4 beta on multiple Android devices and all still Seeking for satellites...


For me TRX-1500 works with SkyDemon 4.2.4 with Android13 and Android 16. Tested with this Bluetooth device: https://www.utronix.se/Aviation/

vikino
v
Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)
Group: Forum Members
Posts: 39, Visits: 89
Tim Dawson - 3/3/2026 11:11:36 AM
I've no idea. But I don't think there was any change in SkyDemon to the BLE stuff in 4.2.3, and plenty of people are using SkyDemon's BLE stuff in 4.2.3 on Android.

Strange...because ive tryied Android 4.2.3 also 4.2.4 beta on multiple Android devices and all still Seeking for satellites...
Tim Dawson
Tim Dawson
SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)SkyDemon Team (698K reputation)
Group: Forum Members
Posts: 8.3K, Visits: 9.9K
I've no idea. But I don't think there was any change in SkyDemon to the BLE stuff in 4.2.3, and plenty of people are using SkyDemon's BLE stuff in 4.2.3 on Android.
vikino
v
Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)Too Much Forum (551 reputation)
Group: Forum Members
Posts: 39, Visits: 89
Tim Dawson - 3/2/2026 9:55:39 AM
I don't think there is any such general bug. If SkyDemon 4.2.3 was not able to get location from BLE devices, there would be hundreds of people getting in touch about it. What have customer support said?

That there is wrong baudspeed set or some wiring problem, but its not. Why would it work on 4.2.1, iPhone 4.2.3 and not Android 4.2.3?

Bouwair
Bouwair
Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)Too Much Forum (4.1K reputation)
Group: Forum Members
Posts: 40, Visits: 2.9K
Hallo SD team,
Is there any change we can use the Vnav on the autopilot. 
Up till now we only get the information for nav not the Vnav sentences.
With kind regards
Freerk Bouwer 

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search