AME Hardware - Revision history

Ctreber: /* Arduino */

2018-06-26T12:05:30Z

Arduino

← Older revision		Revision as of 12:05, 26 June 2018
Line 28:		Line 28:
	* Serial Peripheral Interface (SPI): I/O pins 11, 12, 13 become Master Out Slave In (MOSI), Master In Slave Out (MISO), Serial Clock (SCK). This is a serial bidirectional bus with transfer in both directions at the same time. Slaves must be selected using a digital I/O pin, but there is no protocol overhead. Very efficient, but uses a few pins plus one pin for each device.		* Serial Peripheral Interface (SPI): I/O pins 11, 12, 13 become Master Out Slave In (MOSI), Master In Slave Out (MISO), Serial Clock (SCK). This is a serial bidirectional bus with transfer in both directions at the same time. Slaves must be selected using a digital I/O pin, but there is no protocol overhead. Very efficient, but uses a few pins plus one pin for each device.
	* Inter-Integrated Circuit or Two-Wire Interface (I2C or TWI): I/O pins A4, A5 become Serial Data (SDA), Serial Clock (SCL). This is a serial bidirectional bus. Communication partners are selected by using addresses transmitted over the bus using a communications protocol. More talkative, but uses only two pins for any amount of devices.		* Inter-Integrated Circuit or Two-Wire Interface (I2C or TWI): I/O pins A4, A5 become Serial Data (SDA), Serial Clock (SCL). This is a serial bidirectional bus. Communication partners are selected by using addresses transmitted over the bus using a communications protocol. More talkative, but uses only two pins for any amount of devices.

			Standard-use of pins:

			* 7: Logsury on/off (optional if you don't want to use the runtime-configuration option of Logsury)
			* 8: ESP8266 reset (optional if you don't want to make use of the reset option of AC_ESP8266)
			* 9: Status LED (optional if you don't want to use the LED-version of AC_EventFacility)

	==ESP8266==		==ESP8266==

Ctreber at 20:35, 21 June 2018

2018-06-21T20:35:04Z

← Older revision		Revision as of 20:35, 21 June 2018
Line 24:		Line 24:
	Some I/O pings have alternative meanings depending whether you use certain interfaces (if you don't, they're all yours):		Some I/O pings have alternative meanings depending whether you use certain interfaces (if you don't, they're all yours):

	* Serial interface: O, 1 become Transmit Data (TXD), Receive Data (RDX)		* Serial interface: I/O pins 0, 1 become Transmit Data (TXD), Receive Data (RDX)
	* External interrupts: 2, 3		* External interrupts: I/O pins 2, 3
	* Serial Peripheral Interface (SPI): 11, 12, 13 become Master Out Slave In (MOSI), Master In Slave Out (MISO), Serial Clock (SCK). This is a serial bidirectional bus. Slaves must be selected using a digital I/O pin, but there is no protocol overhead.		* Serial Peripheral Interface (SPI): I/O pins 11, 12, 13 become Master Out Slave In (MOSI), Master In Slave Out (MISO), Serial Clock (SCK). This is a serial bidirectional bus with transfer in both directions at the same time. Slaves must be selected using a digital I/O pin, but there is no protocol overhead. Very efficient, but uses a few pins plus one pin for each device.
	* Inter-Integrated Circuit or Two-Wire Interface (I2C or TWI): A4, A5 become Serial Data (SDA), Serial Clock (SCL). This is a serial bidirectional bus. Communication partners are selected by using addresses transmitted over the bus using a communications protocol.		* Inter-Integrated Circuit or Two-Wire Interface (I2C or TWI): I/O pins A4, A5 become Serial Data (SDA), Serial Clock (SCL). This is a serial bidirectional bus. Communication partners are selected by using addresses transmitted over the bus using a communications protocol. More talkative, but uses only two pins for any amount of devices.

	==ESP8266==		==ESP8266==

Ctreber at 23:20, 19 June 2018

2018-06-19T23:20:39Z

@@ Line 10: / Line 10: @@
 Cheap versions can be ordered from Chinese suppliers for 2.50€ a piece. I'm using them all the time, and they just work fine (didn't have a single dud in 20+ Arduinos).
 ==ESP8266==
@@ Line 23: / Line 41: @@
 * WLAN station/ AP mode. Determines if the chip acts as a client that logs into an existing WLAN or if the chip acts as a WLAN access points which other clients can connect to.
-I have had ESPs that misbehaved a lot, and the chip and the serial connection are prone to problems in general (IMHO!). With "misbehave" I mean:
+The pins:
 * Simply not reacting as expected (replying to a command in unexpected ways)
@@ Line 36: / Line 71: @@
 ==Why not just an ESP8266?==
-Good question! Less hardware, more memory, direct function calls instead of serial communications all sound good. But, the Arduino has more I/O pins. I found programming the ESP is slow, and the ESP is less forgiving when it is handled the wrong way, be it hardware or even software. I fried an ESP by just trying to blink on all I/O pins, to find out which number corresponds to which pin. After the ESP did not interact with the programmer any more.
+Good question! Less hardware, more memory, direct function calls instead of serial communications all sound good. But, the Arduino has more I/O pins. I found programming the ESP is slow, and the ESP is less forgiving when it is handled the wrong way, be it hardware or even software. I fried an ESP by just trying to "blink" all I/O pins, to find out which number corresponds to which pin. After that the ESP did not interact with the programmer any more :-(.
 [[The AME Stack]]
 __NOTOC__

Ctreber: /* ESP8266 */

2018-06-19T22:33:44Z

ESP8266

← Older revision		Revision as of 22:33, 19 June 2018
Line 15:		Line 15:
	'' '''Work in progress, stand by. Some information may be plain wrong, so... Last edit 19.06.2018.''' ''		'' '''Work in progress, stand by. Some information may be plain wrong, so... Last edit 19.06.2018.''' ''

	The ESP8266 is IP and WLAN on a chip - SSL, TCP, UDP, WLAN, as a client or even as an access point (limited to 4 connections).		The ESP8266 is IP- and WLAN-connectivity on a chip - SSL, TCP, UDP, WLAN; as a client or even as an access point (limited to 4 connections).

	The chip supports a number of modes that exclude each other:		The chip supports a number of modes that exclude each other:

Ctreber at 22:33, 19 June 2018

2018-06-19T22:33:04Z

← Older revision		Revision as of 22:33, 19 June 2018
Line 1:		Line 1:
	[[The AME Stack]]		[[The AME Stack]]

	=AME Hardware=		=AME Stack (Hardware)=

			[[File:20170802T115833.jpg\|left\|thumb\|600px\|Voltage controller (left), Arduino (top right), and ESP8266 (bottom right)]]<br clear="all"/>

	==Arduino==		==Arduino==

Ctreber: /* ESP8266 */

2018-06-19T13:25:48Z

ESP8266

← Older revision		Revision as of 13:25, 19 June 2018
Line 10:		Line 10:

	==ESP8266==		==ESP8266==

			'' '''Work in progress, stand by. Some information may be plain wrong, so... Last edit 19.06.2018.''' ''

	The ESP8266 is IP and WLAN on a chip - SSL, TCP, UDP, WLAN, as a client or even as an access point (limited to 4 connections).		The ESP8266 is IP and WLAN on a chip - SSL, TCP, UDP, WLAN, as a client or even as an access point (limited to 4 connections).

	The ESP is its own ~~microcomputer~~, just like the Arduino. And it can be programmed, just like an Arduino.		The chip supports a number of modes that exclude each other:

			* Single/ multiple connection. Determines if only a single connection can be active at the same time, or up to four connections. The mode can only be changed if there currently is no connection. For SSL only single connection mode is supported (I guess SSL is too demanding for multiple connections). Multiple connection mode is required for server mode. Why would you limit yourself to a single connection? I don't know, but I use single connection mode because I need only one connection (to the MQTT broker), and sending out commands and parsing replies is more complex in multiple connection mode.
			* IP client/ server mode. Determines if the chips opens connections as a client or if it accepts incoming connections as a server. The latter requires multiple connection mode.
			* WLAN station/ AP mode. Determines if the chip acts as a client that logs into an existing WLAN or if the chip acts as a WLAN access points which other clients can connect to.

			I have had ESPs that misbehaved a lot, and the chip and the serial connection are prone to problems in general (IMHO!). With "misbehave" I mean:

			* Simply not reacting as expected (replying to a command in unexpected ways)
			* Not be able to establish a WLAN or TCP connection
			* Being stuck in some internal odd state that produces gobs of output
			* Random reboots

			These problems can all be addressed though. Sometimes a software rest helps (a command sent via the serial interface). Sometime a hardware reset is required. On rarer occasions the power needs to be cycled. My software stack uses software and hardware resets. In order to perform hardware resets I connect an Arduino I/O pin to the ESP reset pin (the library supports this). It would be easy to extend that scheme to cycling the power by using another I/O pin, and a transistor that switches the chip off and on again.

			The ESP is its own computer on a chip, just like the Arduino. And it can be programmed by you, just like an Arduino. For why I don't use it ''instead'' of an Arduino, please see the next section.

	==Why not just an ESP8266?==		==Why not just an ESP8266?==

Ctreber: Created page with "The AME Stack =AME Hardware= ==Arduino== The Arduino is a computer on a chip - CPU, memory for programs (ROM, flashable), memory for variables (RAM, volatile), memory f..."

2018-06-19T10:16:21Z

Created page with "The AME Stack =AME Hardware= ==Arduino== The Arduino is a computer on a chip - CPU, memory for programs (ROM, flashable), memory for variables (RAM, volatile), memory f..."

New page

[[The AME Stack]]

=AME Hardware=

==Arduino==

The Arduino is a computer on a chip - CPU, memory for programs (ROM, flashable), memory for variables (RAM, volatile), memory for data (EPROM, non-volatile, runtime-programmable), counters, timers, I/O pins, and various interfaces (shared with the I/O pins; interrupts, serial, I2C, SPI). Different models offer different amounts of assets.

Cheap versions can be ordered from Chinese suppliers for 2.50€ a piece. I'm using them all the time, and they just work fine (didn't have a single dud in 20+ Arduinos).

==ESP8266==

The ESP8266 is IP and WLAN on a chip - SSL, TCP, UDP, WLAN, as a client or even as an access point (limited to 4 connections).

The ESP is its own microcomputer, just like the Arduino. And it can be programmed, just like an Arduino.

==Why not just an ESP8266?==

Good question! Less hardware, more memory, direct function calls instead of serial communications all sound good. But, the Arduino has more I/O pins. I found programming the ESP is slow, and the ESP is less forgiving when it is handled the wrong way, be it hardware or even software. I fried an ESP by just trying to blink on all I/O pins, to find out which number corresponds to which pin. After the ESP did not interact with the programmer any more.

[[The AME Stack]]
__NOTOC__