STorM32 FAQ - Revision history

OlliW at 17:20, 21 June 2019

2019-06-21T17:20:47Z

← Older revision		Revision as of 19:20, 21 June 2019
Line 1:		Line 1:
			''This is the "old" STorM32-BGC documentation, for I2C-IMU firmware versions (versions up to v0.96).''

	== Electronics ==		== Electronics ==

OlliW: /* Which USB-TTL should I use? */

2015-11-30T15:29:13Z

Which USB-TTL should I use?

← Older revision		Revision as of 17:29, 30 November 2015
Line 33:		Line 33:
	* Chip set: Different chip sets by different companies are around to accomplish essentially the same task. For instance, FTDI is such a company, which produces e.g. the FT232RL chip set which uses UART logical levels. Unfortunately, it has become custom to just call any USB serial adapter a FTDI adapter, even if it uses a chip set from e.g. SILABS, and sometimes even if it doesn't use TTL levels but RS232-type levels.		* Chip set: Different chip sets by different companies are around to accomplish essentially the same task. For instance, FTDI is such a company, which produces e.g. the FT232RL chip set which uses UART logical levels. Unfortunately, it has become custom to just call any USB serial adapter a FTDI adapter, even if it uses a chip set from e.g. SILABS, and sometimes even if it doesn't use TTL levels but RS232-type levels.

	After that introduction, the real beef. Currently, four chip sets are around: ~~FT2323RL~~ by FTDI, CP2102 by SILABS, CH340 by WCH, PL2303HX by PROLIFIC (more may exist but these are most relevant). My '''''personal''''' (!) account of them is this as follows:		After that introduction, the real beef. Currently, four chip sets are around: FT232RL or similar by FTDI, CP2102 by SILABS, CH340 by WCH, PL2303HX by PROLIFIC (more may exist but these are most relevant). My '''''personal''''' (!) account of them is this as follows:

	* '''''~~FT2323RL~~ - FTDI''''': My favorite. According to web reports there is a slight chance to get a fake, but the real chip just works flawlessly without any issues, and fakes can be avoided by buying from trusted sources. In addition, this set allows to baudrates of 2000000 bps, as needed for the STorM32 NT concept, out of the box without any further configuration.		* '''''FT232RL - FTDI''''': My favorite. According to web reports there is a slight chance to get a fake, but the real chip just works flawlessly without any issues, and fakes can be avoided by buying from trusted sources. In addition, this set allows to baudrates of 2000000 bps, as needed for the STorM32 NT concept, out of the box without any further configuration.

	* '''''CP2102 - SILABS''''': There used to be issues with drivers, but this seems to have been overcome since a while, which makes this chip set a reliable and solid choice. However, it doesn't support a baudrate of 2000000 bps as needed for the STorM32 NT concept out of the box, but can be configured to do so via some dedicated configuration software.		* '''''CP2102 - SILABS''''': There used to be issues with drivers, but this seems to have been overcome since a while, which makes this chip set a reliable and solid choice. However, it doesn't support a baudrate of 2000000 bps as needed for the STorM32 NT concept out of the box, but can be configured to do so via some dedicated configuration software.

OlliW: /* Which USB-TTL should I use? */

2015-11-28T10:39:42Z

Which USB-TTL should I use?

← Older revision		Revision as of 12:39, 28 November 2015
Line 43:		Line 43:
	* '''''PL2303HX - PROLIFIC''''': I had one PLxxxx adapter, and it didn't provide TTL but RS232-type signals. However, some web reports using some PLxxxx report using it for microcontroller applications. The data sheet for these chips, including the PL2303HX, I find unclear in this point. So, the bottom line, I find the situation for these chips quite confusing, and thus simply stay away from them, as there are alternatives.		* '''''PL2303HX - PROLIFIC''''': I had one PLxxxx adapter, and it didn't provide TTL but RS232-type signals. However, some web reports using some PLxxxx report using it for microcontroller applications. The data sheet for these chips, including the PL2303HX, I find unclear in this point. So, the bottom line, I find the situation for these chips quite confusing, and thus simply stay away from them, as there are alternatives.

	'''''Conclusion:''' For flashing the main STorM32 controller board USB adapters with either FTDI, ~~CH4340~~, or CP2102 chip sets can be used without issues, while for flashing NT modules only FTDI and CH340 adapters work out of the box. CP2102 adapters need some configuration to handle the high baudrate of the NT bus, see [[How to configure CP2102 USB adapters for high baud rates]]. USB adapters with PL2303 chips NEVER work since they don't provide TTL levels.''		'''''Conclusion:''' For flashing the main STorM32 controller board USB adapters with either FTDI, CH340, or CP2102 chip sets can be used without issues, while for flashing NT modules only FTDI and CH340 adapters work out of the box. CP2102 adapters need some configuration to handle the high baudrate of the NT bus, see [[How to configure CP2102 USB adapters for high baud rates]]. USB adapters with PL2303 chips NEVER work since they don't provide TTL levels.''

	==== What about the magnetometer support? ====		==== What about the magnetometer support? ====

OlliW: /* Which USB-TTL should I use? */

2015-11-28T10:39:07Z

Which USB-TTL should I use?

← Older revision		Revision as of 12:39, 28 November 2015
Line 27:		Line 27:
	==== Which USB-TTL should I use? ====		==== Which USB-TTL should I use? ====

	The situation with the USB-TTL adapters is a bit delicate, because of the number of types around, and because improper wording has become widely used practice. For instance, "FTDI adapter", "serial adapter", "TTL adapter", "RS232 adapter", and so on, may or may not mean one and the same thing. So, first some explanations. Two points need to be realized:		The situation with the USB-TTL adapters is a bit delicate, because of the number of types around, and because improper wording has become widely used practice. For instance, "FTDI adapter", "serial adapter", "TTL adapter", "RS232 adapter", and so on, may or may not mean one and the same thing. So, first some explanations (or skip to the end for the conclusions). Two points need to be realized:

	* Logical levels: Three types are around, namely RS232, RS232 at 5V level, and UART. The original RS232, as it was used by the "historical" serial bus on PCs, works with +-15V levels, with -15V representing logical 0. For many cases it was more convenient to narrow the voltage range to 0 .. 5V, so that 0V or LOW represents logic 0. UART is the serial unit found in micro-controllers, and it works with voltages of 0 ... 3.3/5V, but - importantly - logic 0 is represented by 3.3V/5V or HIGH. That is, the logic is inverted with respect to RS232, and obviously both are incompatible. This gives rise to many confusions. E.g., since both 5V-RS232 and UART formally work with TTL levels (or something like it), both were and are called "TTL adapters". Also, since all three are serial protocols all three were and are called "serial adapters". Nowadays it seems that a kind of consensus has been reach at least as much as that "TTL" in most cases means UART logical levels (but you got the sense, you cannot count on that). In this wiki we will use "USB-TTL adapter" to denote a UART/microcontroller compatible adapter.		* Logical levels: Three types are around, namely RS232, RS232 at 5V level, and UART. The original RS232, as it was used by the "historical" serial bus on PCs, works with +-15V levels, with -15V representing logical 0. For many cases it was more convenient to narrow the voltage range to 0 .. 5V, so that 0V or LOW represents logic 0. UART is the serial unit found in micro-controllers, and it works with voltages of 0 ... 3.3/5V, but - importantly - logic 0 is represented by 3.3V/5V or HIGH. That is, the logic is inverted with respect to RS232, and obviously both are incompatible. This gives rise to many confusions. E.g., since both 5V-RS232 and UART formally work with TTL levels (or something like it), both were and are called "TTL adapters". Also, since all three are serial protocols all three were and are called "serial adapters". Nowadays it seems that a kind of consensus has been reach at least as much as that "TTL" in most cases means UART logical levels (but you got the sense, you cannot count on that). In this wiki we will use "USB-TTL adapter" to denote a UART/microcontroller compatible adapter.
Line 35:		Line 35:
	After that introduction, the real beef. Currently, four chip sets are around: FT2323RL by FTDI, CP2102 by SILABS, CH340 by WCH, PL2303HX by PROLIFIC (more may exist but these are most relevant). My '''''personal''''' (!) account of them is this as follows:		After that introduction, the real beef. Currently, four chip sets are around: FT2323RL by FTDI, CP2102 by SILABS, CH340 by WCH, PL2303HX by PROLIFIC (more may exist but these are most relevant). My '''''personal''''' (!) account of them is this as follows:

	'''''FT2323RL - FTDI''''': My favorite. According to web reports there is a slight chance to get a fake, but the real chip just works flawlessly without any issues, and fakes can be avoided by buying from trusted sources. In addition, this set allows to baudrates of 2000000 bps, as needed for the STorM32 NT concept, out of the box without any further configuration.		* '''''FT2323RL - FTDI''''': My favorite. According to web reports there is a slight chance to get a fake, but the real chip just works flawlessly without any issues, and fakes can be avoided by buying from trusted sources. In addition, this set allows to baudrates of 2000000 bps, as needed for the STorM32 NT concept, out of the box without any further configuration.

	'''''CP2102 - SILABS''''': There used to be issues with drivers, but this seems to have been overcome since a while, which makes this chip set a reliable and solid choice. However, it doesn't support a baudrate of 2000000 bps as needed for the STorM32 NT concept out of the box, but can be configured to do so via some dedicated configuration software.		* '''''CP2102 - SILABS''''': There used to be issues with drivers, but this seems to have been overcome since a while, which makes this chip set a reliable and solid choice. However, it doesn't support a baudrate of 2000000 bps as needed for the STorM32 NT concept out of the box, but can be configured to do so via some dedicated configuration software.

	'''''CH340 - WCH''''': The driver is not auto-installed by Win. I myself stopped here, but once the correct driver is installed it is reported to be a viable choice. It is also reported to work with 2000000 bps as needed for the STorM32 NT concept out of the box.		* '''''CH340 - WCH''''': The driver is not auto-installed by Win. I myself stopped here, but once the correct driver is installed it is reported to be a viable choice. It is also reported to work with 2000000 bps as needed for the STorM32 NT concept out of the box.

	'''''PL2303HX - PROLIFIC''''': I had one PLxxxx adapter, and it didn't provide TTL but RS232-type signals. However, some web reports using some PLxxxx report using it for microcontroller applications. The data sheet for these chips, including the PL2303HX, I find unclear in this point. So, the bottom line, I find the situation for these chips quite confusing, and thus simply stay away from them, as there are alternatives.		* '''''PL2303HX - PROLIFIC''''': I had one PLxxxx adapter, and it didn't provide TTL but RS232-type signals. However, some web reports using some PLxxxx report using it for microcontroller applications. The data sheet for these chips, including the PL2303HX, I find unclear in this point. So, the bottom line, I find the situation for these chips quite confusing, and thus simply stay away from them, as there are alternatives.

	'''''Conclusion:''' For flashing the main STorM32 controller board USB adapters with either FTDI, CH4340, or CP2102 chip sets can be used without issues, while for flashing NT modules only FTDI and CH340 adapters work out of the box. CP2102 adapters need some configuration to handle the high baudrate of the NT bus, see [[How to configure CP2102 USB adapters for high baud rates]]. USB adapters with PL2303 chips NEVER work since they don't provide TTL levels.''		'''''Conclusion:''' For flashing the main STorM32 controller board USB adapters with either FTDI, CH4340, or CP2102 chip sets can be used without issues, while for flashing NT modules only FTDI and CH340 adapters work out of the box. CP2102 adapters need some configuration to handle the high baudrate of the NT bus, see [[How to configure CP2102 USB adapters for high baud rates]]. USB adapters with PL2303 chips NEVER work since they don't provide TTL levels.''

OlliW: /* Which USB-TTL should I use? */

2015-11-28T10:37:33Z

Which USB-TTL should I use?

← Older revision		Revision as of 12:37, 28 November 2015
Line 41:		Line 41:
	'''''CH340 - WCH''''': The driver is not auto-installed by Win. I myself stopped here, but once the correct driver is installed it is reported to be a viable choice. It is also reported to work with 2000000 bps as needed for the STorM32 NT concept out of the box.		'''''CH340 - WCH''''': The driver is not auto-installed by Win. I myself stopped here, but once the correct driver is installed it is reported to be a viable choice. It is also reported to work with 2000000 bps as needed for the STorM32 NT concept out of the box.

	'''''PL2303HX - PROLIFIC''''': I had one PLxxxx adapter, and it didn't provide TTL but RS232-type signals. However, some web reports using some PLxxxx report using it for microcontroller applications. The data sheet for these chips, including the PL2303HX, I find unclear in this point. So, the bottom line, I find the situation for these chips quite confusing, and thus simply stay away from them, as there are alternatives.		'''''PL2303HX - PROLIFIC''''': I had one PLxxxx adapter, and it didn't provide TTL but RS232-type signals. However, some web reports using some PLxxxx report using it for microcontroller applications. The data sheet for these chips, including the PL2303HX, I find unclear in this point. So, the bottom line, I find the situation for these chips quite confusing, and thus simply stay away from them, as there are alternatives.

			'''''Conclusion:''' For flashing the main STorM32 controller board USB adapters with either FTDI, CH4340, or CP2102 chip sets can be used without issues, while for flashing NT modules only FTDI and CH340 adapters work out of the box. CP2102 adapters need some configuration to handle the high baudrate of the NT bus, see [[How to configure CP2102 USB adapters for high baud rates]]. USB adapters with PL2303 chips NEVER work since they don't provide TTL levels.''

	==== What about the magnetometer support? ====		==== What about the magnetometer support? ====

OlliW at 10:34, 28 November 2015

2015-11-28T10:34:56Z

← Older revision		Revision as of 12:34, 28 November 2015
Line 62:		Line 62:
	{{GUI\|Write}} writes the values of the GUI to the board and makes them effective immediately. The changes last until the board is reset or powered down.		{{GUI\|Write}} writes the values of the GUI to the board and makes them effective immediately. The changes last until the board is reset or powered down.

	{{GUI\|Store}} makes that the board stores its current values into the ~~EEProm~~ so that they become permanent. The settings stored in the ~~EEprom~~ will be used at power up.		{{GUI\|Store}} makes that the board stores its current values into the EEPROM so that they become permanent. The settings stored in the EEPROM will be used at power up.

	{{GUI\|Write+Store}} does first a Write and then a Store.		{{GUI\|Write+Store}} does first a Write and then a Store.

	Thus: With the {{GUI\|Write}} button, all parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the ~~Eeprom~~, i.e., changes will be lost after a power down. To store changes permanently do a {{GUI\|Write+Store}}, e.g., by clicking the check box next to the {{GUI\|Write}} button which turns it into a {{GUI\|Write+Store}} button.		Thus: With the {{GUI\|Write}} button, all parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the EEPROM, i.e., changes will be lost after a power down. To store changes permanently do a {{GUI\|Write+Store}}, e.g., by clicking the check box next to the {{GUI\|Write}} button which turns it into a {{GUI\|Write+Store}} button.

	==== How to enter precise parameter values? ====		==== How to enter precise parameter values? ====
Line 80:		Line 80:
	Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.		Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.

	==== Flashing with the ~~usb~~-~~ttl~~ adapter produces Windows error messages ====		==== Flashing with the USB-TTL adapter produces Windows error messages ====

	If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you're not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.		If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you're not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.

OlliW at 10:33, 28 November 2015

2015-11-28T10:33:26Z

@@ Line 23: / Line 23: @@
 '''''v1.1/v1.2/v1.3 boards:''''' Motors with resistances of 12 Ohm or larger have been tested to be well handled at 4S, motors with 10 Ohm may be handled with care; for the latest summary see [http://www.rcgroups.com/forums/showpost.php?p=30564101&postcount=3166 here] (for details see also [//www.rcgroups.com/forums/showthread.php?t=2055844&page=2&pp=50#post27515444 here], [//www.rcgroups.com/forums/showthread.php?t=2055844&page=15&pp=50#post28578479 here], [http://www.rcgroups.com/forums/showpost.php?p=28825482&postcount=947 here] and [http://www.rcgroups.com/forums/showpost.php?p=28852888&postcount=953 here])''.
-'''''v1.31 board:''''' As it uses the same motor driver as the "original" 32-bit AlexMos/BaseCam gimbal controlelr board, it can be assumed that it works also for all motors/setups for which the BaseCam board works.
+'''''v1.31 board:''''' As it uses the same motor driver as the "original" 32-bit AlexMos/BaseCam gimbal controller board, it can be assumed that it works also for all motors/setups for which the BaseCam board works.
 ==== What about the magnetometer support? ====

OlliW: /* Which drivers are needed for the USB? */

2015-08-23T09:52:28Z

Which drivers are needed for the USB?

← Older revision		Revision as of 11:52, 23 August 2015
Line 56:		Line 56:
	==== Which drivers are needed for the USB? ====		==== Which drivers are needed for the USB? ====

	On Win7 the driver is usually installed automatically ~~(this~~ may take ~~few~~ minutes, be patient!). The correct VCP driver, usable also for WinXP and Win8/8.1, can ~~also~~ be obtained from [http://www.st.com/web/en/catalog/tools/PF257938 ~~here~~] ~~(it~~ is crucial to follow the instructions in the readme.txt file, otherwise it won't work~~). <~~!~~-- [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here]~~. ~~-->~~		On Win7 the driver is usually installed automatically. This may take some minutes, be patient! It is important to wait until Win7 has finished the install before doing anything else. The correct Virtual Com Port (VCP) driver, usable also for WinXP and Win8/8.1, can be obtained from the [http://www.st.com/web/en/catalog/tools/PF257938 STM download page]. {{COMMENT\| It is crucial to follow the instructions in the readme.txt file, otherwise it won't work!}}.

	==== Storing the parameter values to the EEPROM doesn't seem to work ====		==== Storing the parameter values to the EEPROM doesn't seem to work ====

OlliW: /* How does Read, Write, and Store work? */

2015-06-25T12:50:30Z

How does Read, Write, and Store work?

← Older revision		Revision as of 14:50, 25 June 2015
Line 48:		Line 48:
	{{GUI\|Write+Store}} does first a Write and then a Store.		{{GUI\|Write+Store}} does first a Write and then a Store.

	Thus: With the {{GUI\|Write}} button, all parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a {{GUI\|Write+Store}}, e.g., by clicking the check box next to the {{GUI\|Write}} button.		Thus: With the {{GUI\|Write}} button, all parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a {{GUI\|Write+Store}}, e.g., by clicking the check box next to the {{GUI\|Write}} button which turns it into a {{GUI\|Write+Store}} button.

	==== How to enter precise parameter values? ====		==== How to enter precise parameter values? ====

OlliW at 18:09, 6 June 2015

2015-06-06T18:09:03Z

← Older revision		Revision as of 20:09, 6 June 2015
Line 50:		Line 50:
	Thus: With the {{GUI\|Write}} button, all parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a {{GUI\|Write+Store}}, e.g., by clicking the check box next to the {{GUI\|Write}} button.		Thus: With the {{GUI\|Write}} button, all parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a {{GUI\|Write+Store}}, e.g., by clicking the check box next to the {{GUI\|Write}} button.

	==== ~~Storing the~~ parameter values ~~to the EEPROM doesn't seem to work~~ ====		==== How to enter precise parameter values? ====

	~~Please double-check that~~ the ~~correct firmware for your board has been flashed~~. The ~~problem typically happens then e.g~~. the ~~firmware for a F103RB is flashed onto a board with a F103RC~~.		The o323BGCTool GUI doesn't allow to enter values in the text fields directly. The sliders can be moved using the mouse, or via the up/down keys when selected. The later allows precise adjustment of the values.

	==== Which drivers are needed for the USB? ====		==== Which drivers are needed for the USB? ====

	On Win7 the driver is usually installed automatically (this may take few minutes, be patient!). The correct VCP driver, usable also for WinXP and Win8/8.1, can also be obtained from [http://www.st.com/web/en/catalog/tools/PF257938 here] (it is crucial to follow the instructions in the readme.txt file, otherwise it won't work). <!-- [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here]. -->		On Win7 the driver is usually installed automatically (this may take few minutes, be patient!). The correct VCP driver, usable also for WinXP and Win8/8.1, can also be obtained from [http://www.st.com/web/en/catalog/tools/PF257938 here] (it is crucial to follow the instructions in the readme.txt file, otherwise it won't work). <!-- [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here]. -->

			==== Storing the parameter values to the EEPROM doesn't seem to work ====

			Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.

	==== Flashing with the usb-ttl adapter produces Windows error messages ====		==== Flashing with the usb-ttl adapter produces Windows error messages ====