Radarcape:TrimbleSMT360 FW - Revision history

Nunojpg at 17:26, 8 August 2019

2019-08-08T17:26:15Z

← Older revision		Revision as of 17:26, 8 August 2019
Line 27:		Line 27:
	login to Radarcape shell with ssh, username root + eventually the password you've set		login to Radarcape shell with ssh, username root + eventually the password you've set

	<nowiki>wget https://~~static~~.jetvision.de/tsip-cli-fwup -P /tmp		<nowiki>wget https://www.jetvision.de/resources/tsip-cli-fwup -P /tmp
	chmod +x /tmp/tsip-cli-fwup		chmod +x /tmp/tsip-cli-fwup
	systemctl stop radarcape && /tmp/tsip-cli-fwup /dev/ttyS2 115200 && systemctl start radarcape</nowiki>		systemctl stop radarcape && /tmp/tsip-cli-fwup /dev/ttyS2 115200 && systemctl start radarcape</nowiki>

Dl4mea at 07:28, 1 August 2019

2019-08-01T07:28:53Z

← Older revision		Revision as of 07:28, 1 August 2019
Line 14:		Line 14:
	[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]		[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]

	All devices operating in the area that is not white in above picture may suffer from the problem. The error shows up as not getting any more new satellites after having seen the 2nd QZSS satellite. It lasts until a factory reset of the SMT360 module. Neither reboot nor power cycle ~~solves~~ the ~~problem externally~~.		All devices operating in the area that is not white in above picture may suffer from the problem. The error shows up as not getting any more new satellites after having seen the 2nd QZSS satellite. It lasts until a factory reset of the SMT360 module. Neither software reboot nor power cycle will solve this problem, because the list of satellites is stored persistantly within the GNSS module.

	Radarcape users may not have noticed this problem as drastic as it is because there is an additional distance filter in the SMT360, or because the SMT360 crashed and by that had reset itself. Also, for timing purposes, a limited number of satellites is sufficient. However, readers of our Yahoo forum may have noticed a problem in Australia some time ago which most probable was due to this SMT360 bug, which at that time we did not identify as such.		Radarcape users may not have noticed this problem as drastic as it is because there is an additional distance filter in the SMT360, or because the SMT360 crashed and by that had reset itself. Also, for timing purposes, a limited number of satellites is sufficient. However, readers of our Yahoo forum may have noticed a problem in Australia some time ago which most probable was due to this SMT360 bug, which at that time we did not identify as such.

Nunojpg at 18:19, 1 March 2019

2019-03-01T18:19:41Z

← Older revision		Revision as of 18:19, 1 March 2019
Line 27:		Line 27:
	login to Radarcape shell with ssh, username root + eventually the password you've set		login to Radarcape shell with ssh, username root + eventually the password you've set

	<~~code~~>wget https://static.jetvision.de/tsip-cli-fwup -C /tmp~~<br>~~		<nowiki>wget https://static.jetvision.de/tsip-cli-fwup -P /tmp
	chmod +x /tmp/tsip-cli-fwup		chmod +x /tmp/tsip-cli-fwup
	systemctl stop radarcape		systemctl stop radarcape && /tmp/tsip-cli-fwup /dev/ttyS2 115200 && systemctl start radarcape</nowiki>
	/tmp/tsip-cli-fwup /dev/ttyS2 115200
	systemctl start radarcape</~~code~~>

	Please run these commands without too long delay in between because otherwise the Radarcape watchdog may affect it.		Please run these commands without too long delay in between because otherwise the Radarcape watchdog may affect it.
Line 37:		Line 35:
	The output then looks like this:		The output then looks like this:

	<~~code~~>Beaglebone Black detected, watchdog ping enabled Bundled firmware Size: 777244 Hardware: ResSMT 360 built: 2016-3-23 ~~10h~~ sn: ~~1161154239~~ version: 3023 Firmware: ResSMT 360 built: 2015-06-11 version: 1.1 build number: 0 Doing factory reset... OK, Remote Download is activated Test Remote Download...OK Start transfer...OK writing: 1564 left: 000000 Firmware updated successfully!		<nowiki>Version:20181010.0700
	</~~code~~>		Beaglebone Black detected, watchdog ping enabled
			Bundled firmware
			File: RES360_v1.05.bin
			Size: 777244
			Hardware: ResSMT 360 built: 2016-3-23 22h sn: 1161151764 version: 3023
			Firmware: ResSMT 360 built: 2015-06-11 version: 1.1 build number: 0
			Doing factory reset...
			OK, Remote Download is activated
			Test Remote Download...OK
			Start transfer...OK
			writing: 1564 left: 000000
			Firmware updated successfully!
			</nowiki>

	The tool is safe for itself, it can handle power outages and reprogramming, we never saw any module getting bricked by it.		The tool is safe for itself, it can handle power outages and reprogramming, we never saw any module getting bricked by it.

imported>Nunojpg at 17:47, 6 December 2018

2018-12-06T17:47:33Z

← Older revision		Revision as of 17:47, 6 December 2018
Line 45:		Line 45:
	2) Devices operating Major 2 Radarcape software that currently don't have problems:		2) Devices operating Major 2 Radarcape software that currently don't have problems:

	~~We at the moment have a release candidate for~~ Radarcape ~~firmware, which should be ready begin of October, 2018. This is grown too far as that we would like to add the SMT360 firmware update into it.~~		The next Radarcape release will include an integrated, silent SMT3680 update function (estimated January 2019).
	~~However, immediately after~~ release ~~of this, we~~ will ~~let follow another version with~~ an integrated, silent SMT3680 update function.
	If you think updating is not that urgent, please wait for this release.		If you think updating is not that urgent, please wait for this release.

imported>Nunojpg at 17:45, 6 December 2018

2018-12-06T17:45:32Z

← Older revision		Revision as of 17:45, 6 December 2018
Line 41:		Line 41:

	The tool is safe for itself, it can handle power outages and reprogramming, we never saw any module getting bricked by it.		The tool is safe for itself, it can handle power outages and reprogramming, we never saw any module getting bricked by it.
	After this, the GPS status in the web ~~menue~~ should display version 1.05		After this, the GPS status in the web menu should display version 1.05

	2) Devices operating Major 2 Radarcape software that currently don't have problems:		2) Devices operating Major 2 Radarcape software that currently don't have problems:

imported>Dl4mea: /* Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug */

2018-09-26T06:13:44Z

Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug

← Older revision		Revision as of 06:13, 26 September 2018
Line 10:		Line 10:
	Trimble confirmed to us that the SMT360 firmware 1.01, 1.02 and 1.03 has a bug when operating in the visibility of QZSS satellite system.		Trimble confirmed to us that the SMT360 firmware 1.01, 1.02 and 1.03 has a bug when operating in the visibility of QZSS satellite system.

	[[File:~~http://www.satnavi.jaxa.jp/e/news/images/~~img_1106012_01.gif]]		[[File:img_1106012_01.gif]]

	[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]		[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]

	All devices operating in the area that is not white in above picture may suffer from the problem. ~~<document link>~~ The error shows up as not getting any more new satellites after having seen the 2nd QZSS satellite. It lasts until a factory reset of the SMT360 module. Neither reboot nor power cycle solves the problem externally.		All devices operating in the area that is not white in above picture may suffer from the problem. The error shows up as not getting any more new satellites after having seen the 2nd QZSS satellite. It lasts until a factory reset of the SMT360 module. Neither reboot nor power cycle solves the problem externally.

	Radarcape users may not have noticed this problem as drastic as it is because there is an additional distance filter in the SMT360, or because the SMT360 crashed and by that had reset itself. Also, for timing purposes, a limited number of satellites is sufficient. However, readers of our Yahoo forum may have noticed a problem in Australia some time ago which most probable was due to this SMT360 bug, which at that time we did not identify as such.		Radarcape users may not have noticed this problem as drastic as it is because there is an additional distance filter in the SMT360, or because the SMT360 crashed and by that had reset itself. Also, for timing purposes, a limited number of satellites is sufficient. However, readers of our Yahoo forum may have noticed a problem in Australia some time ago which most probable was due to this SMT360 bug, which at that time we did not identify as such.
Line 25:		Line 26:

	login to Radarcape shell with ssh, username root + eventually the password you've set		login to Radarcape shell with ssh, username root + eventually the password you've set
	wget https://static.jetvision.de/tsip-cli-fwup -C /tmp
			<code>wget https://static.jetvision.de/tsip-cli-fwup -C /tmp<br>
	chmod +x /tmp/tsip-cli-fwup		chmod +x /tmp/tsip-cli-fwup
	systemctl stop radarcape		systemctl stop radarcape
	/tmp/tsip-cli-fwup /dev/ttyS2 115200		/tmp/tsip-cli-fwup /dev/ttyS2 115200
	systemctl start radarcape		systemctl start radarcape</code>

	Please run these commands without too long delay in between because otherwise the Radarcape watchdog may affect it.		Please run these commands without too long delay in between because otherwise the Radarcape watchdog may affect it.
Line 35:		Line 37:
	The output then looks like this:		The output then looks like this:

	Beaglebone Black detected, watchdog ping enabled Bundled firmware Size: 777244 Hardware: ResSMT 360 built: 2016-3-23 10h sn: 1161154239 version: 3023 Firmware: ResSMT 360 built: 2015-06-11 version: 1.1 build number: 0 Doing factory reset... OK, Remote Download is activated Test Remote Download...OK Start transfer...OK writing: 1564 left: 000000 Firmware updated successfully!		<code>Beaglebone Black detected, watchdog ping enabled Bundled firmware Size: 777244 Hardware: ResSMT 360 built: 2016-3-23 10h sn: 1161154239 version: 3023 Firmware: ResSMT 360 built: 2015-06-11 version: 1.1 build number: 0 Doing factory reset... OK, Remote Download is activated Test Remote Download...OK Start transfer...OK writing: 1564 left: 000000 Firmware updated successfully!
			</code>

	The tool is safe for itself, it can handle power outages and reprogramming, we never saw any module getting bricked by it.		The tool is safe for itself, it can handle power outages and reprogramming, we never saw any module getting bricked by it.

imported>Dl4mea: /* Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug */

2018-09-26T06:04:07Z

Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug

← Older revision		Revision as of 06:04, 26 September 2018
Line 10:		Line 10:
	Trimble confirmed to us that the SMT360 firmware 1.01, 1.02 and 1.03 has a bug when operating in the visibility of QZSS satellite system.		Trimble confirmed to us that the SMT360 firmware 1.01, 1.02 and 1.03 has a bug when operating in the visibility of QZSS satellite system.

			[[File:http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif]]
	[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]		[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]

imported>Dl4mea: /* Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug */

2018-09-26T06:03:22Z

Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug

← Older revision		Revision as of 06:03, 26 September 2018
Line 9:		Line 9:

	Trimble confirmed to us that the SMT360 firmware 1.01, 1.02 and 1.03 has a bug when operating in the visibility of QZSS satellite system.		Trimble confirmed to us that the SMT360 firmware 1.01, 1.02 and 1.03 has a bug when operating in the visibility of QZSS satellite system.

			[http://www.satnavi.jaxa.jp/e/news/images/img_1106012_01.gif QZSS Visibility]

	All devices operating in the area that is not white in above picture may suffer from the problem. <document link> The error shows up as not getting any more new satellites after having seen the 2nd QZSS satellite. It lasts until a factory reset of the SMT360 module. Neither reboot nor power cycle solves the problem externally.		All devices operating in the area that is not white in above picture may suffer from the problem. <document link> The error shows up as not getting any more new satellites after having seen the 2nd QZSS satellite. It lasts until a factory reset of the SMT360 module. Neither reboot nor power cycle solves the problem externally.

imported>Dl4mea at 05:26, 26 September 2018

2018-09-26T05:26:12Z

@@ Line 1: / Line 1: @@
 {{#seo:
-|title=Trimble SMT360
+|title=Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug
 |titlemode=replace
 |keywords=radarcape,Trimble,SMT360,GPS
-|description=Radarcape Frequently Asked Questions (FAQ)
+|description=Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug
 }}
-====Q: Will you provide solutions of all the application ideas?====
+====Trimble SMT360 Firmware 1.01-1.03 QZSS Firmware Bug====

imported>Dl4mea: Created page with "{{#seo: |title=Trimble SMT360 |titlemode=replace |keywords=radarcape,Trimble,SMT360,GPS |description=Radarcape Frequently Asked Questions (FAQ) }} ====Q: Will you provide so..."

2018-09-26T05:24:07Z

Created page with "{{#seo: |title=Trimble SMT360 |titlemode=replace |keywords=radarcape,Trimble,SMT360,GPS |description=Radarcape Frequently Asked Questions (FAQ) }} ====Q: Will you provide so..."

New page

{{#seo:
|title=Trimble SMT360
|titlemode=replace
|keywords=radarcape,Trimble,SMT360,GPS
|description=Radarcape Frequently Asked Questions (FAQ)
}}

====Q: Will you provide solutions of all the application ideas?====