Posts made by evb

evb

I searched the forum on maximum distances, but didn't find much information about it.
I know that distances can be influenced by concrete walls, steel, …, but what are the average distances you are getting with this radio RFM69HW?

evb

This post is a try to order my thoughts about the mysensors implementation possibilities for signing and encryption.

I thought that it could be of some help for other people, who are new, like me, to mysensors and want to start using it.
This is written with in mind the current version 2.3.1 of the mysensors libary and 2 Arduinos Uno's R3 as hardware. Be aware that this can change in the future as the library will continue to evolve!

Please, if you find any mistakes, don't hesitate to point them out to me so I can correct this post.

First some (condensed) theory found in the docs and on this forum.

Two different things:

Signing messages : this makes that the receiver is sure that the received message is really from the transmitter. The message can't be changed by somebody during the transmission of the message. This is done by the MySensors message protocol.
More detailed explication can be found on: https://www.mysensors.org/apidocs/group__MySigninggrpPub.html#MySigninggrpencryption
Encryption of the messages: is done on the level of the used radio itself. For RFM69HW for example, it is done by the hardware itself of the radio. It is independent from the MySensors message protocol implementation.

A. Signing of the messages

Three possibilities: 2 based on software and one based on extra external hardware. The latest I can't test because I have no Atmel ATSHA204 chips lying around...

First option, software backed by using only a password : weaker security, but simple to activate.

MY_SIGNING_SIMPLE_PASSWORD: this keyword enables security only on the level signing
If the provided password is shorter than the size of the HMAC key, it will be null-padded to accommodate the key size in question. A 32 character password is the maximum length. Any password longer than that will be truncated.
Second option, sofware backed

MY_SIGNING_SOFT: this keyword enables security only on the level signing

If MY_SIGNING_SIMPLE_PASSWD is used a personalisation must not be done.
If not used, a personalization must be done, the values are stored in EEPROM.(see: https://www.mysensors.org/apidocs-beta/group__MySigninggrpPub.html#personalization). See also further on.
Third option, hardware backed via the Atmel ATSHA204 chip

MY_SIGNING_ATSHA204: this keyword enables security only on the level signing

If MY_SIGNING_SIMPLE_PASSWD is used a personalisation must not be done.
If not used, a personalization must be done, the values are written to the Atmel ATSHA204 ship. It is irreversible!! (see https://www.mysensors.org/apidocs-beta/group__MySigninggrpPub.html#personalization)

B. Encryption of the radio transport level

Only possible for the supported radios (RF24, RFM69, NRF5, RFM95 at current library version 2.3.1)(https://www.mysensors.org/apidocs-beta/group__EncryptionSettingGrpPub.html)
The RFM69 radio does support hardware encryption of the communication using AES (Advanced Encryption Standard).

MY_ENCRYPTION_SIMPLE_PASSWORD: this keyword enables encryption on all radio communications of the radio types that supports it and uses provided password as key.
If the provided password is shorter than the size of the AES key, it will be null-padded to accommodate the key size in question. A 16 character password is the maximum length. Any password longer than that will be truncated.
example : #define MY_ENCRYPTION_SIMPLE_PASSWD "MyInsecurePassword"

If you are already using the first option of signing messages (MY_SIGNING_SIMPLE_PASSWORD), you can replace it by following keyword:

MY_SECURITY_SIMPLE_PASSWORD: this keyword enables security on the level signing and encryption (only usable on Arduino. On the Raspberry PI use the other two simple options)

My practical tests

a sensor based on an Arduino Uno with the sketch UltraSonic_sensor from the website adapted for the RFM69HW radio
a gateway based on an Arduino, a W5100 ethernet shield for the Uno and a radio RFM69HW (see https://forum.mysensors.org/topic/10358/solved-mqtt-gateway-based-on-arduino-uno-uno-compatible-w5100-ethernet-shield-rfm69hw-radio)

Added in the two sketches: only encryption

#define MY_ENCRYPTION_SIMPLE_PASSWORD "my16characterpassword"

Result : it works

Added in the two sketches: encryption and simple signing

#define MY_ENCRYPTION_SIMPLE_PASSWORD "my16characterpassword"
#define MY_SIGNING_SIMPLE_PASSWORD "my32characterpassword"

Result : warning when downloading the code into the gateway: "Low memory available, stability problems may occur."
It doesn't work!

Added in the two sketches: encryption and simple signing

#define MY_ENCRYPTION_SIMPLE_PASSWORD "my16characterpassword"
#define MY_SIGNING_SIMPLE_PASSWORD "my16characterpassword"

Result : warning when downloading the code into the gateway: "Low memory available, stability problems may occur."
It doesn't work!

Added in the two sketches: the shortcut define for the Arduino platform

#define MY_SECURITY_SIMPLE_PASSWORD "my16characterpassword"

Result : it works

Added in the two sketches: the shortcut define for the Arduino platform

#define MY_SECURITY_SIMPLE_PASSWORD "my32characterpassword"

Result : it works

Is this shortcut define specially done for the Arduino platform to avoid the low memory condition?

Added in the two sketches : encryption and soft signing with simple password personalization

//enable radio communication encryption
#define MY_ENCRYPTION_SIMPLE_PASSWD "my16characterpassword"
#define MY_SIGNING_SIMPLE_PASSWD "my32characterpassword"
#define MY_SIGNING_SOFT
#define MY_SIGNING_REQUEST_SIGNATURES
#define MY_SIGNING_SOFT_RANDOMSEED_PIN A0

Result : warning when downloading the code into the gateway: "Low memory available, stability problems may occur."
It doesn't work. The signing is failing.

Added in the two sketches : encryption and soft signing with personalization
First we will personalize each arduino (the sensor and the gateway)

open the SecurityPersonalizer.ino file via the Arduino IDE menu File, Examples, Mysensors, SecurityPersonalizer
uncomment the define GENERATE_KEYS_SOFT
upload the sketch to your Arduino
open the serial monitor
here you will find your generated keys HMAC and AES keys
copy the entries under the 'Key copy section' into the SecurityPersonalizer.ino file
comment again the define GENERATE_KEYS_SOFT

The following 3 steps must be done on each node where you want to use soft signing

uncomment the define PERSONALIZE_SOFT
upload the sketch again to your Arduino
in the serial monitor output you will find now that the keys are written to the EEPROM (see EEPROM section)

The following 5 steps must also be done on each node where you want to use whitelisting

if you want to use whitelisting and your device does not provide a unique device ID, you have to generate a unique serial and store it in EEPROM (my arduino uno does not provide a unique device ID, so I must run the sketch)
comment the define PERSONALIZE_SOFT
uncomment the define PERSONALIZE_SOFT_RANDOM_SERIAL
upload the sketch to your Arduino
in the serial monitor output you will find now a generated serial unique device ID. This unique serial ID must be copied somewhere on a safe place. You must later on copy this key in the whitelisting define of your gateway and nodes sketches.

Take now your sketches and add the following defines

//enable radio communication encryption
#define MY_ENCRYPTION_SIMPLE_PASSWD "my16characterpassword"
//enable soft signing
#define MY_SIGNING_SOFT
#define MY_SIGNING_REQUEST_SIGNATURES
#define MY_SIGNING_SOFT_RANDOMSEED_PIN A0
#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = 0,.serial = {0x11,0x22,0x33,0x44,0x55,0x66,0x77,0x88,0x99}},{.nodeId = 1,.serial = {0x99,0x88,0x77,0x66,0x55,0x44,0x33,0x22,0x11}}}

The MQTT gateway has always nodeid = 0 and my sensor has nodeid = 1 (the sensors must have a fixed set nodeid because in MQTT mode, the controller (like HomeAssistant) can't assign node ids).
The serials given above are fake numbers, use the ones from your sketch!

Result : warning when downloading the code into the gateway: "Low memory available, stability problems may occur."
It doesn't work!

So I think that in my case, with an Arduino Uno as MQTT gateway, only the simple signing and encryption is possible.
Maybe the hardware backed signing, but I can't test this at this moment. (see my other question : https://forum.mysensors.org/topic/10370/is-there-still-a-breakout-board-for-the-atmel-atsha204a-chip)

evb

Hi,

Was searching how to implement the Atmel ATSHA204A chip as a signing hardware device in the gateway and the sensor nodes.
Found the chip on AliExpress quickly, but it is only available as smd component, so was searching for a breakout board.
There was once a breakout board done by Sparkfun, but it isn't made anymore (https://www.sparkfun.com/products/retired/11551)

Searching with our friend Google did not reveal any other manufacturers

Does someone knows about a breakout board for this chip?
Or is my only choice to use these little smd component ?

evb

Nobody has never build a gateway based on an Arduino Uno, a W5100 shield and a RFM69HW?

So I will answer my own questions
I did take my chance and choose to build first a gateway version using the hardware SPI bus (no soft spi) and I was lucky, it worked directly! So no need to try the soft-spi version.

Because I did already build previously a sensor (https://www.mysensors.org/build/distance), I had all hardware already ready to be used.

So what is the used hardware?

one standard Arduino Uno R3 (guine or chinese clone, DON'T BUY WAVGAT arduino uno types, they require specific hardware drivers in the Arduino IDE and this manufacturer doesn't update his own old drivers!!)(https://www.aliexpress.com/item/1pcs-Smart-Electronics-high-quality-UNO-R3-MEGA328P-CH340G-Compatible-NO-USB-CABLE-for-arduino/32830661533.html)
one RFM69HW, version 868MHz (check what you can use at your country!)(https://www.aliexpress.com/item/Free-Shipping-RFM69HW-868Mhz-Transceiver-Module-High-Integrated-HopeRF-Wireless-868S2-Module-SPI-1-8-3/32810316806.html)
one helical antenna (https://www.aliexpress.com/item/10PCS-868MHz-Helical-Antenna-2-15dBi-13mm-Stable-for-Remote-Contorl/32668155368.html)
one W5100 shield pin compatible with an Arduino Uno (https://www.aliexpress.com/item/Free-Shipping-UNO-Shield-Ethernet-Shield-W5100-R3-UNO-Mega-2560-1280-328-UNR-R3-only/32502588687.html)
one proto shield to build the RFM69HW radio on top of the W5100 shield (https://www.aliexpress.com/item/Standard-Proto-Screw-Shield-Board-For-Arduino-Compatible-Improved-version-support-A6-A7-Diy-Kit-Electronic/32832054800.html)
one logic channel convertor between Arduino 5V and RFM69HW radio 3.3V (https://www.aliexpress.com/item/3-3V-5V-TXS0108E-8-Channel-Logic-Level-Bi-directional-Converter-Module-TXB0108-Mutual-Convert-Module/32916020205.html)

The hardware is wired following next schematic:
0_1556974214950_Arduino Uno Ethernet Gateway.png

Connecting the RFM69HW hardware was somewhat tricky. The used pin headers on the RFM69HW are not following the standard spaced 2.54mm pin headers like on the Arduino print. I did not have a converter plate, so I soldered some hard wire into the RFM69HW pins and bend them into the pin holes from the protoboard. See photo.

So what about the software:

Arduino IDE version 1.8.9
MySensors library 2.3.1

I did take as base the sketch found on the website https://www.mysensors.org/build/mqtt_gateway or https://github.com/mysensors/MySensors/blob/master/examples/GatewayW5100MQTTClient/GatewayW5100MQTTClient.ino

Important is to configure the specific RFM69 defines
#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RFM69_868MHZ // Set your frequency here
#define MY_IS_RFM69HW // Omit if your RFM is not "H"
#define MY_RFM69_NEW_DRIVER

When the W5100 Arduino shield is connected we have to move SS (slave select) pin for the RFM69 radio because the shield is using the default D10
#define MY_RFM69_CS_PIN 6

/*
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
 * Copyright (C) 2013-2019 Sensnology AB
 * Full contributor list: https://github.com/mysensors/MySensors/graphs/contributors
 *
 * Documentation: http://www.mysensors.org
 * Support Forum: http://forum.mysensors.org
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * version 2 as published by the Free Software Foundation.
 *
 *******************************
 *
 * REVISION HISTORY
 * Version 1.0 - Henrik Ekblad
 * Version 1.1 - Eric Van Bocxlaer
 *
 * DESCRIPTION
 * The W5100 MQTT gateway sends radio network (or locally attached sensors) data to your MQTT broker.
 * The node also listens to MY_MQTT_TOPIC_PREFIX and sends out those messages to the radio network
 *
 * LED purposes:
 * - To use the feature, uncomment WITH_LEDS_BLINKING in MyConfig.h
 * - RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received
 * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
 * - ERR (red) - fast blink on error during transmission error or receive crc error
 *
 * See http://www.mysensors.org/build/esp8266_gateway for wiring instructions.
 * nRF24L01+  ESP8266
 * VCC        VCC
 * CE         GPIO4
 * CSN/CS     GPIO15
 * SCK        GPIO14
 * MISO       GPIO12
 * MOSI       GPIO13
 *
 * Not all ESP8266 modules have all pins available on their external interface.
 * This code has been tested on an ESP-12 module.
 * The ESP8266 requires a certain pin configuration to download code, and another one to run code:
 * - Connect REST (reset) via 10K pullup resistor to VCC, and via switch to GND ('reset switch')
 * - Connect GPIO15 via 10K pulldown resistor to GND
 * - Connect CH_PD via 10K resistor to VCC
 * - Connect GPIO2 via 10K resistor to VCC
 * - Connect GPIO0 via 10K resistor to VCC, and via switch to GND ('bootload switch')
 *
  * Inclusion mode button:
 * - Connect GPIO5 via switch to GND ('inclusion switch')
 *
 * Hardware SHA204 signing is currently not supported!
 *
 * Make sure to fill in your ssid and WiFi password below for ssid & pass.
 * 
 * ***************************************************************************************************************
 * Connection with RFM69HW and EthernetShieldW5100 through the SPI bus (Serial Peripheral Interface)
 * On this bus we can have only one master (= the Arduino Uno) and different slaves (= the W5100 and the RFM69HW).
 * The master can only talk to one slave each time!
 * 
 * RFM69HW    Uno R3    EthernetShieldW5100(autowired)
 * VCC 3.3V   VCC 3.3V  
 *            VCC 5.0V  VCC 5.0V
 * DIO0       D2/INT0
 * NSS        D6
 * SCK        D13/SCK   SCK (D13)
 * MISO       D12/MISO  MISO (D12)
 * MOSI       D11/MOSI  MOSI (D11)
 *            D4        SS (sd-card)
 *            D10/SS    SS (W5100)(Default in ethernet library: do not wire different with a no shield version!)
 *            
 * 
 * NSS/SS : Slave Select for SPI bus (the master selects with which slave he want to talk)
 * SCK : serial clock signal delivered by the master
 * MISO : Master Input Slave Output (arduino receives data from the slave)
 * MOSI : Master Output Slave Input (arduino sends data to the slave)
 */


// Enable debug prints to serial monitor
//#define MY_DEBUG
// Enable specific RFM69 debug prints to serial monitor
//#define MY_DEBUG_VERBOSE_RFM69

// Enables and select radio type (if attached)
//#define MY_RADIO_RF24
//#define MY_RADIO_RFM95
#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RFM69_868MHZ // Set your frequency here
#define MY_IS_RFM69HW // Omit if your RFM is not "H"
#define MY_RFM69_NEW_DRIVER

#define MY_GATEWAY_MQTT_CLIENT

// Set this node's subscribe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"

// Set MQTT client id
#define MY_MQTT_CLIENT_ID "mysensors-1"

// Enable gateway ethernet module type : not needed here because MY_GATEWAY_MQTT_CLIENT defines already the use of W5100
//#define MY_GATEWAY_W5100
#define SD_SS_PIN (4)  // chip-select for SD card (normally unused, pull high!, see code!) 

// W5100 Ethernet module SPI enable (this setting is optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4

// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
// Situation on 2019-05-04: with the new RFM69HW driver this is not true anymore for a radio RFM69!
//#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
//#define MY_SOFTSPI
//#define MY_SOFT_SPI_SCK_PIN 14
//#define MY_SOFT_SPI_MISO_PIN 16
//#define MY_SOFT_SPI_MOSI_PIN 15
//#endif

// When W5100 shield is connected we have to move SS (slave select) pin for the RFM69 radio because the shield
// is using the default D10
#define MY_RFM69_CS_PIN 6

// When W5100 is connected we have to move CE/CSN pins for NRF radio
//#ifndef MY_RF24_CE_PIN
//#define MY_RF24_CE_PIN 5
//#endif
//#ifndef MY_RF24_CS_PIN
//#define MY_RF24_CS_PIN 6
//#endif

// Enable these if your MQTT broker requires username/password
//#define MY_MQTT_USER "username"
//#define MY_MQTT_PASSWORD "password"

// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
//#define MY_IP_ADDRESS 192,168,178,87

// If using static ip you can define Gateway and Subnet address as well
//#define MY_IP_GATEWAY_ADDRESS 192,168,178,1
//#define MY_IP_SUBNET_ADDRESS 255,255,255,0

// MQTT broker ip address or url. Define one or the other.
//#define MY_CONTROLLER_URL_ADDRESS "m20.cloudmqtt.com"
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68

// The MQTT broker port to to open
// With simple arduino uno's we can't use encrypted communication!
#define MY_PORT 1883

/*
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN  3

// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 16  // Error led pin
//#define MY_DEFAULT_RX_LED_PIN  16  // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN  16  // the PCB, on board LED
*/

#include <Ethernet.h>
#include <MySensors.h>

void before() {
    pinMode(SD_SS_PIN, OUTPUT);
    digitalWrite(SD_SS_PIN, HIGH); 
}

void setup()
{
    // Setup locally attached sensors
}

void presentation()
{
    // Present locally attached sensors here
}

void loop()
{
    // Send locally attached sensors data here
}

I hope that this will be helpful for some people trying to build something equivalent

Free Shipping RFM69HW 868Mhz Transceiver Module High Integrated HopeRF Wireless 868S2 Module SPI 1.8-3.6V DC 0-800M Distance

$1.98

10PCS/Lot 868MHz Helical Antenna 2.15 dBi 13 mm Stable for Remote Control

$1.47

UNO Shield Ethernet Shield W5100 R3 UNO Mega 2560 1280 328 UNR R3 only W5100 Development board FOR WAVGAT

$5.29

Standard Proto Screw Shield Board For Arduino Compatible Improved version support A6 A7 Diy Kit Electronic PCB Board Module

$0.73

3.3V 5V TXS0108E 8 Channel Logic Level Bi-directional Converter Module TXB0108 Mutual Convert Module TXS0108

$0.52

evb

Hi Folks,

I'm new to MySensors, so before beginning building things, I read the docs, search the forum, etc., to be able to form me an idea how to start.

First taking the docs: https://www.mysensors.org/build/ethernet_gateway and https://www.mysensors.org/build/mqtt_gateway

The MQTT gateway is based on the ethernet gateway, so we are starting there.
The recommandation is to use a W5100 Ethernet module. This module has problems sharing SPI with the radio, so it is proposed to use soft-spi for the radio.
The W5100 ethernet shield module is hardware wired:

The radio should then be wired for soft-spi following the docs.
Because there is no example for a RFM69HW, I imagine that we must follow the same schematic as for the NRF24L01 radio.

The given sketch is based on the use of a NRF24L01 radio, so when searching for the correct settings for RFM69HW in the forum, I stumbled on plenty of topics of people trying to build the same thing.
Some topics are already several years old, speaking about changing core ethernet libraries for the W5100 to disable the interrupts, others are building on forks of MySensors, forks of RFM69 library, etc.
I saw also a remark in a topic that for using soft-spi, we should use the new RFM69 driver in the MySensors lib.
In one of the topics with an own fork, was mentioned that, because the transactions in SPI where now supported in the RFM69 library, we can now wire also the RFM69HW radio to the same ports on the Arduino as the ethernet module.

So, when reading all these topics, I did loose my view on the things :
With the current version of the MySensors library (2.3.1)

must we use soft-spi like mentioned in the docs or hardware spi like found in topics on the forum?
https://forum.mysensors.org/topic/5109/solved-rfm69-based-nodes-unable-to-report-lib-version/45 : Are these forks now included into the main branch of MySensors?

evb

I don't think they are fake otherwise they won't do anything.
They work with normal sketches, even used several MySensors sketch examples, running without any problem, provided that I don't include the <MySensors.h> line.

Because the board does need his own files to work in the Arduino IDE, the used Atmega clone is too different from the normal line of Atmega's (clones).
Searching on Google revealed that probably this board is using a LogicGreen LGT8Fx8 chip instead of an ATMega328P.
(https://forum.arduino.cc/index.php?topic=560692.0)
When I go into the folders of the specific driver files for the IDE, I see folders with names like lgt8f88a, etc...

Meanwhile, I tested the setup with another Chinese brand of an Arduino clone. These clones don't need specific drivers files, you can just use the Aduino Genuino board. Everything is working.

It is just challenging if I could make it work with these WavGat brand of so-named Arduino uno's.

evb

Hi,

Did use for several projects already clone Arduino's from AliExpress without any problems regarding the compatibility with the Arduino main stream.
For the last order, I didn't look very closely to the brand of the clone, finding me know with some problems.
I ordered some WavGat Arduino uno boards (https://www.aliexpress.com/item/high-quality-One-set-UNO-R3-CH340G-MEGA328P-for-Arduino-UNO-R3-USB-CABLE-ATMEGA328P-AU/32810623079.html)
If I can believe the information given, they are using an ATMEGA328P clone as processor.

After some tweaking of the specific WavGat Arduino drivers (they are not really maintained by the manufacturer to follow the new Arduino 1.8.x branch ), I could compile the sketches without errors.

The blinking led sketchs worked without any problem. The next step was an example of MySensors, drivers, AltSoftSerial, the serial monitor is outputting data (example uses 9600 baud). So far, so good.

The next example was a distance sensor (example from the site): result was garbage in the serial monitor.
I activated MY_DEBUG, same result, garbage in the serial monitor.
Tested at several bauds : 300, 2400, 9600, … : all same result, garbage.
The same script works like a charm on a real Arduino board, so it is not a programming error in the sketch.

So for testing, I created a minimum script with only a serial print "hello world". Works! No garbage in the serial monitor.
Started to add the first lines specific for MySensors

#define MY_DEBUG
#define MY_RADIO_RFM69
#define MY_BAUD_RATE (9600ul)

#include <SPI.h>
#include <MySensors.h>

void setup() {
// put your setup code here, to run once:
Serial.begin(9600);
}

void loop() {
// put your main code here, to run repeatedly:
Serial.print("hello world");
Serial.println();
}

When adding the #include <MySensors.h>, the serial monitor begins with outputting garbage.

So it is clearly that somewhere in the MySensors library something happens to produce this.
Very probably it is due to the no 100% compatibility of the WavGat Arduino.

The problem: where to begin the debug?
I searched the site, but till now, didn't find any information to guide me in the correct direction.

WAVGAT high quality One set UNO R3 (CH340G) MEGA328P for Arduino UNO R3 + USB CABLE ATMEGA328P-AU Development board

$0.89

evb

@evb