Mode-S Beast:Firmware Updates - Revision history

Nunojpg at 21:24, 20 October 2020

2020-10-20T21:24:46Z

imported>Dl4mea: /* FW 1.32a Correction Release */

2015-11-13T19:45:24Z

FW 1.32a Correction Release

← Older revision		Revision as of 19:45, 13 November 2015
Line 194:		Line 194:

	(Please also those who have got the USB updater in advance, download it again)<br>Testing of the serial configuration feature can easiest be done by switching off and on Mode-A/C decoding with the letters "j" and "J" in the config string and observing it with Planeplotter's speed meter.		(Please also those who have got the USB updater in advance, download it again)<br>Testing of the serial configuration feature can easiest be done by switching off and on Mode-A/C decoding with the letters "j" and "J" in the config string and observing it with Planeplotter's speed meter.


	===Revision 1.40 - 07.03.2012===		===Revision 1.40 - 07.03.2012===

imported>Dl4mea: /* Revision 1.43 - 13.11.2015 */

2015-11-13T19:44:40Z

Revision 1.43 - 13.11.2015

← Older revision		Revision as of 19:44, 13 November 2015
Line 255:		Line 255:
	{\| class="wikitable"		{\| class="wikitable"
	\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):		\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):
	\|[http://www.modesbeast.com/resources/~~meaADSB-v143~~-1ch-blaster.zip 1 CH Firmware V1.43]		\|[http://www.modesbeast.com/resources/meaADSB_v143-1ch-blaster.zip 1 CH Firmware V1.43]
	\|[http://www.modesbeast.com/resources/~~meaADSB-v143~~-2ch-blaster.zip 2 CH Firmware V1.43]		\|[http://www.modesbeast.com/resources/meaADSB_v143-2ch-blaster.zip 2 CH Firmware V1.43]
	\|-		\|-
	\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):		\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):
	\|[http://www.modesbeast.com/resources/~~meaADSB-v143~~-1ch-usbupdate.zip 1 CH Firmware V1.43]		\|[http://www.modesbeast.com/resources/meaADSB_v143-1ch-usbupdate.zip 1 CH Firmware V1.43]
	\|[http://www.modesbeast.com/resources/~~meaADSB-v143~~-2ch-usbupdate.zip 2 CH Firmware V1.43]		\|[http://www.modesbeast.com/resources/meaADSB_v143-2ch-usbupdate.zip 2 CH Firmware V1.43]
	\|}		\|}

	Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 or later (sold after September 2011) can enjoy updating over USB.		Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 or later (sold after September 2011) can enjoy updating over USB.

imported>Dl4mea: /* Revision 1.43 - 13.11.2015 */

2015-11-13T19:42:49Z

Revision 1.43 - 13.11.2015

← Older revision		Revision as of 19:42, 13 November 2015
Line 242:		Line 242:
	===Revision 1.43 - 13.11.2015===		===Revision 1.43 - 13.11.2015===

	~~This version introduces a totally new design of the frame synchronisation, which now uses all available information from the preamble without any compromises. It was tested over several weeks by~~ some ~~beta testers with great success, who all saw a further <ins>increase of frame rate by about 10%</ins> and also <ins>some increase in range</ins>. When testing by myself, I now can see up to '''1500~~ Mode-S ~~frames per second''' in the evening hours with only the omni antenna~~ and ~~I am getting a stable 225nm range displayed. The sensitivity increase not at least allows me seeing the ground traffic at Munich airport~~, ~~which did not appear in the versions before~~ and ~~whatfor I needed the yagi antenna. Also, I found a way how to better filter false non~~-~~CRC checkable frames, which are drastically reduced and keep load away from the interface and post processing SW. My number is that around 75%~~ of ~~the frames now are good frames~~.		Following some confusion around Mode-S Beast firmware, about betas and whatever became published, this version is released for clarification and re-synchronisation of Beast users to a common released version.

	While testing, I found a nice performance value: When the channel is not heavily loaded, below about 60 aircraft beeing tracked, the number of frames per second is 10 times the number of aircraft. Or, in other words, each aircraft transmits 10 frames per second. ~~This may be different in other parts of the world, as for example we've learned just recently that in some areas DF-20~~ and ~~DF-21 are not in use.~~		<ins>FW V1.43 adds following new features and corrections:</ins>

	~~<ins>FW V1.40 adds following new features and corrections:</ins>~~		* A possible FPGA coding fault was fixed (It never caused problems, but clean design requires such)
			* FPGA output drivers were programmed for slower edges, which lowers the internally generated noise floor of the board
	* ~~New~~ design of the frame synchronisation: Leads to a better detection of frames while having local reflections, and also a better detection of weak and noisy frames. Not at least the timestamp by this has an accuracy of 1 sample clock or 62ns.
	* ~~Removal of double~~ output ~~DF-17 frames while having forward error correction (FEC) enabled.~~
	* FEC of .DF-11 frames is working again.
	* Improved signal level measurement: Signal level now is measured using all 128 ADC samples that are part of the preamble. It is the normalized level difference between all samples that should be zero and those which ~~should be one. The value range has not changed, just~~ the ~~accuracy is better.~~
	* Drastic decrease of ~~corrupt frames that cannot be checked by a CRC.~~

	'''Who needs this update?'''<br>This FW update is recommended to all users.		'''Who needs this update?'''<br>This FW update is recommended to all users.
Line 260:		Line 255:
	{\| class="wikitable"		{\| class="wikitable"
	\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):		\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):
	\|[http://www.modesbeast.com/resources/meaADSB-~~v140~~-1ch-blaster.zip 1 CH Firmware V1.40]		\|[http://www.modesbeast.com/resources/meaADSB-v143-1ch-blaster.zip 1 CH Firmware V1.43]
	\|[http://www.modesbeast.com/resources/meaADSB-~~v140~~-2ch-blaster.zip 2 CH Firmware V1.40]		\|[http://www.modesbeast.com/resources/meaADSB-v143-2ch-blaster.zip 2 CH Firmware V1.43]
	\|-		\|-
	\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):		\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):
	\|[http://www.modesbeast.com/resources/meaADSB-~~v140~~-1ch-usbupdate.zip 1 CH Firmware V1.40]		\|[http://www.modesbeast.com/resources/meaADSB-v143-1ch-usbupdate.zip 1 CH Firmware V1.43]
	\|[http://www.modesbeast.com/resources/meaADSB-~~v140~~-2ch-usbupdate.zip 2 CH Firmware V1.40]		\|[http://www.modesbeast.com/resources/meaADSB-v143-2ch-usbupdate.zip 2 CH Firmware V1.43]
	\|}		\|}

	Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 (sold after September 2011) can enjoy updating over USB.		Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 or later (sold after September 2011) can enjoy updating over USB.

imported>Dl4mea: /* Revision 1.40 - 07.03.2012 */

2015-11-13T19:38:52Z

Revision 1.40 - 07.03.2012

← Older revision		Revision as of 19:38, 13 November 2015
Line 235:		Line 235:

	Remember when updating from versions before V1.32, that the serial interface needs a minor modification done. See [[Mode-S Beast:Firmware Updates\|here]].		Remember when updating from versions before V1.32, that the serial interface needs a minor modification done. See [[Mode-S Beast:Firmware Updates\|here]].

			===Revision 1.41 - Revision 1.42beta===

			These were demo and test releases, never released for public because the effort of updating was not worth the possible minor improvement.

			===Revision 1.43 - 13.11.2015===

			This version introduces a totally new design of the frame synchronisation, which now uses all available information from the preamble without any compromises. It was tested over several weeks by some beta testers with great success, who all saw a further <ins>increase of frame rate by about 10%</ins> and also <ins>some increase in range</ins>. When testing by myself, I now can see up to '''1500 Mode-S frames per second''' in the evening hours with only the omni antenna and I am getting a stable 225nm range displayed. The sensitivity increase not at least allows me seeing the ground traffic at Munich airport, which did not appear in the versions before and whatfor I needed the yagi antenna. Also, I found a way how to better filter false non-CRC checkable frames, which are drastically reduced and keep load away from the interface and post processing SW. My number is that around 75% of the frames now are good frames.

			While testing, I found a nice performance value: When the channel is not heavily loaded, below about 60 aircraft beeing tracked, the number of frames per second is 10 times the number of aircraft. Or, in other words, each aircraft transmits 10 frames per second. This may be different in other parts of the world, as for example we've learned just recently that in some areas DF-20 and DF-21 are not in use.

			<ins>FW V1.40 adds following new features and corrections:</ins>

			* New design of the frame synchronisation: Leads to a better detection of frames while having local reflections, and also a better detection of weak and noisy frames. Not at least the timestamp by this has an accuracy of 1 sample clock or 62ns.
			* Removal of double output DF-17 frames while having forward error correction (FEC) enabled.
			* FEC of .DF-11 frames is working again.
			* Improved signal level measurement: Signal level now is measured using all 128 ADC samples that are part of the preamble. It is the normalized level difference between all samples that should be zero and those which should be one. The value range has not changed, just the accuracy is better.
			* Drastic decrease of corrupt frames that cannot be checked by a CRC.

			'''Who needs this update?'''<br>This FW update is recommended to all users.

			'''Free downloads:'''

			{\| class="wikitable"
			\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):
			\|[http://www.modesbeast.com/resources/meaADSB-v140-1ch-blaster.zip 1 CH Firmware V1.40]
			\|[http://www.modesbeast.com/resources/meaADSB-v140-2ch-blaster.zip 2 CH Firmware V1.40]
			\|-
			\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):
			\|[http://www.modesbeast.com/resources/meaADSB-v140-1ch-usbupdate.zip 1 CH Firmware V1.40]
			\|[http://www.modesbeast.com/resources/meaADSB-v140-2ch-usbupdate.zip 2 CH Firmware V1.40]
			\|}

			Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 (sold after September 2011) can enjoy updating over USB.

imported>Dl4mea: /* Firmware Revision Indication */

2015-11-12T21:45:59Z

Firmware Revision Indication

← Older revision		Revision as of 21:45, 12 November 2015
Line 59:		Line 59:
	\|on		\|on
	\|-		\|-
	\|FW V1.4§		\|FW V1.43
	\|flashing		\|flashing
	\|off		\|off

imported>Dl4mea: /* Firmware Revision Indication */

2015-11-12T21:30:30Z

Firmware Revision Indication

← Older revision		Revision as of 21:30, 12 November 2015
Line 50:		Line 50:
	\|on		\|on
	\|-		\|-
	\|FW V1.43		\|FW V1.41/V1.42
	\|flashing		\|flashing
	\|flashing		\|flashing
	\|off		\|off
	\|off		\|off
			\|off
			\|off
			\|on
			\|-
			\|FW V1.4§
			\|flashing
			\|off
			\|flashing
			\|flashing
	\|off		\|off
	\|off		\|off

imported>Dl4mea: /* Firmware Revision Indication */

2015-11-12T21:26:56Z

Firmware Revision Indication

← Older revision		Revision as of 21:26, 12 November 2015
Line 46:		Line 46:
	\|off		\|off
	\|flashing		\|flashing
			\|off
			\|off
			\|on
			\|-
			\|FW V1.43
			\|flashing
			\|flashing
			\|off
			\|off
	\|off		\|off
	\|off		\|off
Line 52:		Line 61:

	'''Note:''' LED colors of 2CH version are different.		'''Note:''' LED colors of 2CH version are different.


	==Copyright Notice==		==Copyright Notice==

imported>Dl4mea: /* Revision 1.30 - 20.09.2011 */

2013-12-01T15:22:16Z

Revision 1.30 - 20.09.2011

← Older revision		Revision as of 15:22, 1 December 2013
Line 117:		Line 117:
	The <ins>binary protocol</ins> the Mode-S Beasts makes a more efficient usage of the serial interface. It allows transmission of twice as much information on the same baudrate.		The <ins>binary protocol</ins> the Mode-S Beasts makes a more efficient usage of the serial interface. It allows transmission of twice as much information on the same baudrate.

	The binary format is a simple escaped format, ~~like~~		The binary format is a simple escaped format, which only doubles the escape character and else is a fully transparent data stream. There is a good capability to expand it to more frame types later.

	~~TBD~~

	Since especially Xport-Ethernet users gain from this feature, and additionally since Bev implemented the TCP Mode-S Beast support in Planeplotter right in time, the "AV" UDP support was dropped in the expectation that the binary mode is used with preference over Ethernet. As an example, Bev while testing was easily able to connect to my Mode-S Beast from Portugal. More on the [[Mode-S Beast:Lantronix Xport Assembly\|Xport page]]. More about the different output formats on the [[Mode-S Beast:Data Output Formats\|output formats page]].		Since especially Xport-Ethernet users gain from this feature, and additionally since Bev implemented the TCP Mode-S Beast support in Planeplotter right in time, the "AV" UDP support was dropped in the expectation that the binary mode is used with preference over Ethernet. As an example, Bev while testing was easily able to connect to my Mode-S Beast from Portugal. More on the [[Mode-S Beast:Lantronix Xport Assembly\|Xport page]]. More about the different output formats on the [[Mode-S Beast:Data Output Formats\|output formats page]].

	Signal level information is output on the interface for each Mode-S and Mode-AC frame now. This can be used for example to identify the most close flying aircraft. The range is from 0 to about 210. The upper limit is a floating value and depends on the noise level that the antenna sees. Users are recommended to use a long term filter on the maximum when they like to scale the value down or upwards. Due to compatibility reasons, the signal level is available only in the binary output protocol.		Signal level information is output on the interface for each Mode-S and Mode-AC frame now. This can be used for example to identify the most close flying aircraft. The range is from 0 to about 210. The upper limit is a floating value and depends on the noise level that the antenna sees. Users are recommended to use a long term filter on the maximum when they like to scale the value down or upwards. Due to compatibility reasons, the signal level is available only in the binary output protocol.


	===Revision 1.31 - 07.10.2011===		===Revision 1.31 - 07.10.2011===

imported>Beastadmin at 15:08, 1 December 2013

2013-12-01T15:08:36Z

← Older revision		Revision as of 15:08, 1 December 2013
Line 102:		Line 102:

	{\|		{\|
	\|[[File:Fpga-shot32-1756frames.gif\|link File:Fpga-shot32-1756frames-big.gif\|Received off-air message rate ]]		\|[[File:Fpga-shot32-1756frames.gif\|link=File:Fpga-shot32-1756frames-big.gif\|Received off-air message rate ]]
	\|''(click on the speedmeter picture to see whole screen)''<br><br>Note that the USB serial bus is again the bottleneck and the implementation gives Mode-S priority over Mode-AC.<br><br>Also remember that prediction is now totally off in my Planeplotter screenshots.		\|''(click on the speedmeter picture to see whole screen)''<br><br>Note that the USB serial bus is again the bottleneck and the implementation gives Mode-S priority over Mode-AC.<br><br>Also remember that prediction is now totally off in my Planeplotter screenshots.
	\|-		\|-
	\|[[File:Fpga-shot32-1934frames.gif\|link File:Fpga-shot32-1934frames-big.gif\|Received off-air message rate ]]		\|[[File:Fpga-shot32-1934frames.gif\|link=File:Fpga-shot32-1934frames-big.gif\|Received off-air message rate ]]
	\|<ins>Update 26.08.2011:</ins><br>''(whole Planplotter screen if you click on the picture)''<br>Friday evening is the traffic maximum: 1934 Mode-S frames and 6180 Mode-AC frames. MLAT was on! Compared to the capture on the left, it seems that Mode-AC is now less because of Mode-S priority.		\|<ins>Update 26.08.2011:</ins><br>''(whole Planplotter screen if you click on the picture)''<br>Friday evening is the traffic maximum: 1934 Mode-S frames and 6180 Mode-AC frames. MLAT was on! Compared to the capture on the left, it seems that Mode-AC is now less because of Mode-S priority.
	\|}		\|}
Line 111:		Line 111:
	My maximum distance on the yagi is 300nm:		My maximum distance on the yagi is 300nm:

	[[File:Pp-shot80-300nm.gif\|link File:Pp-shot80-300nm-big.gif\|Planeplotter screenshot 80-300 NM]]		[[File:Pp-shot80-300nm.gif\|link=File:Pp-shot80-300nm-big.gif\|Planeplotter screenshot 80-300 NM]]

	Look at the left side of the picture: There you see the range rings for 200nm (solid) and 225nm (dashed). The 300nm distance of NVR277 is shown in the bottom line. The picture was taken with prediction off, so notice that there was a sequence of frames received from this plane and another one before. Surely there was some good propagation, but at least those between 200nm and 225nm are regular.		Look at the left side of the picture: There you see the range rings for 200nm (solid) and 225nm (dashed). The 300nm distance of NVR277 is shown in the bottom line. The picture was taken with prediction off, so notice that there was a sequence of frames received from this plane and another one before. Surely there was some good propagation, but at least those between 200nm and 225nm are regular.

← Older revision		Revision as of 21:24, 20 October 2020
Line 150:		Line 150:
	''A word about all the effort to cope with the serial interface bottleneck''' - or why the hell do other receivers not suffer from this? Simply said: Their frame rate (maybe performance) is not as high as that of the Mode-S Beast. And they mostly do not decode Mode-AC with timestamp, which is while on the input just 12 Bits on the output nearly multipes times 5.		''A word about all the effort to cope with the serial interface bottleneck''' - or why the hell do other receivers not suffer from this? Simply said: Their frame rate (maybe performance) is not as high as that of the Mode-S Beast. And they mostly do not decode Mode-AC with timestamp, which is while on the input just 12 Bits on the output nearly multipes times 5.

	'''Downloads:''' [~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB-v131-1ch-SNRimp-blaster.zip 1 CH Firmware V1.31], [~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB-v131-2ch-SNRimp-blaster.zip 2 CH Firmware V1.31]		'''Downloads:''' [https://jetvision.de/resources/meaADSB-v131-1ch-SNRimp-blaster.zip 1 CH Firmware V1.31], [https://jetvision.de/resources/meaADSB-v131-2ch-SNRimp-blaster.zip 2 CH Firmware V1.31]


Line 167:		Line 167:
	{\| class="wikitable"		{\| class="wikitable"
	\|for USB blaster (POF file):		\|for USB blaster (POF file):
	\|[~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB-v132a-1ch-bincorr-blaster.zip 1 CH Firmware V1.32a]		\|[https://jetvision.de/resources/meaADSB-v132a-1ch-bincorr-blaster.zip 1 CH Firmware V1.32a]
	\|[~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB-v132a-2ch-bincorr-blaster.zip 2 CH Firmware V1.32a]		\|[https://jetvision.de/resources/meaADSB-v132a-2ch-bincorr-blaster.zip 2 CH Firmware V1.32a]
	\|-		\|-
	\|for embedded update (RBF file):		\|for embedded update (RBF file):
	\|[~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB-v132a-1ch-bincorr-usbupdate.zip 1 CH Firmware V1.32a]		\|[https://jetvision.de/resources/meaADSB-v132a-1ch-bincorr-usbupdate.zip 1 CH Firmware V1.32a]
	\|[~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB-v132a-2ch-bincorr-usbupdate.zip 2 CH Firmware V1.32a]		\|[https://jetvision.de/resources/meaADSB-v132a-2ch-bincorr-usbupdate.zip 2 CH Firmware V1.32a]
	\|}		\|}

Line 215:		Line 215:
	{\| class="wikitable"		{\| class="wikitable"
	\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):		\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):
	\|[~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB-v140-1ch-blaster.zip 1 CH Firmware V1.40]		\|[https://jetvision.de/resources/meaADSB-v140-1ch-blaster.zip 1 CH Firmware V1.40]
	\|[~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB-v140-2ch-blaster.zip 2 CH Firmware V1.40]		\|[https://jetvision.de/resources/meaADSB-v140-2ch-blaster.zip 2 CH Firmware V1.40]
	\|-		\|-
	\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):		\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):
	\|[~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB-v140-1ch-usbupdate.zip 1 CH Firmware V1.40]		\|[https://jetvision.de/resources/meaADSB-v140-1ch-usbupdate.zip 1 CH Firmware V1.40]
	\|[~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB-v140-2ch-usbupdate.zip 2 CH Firmware V1.40]		\|[https://jetvision.de/resources/meaADSB-v140-2ch-usbupdate.zip 2 CH Firmware V1.40]
	\|}		\|}

Line 254:		Line 254:
	{\| class="wikitable"		{\| class="wikitable"
	\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):		\|[[Mode-S Beast:Update with Blaster\|for USB-Blaster]] (POF file):
	\|[~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB_v143-1ch-blaster.zip 1 CH Firmware V1.43]		\|[https://jetvision.de/resources/meaADSB_v143-1ch-blaster.zip 1 CH Firmware V1.43]
	\|[~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB_v143-2ch-blaster.zip 2 CH Firmware V1.43]		\|[https://jetvision.de/resources/meaADSB_v143-2ch-blaster.zip 2 CH Firmware V1.43]
	\|-		\|-
	\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):		\|[[Mode-S Beast:Update over USB\|for embedded update]] (RBF file):
	\|[~~http~~://~~www~~.~~modesbeast.com~~/resources/meaADSB_v143-1ch-usbupdate.zip 1 CH Firmware V1.43]		\|[https://jetvision.de/resources/meaADSB_v143-1ch-usbupdate.zip 1 CH Firmware V1.43]
	\|[~~http~~://~~www.modesbeast~~.~~com~~/resources/meaADSB_v143-2ch-usbupdate.zip 2 CH Firmware V1.43]		\|[https://jetvision.de/resources/meaADSB_v143-2ch-usbupdate.zip 2 CH Firmware V1.43]
	\|}		\|}

	Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 or later (sold after September 2011) can enjoy updating over USB.		Remember that those which got their HW V1.0 Beast (sold around May 2011) updated to USB update or those who have HW V1.1 or later (sold after September 2011) can enjoy updating over USB.