Modems - Revision history

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-21T06:53:55Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 00:53, 21 January 2021
Line 742:		Line 742:
	The UART0 pins have been swapped because on my Wemos D1 mini the on board serial to USB chip uses the default UARTO pins, Serial Tx is now assigned to GPIO15 and Rx is assigned to GPIO13 on your ESP8266 board, on my Wemos D1 mini pin D7 (GPIO13) is the Rx and D8 (GPIO15) is the Tx.		The UART0 pins have been swapped because on my Wemos D1 mini the on board serial to USB chip uses the default UARTO pins, Serial Tx is now assigned to GPIO15 and Rx is assigned to GPIO13 on your ESP8266 board, on my Wemos D1 mini pin D7 (GPIO13) is the Rx and D8 (GPIO15) is the Tx.

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry ~~connection~~ speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be also the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.
	The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry		The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry.
	OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.		OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.
	You must set the modem's baud rate in the airframe file at 57600 bps ALSO but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.		You must set the modem's baud rate in the airframe file at 57600 bps ALSO but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-21T06:52:15Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 00:52, 21 January 2021
Line 743:		Line 743:

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry connection speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry connection speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.

	The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry		The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry
	OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.		OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-21T06:51:47Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 00:51, 21 January 2021
Line 743:		Line 743:

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry connection speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry connection speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.

	The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry		The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry
	OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.		OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-21T06:50:55Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 00:50, 21 January 2021
Line 742:		Line 742:
	The UART0 pins have been swapped because on my Wemos D1 mini the on board serial to USB chip uses the default UARTO pins, Serial Tx is now assigned to GPIO15 and Rx is assigned to GPIO13 on your ESP8266 board, on my Wemos D1 mini pin D7 (GPIO13) is the Rx and D8 (GPIO15) is the Tx.		The UART0 pins have been swapped because on my Wemos D1 mini the on board serial to USB chip uses the default UARTO pins, Serial Tx is now assigned to GPIO15 and Rx is assigned to GPIO13 on your ESP8266 board, on my Wemos D1 mini pin D7 (GPIO13) is the Rx and D8 (GPIO15) is the Tx.

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry connection speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.
			The reason is simple, inside this 57600 bps bandwidth two things must be accommodated, one is the standard rc servo channel data and the other is the paparazzi telemetry
	OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.		OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.
	You must set the modem's baud rate in the airframe file at 57600 bps ALSO but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.		You must set the modem's baud rate in the airframe file at 57600 bps ALSO but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-21T06:41:26Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 00:41, 21 January 2021
Line 743:		Line 743:

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.
	OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver ~~to autopilot~~ uart speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.		OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver's uart and tx module uart connection speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.
	You ~~still need to~~ set the modem baud rate in the ~~aircraft~~ file at 57600 bps but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.		You must set the modem's baud rate in the airframe file at 57600 bps ALSO but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.

	VERY IMPORTANT:		VERY IMPORTANT:

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-15T09:53:43Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 03:53, 15 January 2021
Line 731:		Line 731:
	that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2		that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2

	It could be a joke but i didn't saw the EXCELLENT project of Christophe De Wagter (CDW) and i spent 2 whole days and one night reading about Arduino coding style and ESP8266 libraries only to write a very simple version of his code.....		It could be a joke but i didn't saw the EXCELLENT project of Christophe De Wagter (CDW) (i only saw it when i came here to edit this page...) and i spent 2 whole days and one night reading about Arduino coding style and ESP8266 libraries only to write a very simple version of his code...

	Now upload whichever program you decided to use to your ESP8266 board, both are in AP mode but have different SSID and password, make sure that you have selected the right ESP8266 board as a target, i use the Wemos D1 mini because that was what came in first after i ordered a bunch of those ESP8266 modules.		Now upload whichever program you decided to use to your ESP8266 board, both are in AP mode but have different SSID and password, make sure that you have selected the right ESP8266 board as a target, i use the Wemos D1 mini because that was what came in first after i ordered a bunch of those ESP8266 modules.

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-15T09:52:24Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 03:52, 15 January 2021
Line 730:		Line 730:
	HAVE IN MIND THAT THE CODE IN THE PREVIOUS PROJECT WITH ESP8266 NAMED "ESP8266 Chip Module" (https://github.com/paparazzi/esp8266_udp_firmware) IS FAR BETTER AND IT WORKS VERY VERY WELL WITHOUT ANY DELAY, mine is a simple program just to understand what is going on basically so use the "esp8266_udp_firmware" but remember to edit the wifi_config.h to suit your needs and also the LED pin inside "pprz_udp_link" line #14		HAVE IN MIND THAT THE CODE IN THE PREVIOUS PROJECT WITH ESP8266 NAMED "ESP8266 Chip Module" (https://github.com/paparazzi/esp8266_udp_firmware) IS FAR BETTER AND IT WORKS VERY VERY WELL WITHOUT ANY DELAY, mine is a simple program just to understand what is going on basically so use the "esp8266_udp_firmware" but remember to edit the wifi_config.h to suit your needs and also the LED pin inside "pprz_udp_link" line #14
	that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2		that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2

	It could be a joke but i didn't saw the EXCELLENT project of Christophe De Wagter (CDW) and i spent 2 whole days and one night reading about Arduino coding style and ESP8266 libraries only to write a very simple version of his code.....		It could be a joke but i didn't saw the EXCELLENT project of Christophe De Wagter (CDW) and i spent 2 whole days and one night reading about Arduino coding style and ESP8266 libraries only to write a very simple version of his code.....

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-15T09:51:49Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 03:51, 15 January 2021
Line 730:		Line 730:
	HAVE IN MIND THAT THE CODE IN THE PREVIOUS PROJECT WITH ESP8266 NAMED "ESP8266 Chip Module" (https://github.com/paparazzi/esp8266_udp_firmware) IS FAR BETTER AND IT WORKS VERY VERY WELL WITHOUT ANY DELAY, mine is a simple program just to understand what is going on basically so use the "esp8266_udp_firmware" but remember to edit the wifi_config.h to suit your needs and also the LED pin inside "pprz_udp_link" line #14		HAVE IN MIND THAT THE CODE IN THE PREVIOUS PROJECT WITH ESP8266 NAMED "ESP8266 Chip Module" (https://github.com/paparazzi/esp8266_udp_firmware) IS FAR BETTER AND IT WORKS VERY VERY WELL WITHOUT ANY DELAY, mine is a simple program just to understand what is going on basically so use the "esp8266_udp_firmware" but remember to edit the wifi_config.h to suit your needs and also the LED pin inside "pprz_udp_link" line #14
	that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2		that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2
			It could be a joke but i didn't saw the EXCELLENT project of Christophe De Wagter (CDW) and i spent 2 whole days and one night reading about Arduino coding style and ESP8266 libraries only to write a very simple version of his code.....

	Now upload whichever program you decided to use to your ESP8266 board, both are in AP mode but have different SSID and password, make sure that you have selected the right ESP8266 board as a target, i use the Wemos D1 mini because that was what came in first after i ordered a bunch of those ESP8266 modules.		Now upload whichever program you decided to use to your ESP8266 board, both are in AP mode but have different SSID and password, make sure that you have selected the right ESP8266 board as a target, i use the Wemos D1 mini because that was what came in first after i ordered a bunch of those ESP8266 modules.
Line 740:		Line 741:
	The UART0 pins have been swapped because on my Wemos D1 mini the on board serial to USB chip uses the default UARTO pins, Serial Tx is now assigned to GPIO15 and Rx is assigned to GPIO13 on your ESP8266 board, on my Wemos D1 mini pin D7 (GPIO13) is the Rx and D8 (GPIO15) is the Tx.		The UART0 pins have been swapped because on my Wemos D1 mini the on board serial to USB chip uses the default UARTO pins, Serial Tx is now assigned to GPIO15 and Rx is assigned to GPIO13 on your ESP8266 board, on my Wemos D1 mini pin D7 (GPIO13) is the Rx and D8 (GPIO15) is the Tx.

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be about 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.
			OPENLRSng has 2 baud rate settings in its dedicated Chrome app, The serial link baud rate and the air data rate, set the first to 57600 and the second to 57600 which means that you will get a serial link connection speed of 57600 bps (rc receiver to autopilot uart speed) and an air data rate (rc receiver to radio Tx module) of 57600 bps which can pass a transparent serial link of 19200 bps along the rc link.
	You still need to set the modem baud rate in the aircraft file at 57600 bps but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.		You still need to set the modem baud rate in the aircraft file at 57600 bps but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.
	~~With OPENLRSng air data speed set at 57600 bps there is enough bandwidth to transmit both the rc link and the 19200 bps telemetry data.~~
	~~If you have any problem with the code let me know, use the mailing list or contact me directly.~~

	VERY IMPORTANT:		VERY IMPORTANT:

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-15T09:33:42Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 03:33, 15 January 2021
Line 741:		Line 741:

	Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.		Important: The ESP8266's default serial port speed is 57600 bps and this will be the telemetry speed but if you plan to duplicate my method of telemetry using OPENLRSng as the telemetry transport method please remember that 57600 bps is only the speed of the TX module to ESP8266 module connection and not the actual telemetry data rate which will be 19200 bps maximum if you select the air to air data speed of the RC receiver and rc radio TX module to be 57600 bps.
	You still need to set the ~~GCS session~~ at 57600 bps but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.		You still need to set the modem baud rate in the aircraft file at 57600 bps but the actual telemetry rate will be about 19200 bps and that's why you need to adjust your messages that come through telemetry to fit in that 19200 bps rate.
	With OPENLRSng air data speed set at 57600 bps there is enough bandwidth to transmit both the rc link and the 19200 bps telemetry data.		With OPENLRSng air data speed set at 57600 bps there is enough bandwidth to transmit both the rc link and the 19200 bps telemetry data.
	If you have any problem with the code let me know, use the mailing list or contact me directly.		If you have any problem with the code let me know, use the mailing list or contact me directly.

Hendrix: /* Yet another ESP8266 datalink modem */

2021-01-15T09:26:09Z

Yet another ESP8266 datalink modem

← Older revision		Revision as of 03:26, 15 January 2021
Line 729:		Line 729:

	HAVE IN MIND THAT THE CODE IN THE PREVIOUS PROJECT WITH ESP8266 NAMED "ESP8266 Chip Module" (https://github.com/paparazzi/esp8266_udp_firmware) IS FAR BETTER AND IT WORKS VERY VERY WELL WITHOUT ANY DELAY, mine is a simple program just to understand what is going on basically so use the "esp8266_udp_firmware" but remember to edit the wifi_config.h to suit your needs and also the LED pin inside "pprz_udp_link" line #14		HAVE IN MIND THAT THE CODE IN THE PREVIOUS PROJECT WITH ESP8266 NAMED "ESP8266 Chip Module" (https://github.com/paparazzi/esp8266_udp_firmware) IS FAR BETTER AND IT WORKS VERY VERY WELL WITHOUT ANY DELAY, mine is a simple program just to understand what is going on basically so use the "esp8266_udp_firmware" but remember to edit the wifi_config.h to suit your needs and also the LED pin inside "pprz_udp_link" line #14
	that reads #define LED_PIN ~~2 //~~ Wemos D1 mini ~~on the board i use.~~		that reads #define LED_PIN 13, for the Wemos D1 mini this line should read #define LED_PIN 2

	Now upload whichever program you decided to use to your ESP8266 board, both are in AP mode but have different SSID and password, make sure that you have selected the right ESP8266 board as a target, i use the Wemos D1 mini because that was what came in first after i ordered a bunch of those ESP8266 modules.		Now upload whichever program you decided to use to your ESP8266 board, both are in AP mode but have different SSID and password, make sure that you have selected the right ESP8266 board as a target, i use the Wemos D1 mini because that was what came in first after i ordered a bunch of those ESP8266 modules.