Remove ERR pulses from standard library nodes

[nkrkv]

First-class error support is coming to XOD. The standard library should use the new mechanism as it more flexible and because the standard library is an instance of how things should be done.

Currently, the following patches use ERR-pulses:

$ rg ERR -l workspace | xargs -n1 dirname | sort | uniq
...
workspace/__lib__/xod/common-hardware/adxl335-accelerometer
workspace/__lib__/xod/common-hardware/analog-sensor
workspace/__lib__/xod/common-hardware/button
workspace/__lib__/xod/common-hardware/dht11-thermometer
workspace/__lib__/xod/common-hardware/dht2x-thermometer
workspace/__lib__/xod/common-hardware/dhtxx-read-raw
workspace/__lib__/xod/common-hardware/ds1307-rtc-read
workspace/__lib__/xod/common-hardware/ds1307-rtc-write
workspace/__lib__/xod/common-hardware/ds18b20-thermometer
workspace/__lib__/xod/common-hardware/gp2y0a02-range-meter
workspace/__lib__/xod/common-hardware/gp2y0a21-range-meter
workspace/__lib__/xod/common-hardware/gp2y0a41-range-meter
workspace/__lib__/xod/common-hardware/h-bridge-dc-motor
workspace/__lib__/xod/common-hardware/hc-sr04-ultrasonic-range
workspace/__lib__/xod/common-hardware/hc-sr04-ultrasonic-time
workspace/__lib__/xod/common-hardware/l3g4200-gyro
workspace/__lib__/xod/common-hardware/l3gd20h-gyro
workspace/__lib__/xod/common-hardware/led
workspace/__lib__/xod/common-hardware/lis331dlh-accelerometer
workspace/__lib__/xod/common-hardware/lis331hh-accelerometer
workspace/__lib__/xod/common-hardware/lis3dh-accelerometer
workspace/__lib__/xod/common-hardware/lps331-barometer
workspace/__lib__/xod/common-hardware/pot
workspace/__lib__/xod/common-hardware/sd-log
workspace/__lib__/xod/common-hardware/servo
workspace/__lib__/xod/common-hardware/st-barometer-read-pressure-raw
workspace/__lib__/xod/common-hardware/st-barometer-read-tmp-raw
workspace/__lib__/xod/common-hardware/st-barometer-write-register
workspace/__lib__/xod/common-hardware/st-imu-generic-sensor
workspace/__lib__/xod/common-hardware/st-imu-read-xyz
workspace/__lib__/xod/common-hardware/st-imu-write-register
workspace/__lib__/xod/common-hardware/thermometer-tmp36
workspace/__lib__/xod/core/error
workspace/__lib__/xod/core/format-progress
workspace/__lib__/xod-dev/ds-rtc/read
workspace/__lib__/xod-dev/ds-rtc/rtc
workspace/__lib__/xod-dev/ds-rtc/write
workspace/__lib__/xod-dev/esp8266/close
workspace/__lib__/xod-dev/esp8266/connect
workspace/__lib__/xod-dev/esp8266/connect-wifi
workspace/__lib__/xod-dev/esp8266/http-request(esp8266-inet)
workspace/__lib__/xod-dev/esp8266/kick
workspace/__lib__/xod-dev/esp8266-mcu/connect
workspace/__lib__/xod-dev/esp8266-mcu/http-request(esp8266-mcu-inet)
workspace/__lib__/xod-dev/esp8266-mcu/open-tcp
workspace/__lib__/xod-dev/esp8266-mcu/read-byte
workspace/__lib__/xod-dev/esp8266-mcu/send
workspace/__lib__/xod-dev/esp8266/open-tcp
workspace/__lib__/xod-dev/esp8266/receive-one-byte
workspace/__lib__/xod-dev/esp8266/send
workspace/__lib__/xod-dev/esp8266/set-station-mode
workspace/__lib__/xod-dev/pn532-nfc/init
workspace/__lib__/xod-dev/pn532-nfc/nfc-scanner
workspace/__lib__/xod-dev/pn532-nfc/pair-tag
workspace/__lib__/xod-dev/pn532-nfc/read-page
workspace/__lib__/xod-dev/pn532-nfc/write-page
workspace/__lib__/xod-dev/sharp-irm/gp2y0a02-range-meter
workspace/__lib__/xod-dev/sharp-irm/gp2y0a21-range-meter
workspace/__lib__/xod-dev/sharp-irm/gp2y0a41-range-meter
workspace/__lib__/xod-dev/w5500/connect
workspace/__lib__/xod-dev/w5500/connect-blocking
workspace/__lib__/xod-dev/w5500/connect-manual
workspace/__lib__/xod-dev/w5500/connect-manual-blocking
workspace/__lib__/xod-dev/w5500/ethernet-shield
workspace/__lib__/xod-dev/w5500/http-request(w5500-inet)
workspace/__lib__/xod-dev/w5500/open-tcp
workspace/__lib__/xod-dev/w5500/send
workspace/__lib__/xod/gpio/analog-read
workspace/__lib__/xod/gpio/digital-read
workspace/__lib__/xod/gpio/digital-write
workspace/__lib__/xod/gpio/pwm-write
workspace/__lib__/xod/i2c/begin-transmission
workspace/__lib__/xod/i2c/end-transmission
workspace/__lib__/xod/i2c/read-byte
workspace/__lib__/xod/i2c/request
workspace/__lib__/xod/i2c/write-byte
workspace/__lib__/xod/net/http-get
workspace/__lib__/xod/net/http-post
workspace/__lib__/xod/net/http-request
workspace/__lib__/xod/uart/print
workspace/__lib__/xod/uart/read-byte
workspace/__lib__/xod/uart/read-bytes
workspace/__lib__/xod/uart/write-byte
...

Let’s replace the ERR’s with error raising.

Acceptance criteria

• [x] The patches listed have no ERR pulse outputs
• [x] They raise an error if things go wrong
• [x] Nodes’ or pin descriptions are complemented with mentions about possible errors
• [x] Documentation articles which use the ERR pulses are tweaked accordingly¹
• [x] Tutorial chapters which mention ERR are tweaked accordingly (notably, 104-button)

¹

$ rg ERR -l | xargs -n1 dirname | sort | uniq 
docs/guide/buses
docs/guide/http-get
docs/guide/i2c
docs/guide/rtc-example
docs/guide/sd-log-example
docs/guide/w5500-advanced
docs/guide/w5500-connect
docs/guide/wrapping-arduino-libraries

[brusherru]

I found some classes of errors. So here are error codes that I can propose to use (but not sure about numbers):

• 1 — Invalid port (xod/gpio)
• 2 — Invalid address (xod/i2c)
• 3 — No available bytes to read (xod/i2c, xod/uart, xod/net, xod-dev/esp*, xod-dev/pn532-nfc and etc)
• 4 — No bytes written (the same list)
• 5 — No internet connection (xod/net, xod-dev/esp*, xod-dev/w5500).
• 6 — Can't establish TCP connection (xod/net, xod-dev/esp*, xod-dev/w5500)
• 7 — Wrong hardware connection (xod/common-hardware, xod-dev/pn532-nfc and etc). Probably, can be merged with the first one: "Invalid port"
• 8 — Data too long (xod/i2c)
• 9 — NACK on address transmit (xod/i2c)
• 10 — NACK on data transmit (xod/i2c)
• 11 — Other I2C error (xod/i2c)
• 12 — AT command error (xod-dev/esp8266, probably GPRS shield too etc)
• 13 — No echo (xod/common-hardware/hc-sr04-ultrasonic-time).

Probably we have to group it by classes (i2c, io, gpio, network, devices). And probably some hardware-specific errors should be at "user-land" space. For example, "No echo" error code of the ultrasonic range meter could have a number 101.

Moreover, "No echo" probably is not an error and should be left as an output pulse. The same thing with read-byte. Should it raise an error if there are no available bytes to read, or just pulse to the output pulse "NA" (Not Available)?

Also, the whole error system reminds me of error codes from bash scripts. So, probably, all error codes should be node specific. analog-read can't raise an error about internet connection like the any esp8266-mcu can't raise "Invalid port" error.

@nkrkv @evgenykochetkov @knopki Please, tell me your thoughts about it.