From 20ddf03dcf4d2c7c5fb5c6c6bd13134b0431336b Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Mon, 2 Oct 2023 14:52:37 +0200 Subject: [PATCH] titles instead --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a6bcf60..396c582 100644 --- a/README.md +++ b/README.md @@ -9,9 +9,10 @@ WPJ428 + SIMCOM 8202G **We see this project as a way to assess how well we can regain control/understanding on our NR5G/LTE routers.** *And for now the answer seems to be "very little"*. ---- -⛔✋ THIS IS NOT AN HOW-TO GUIDE. During the process, it appears we made major mistakes. Because we had +## ⛔✋ THIS IS NOT AN HOW-TO GUIDE. + +During the process, it appears we made major mistakes. Because we had already bought the components, it was too late and had to live with them or find workarounds. But for a new build, it is advised to choose better components. Here are our major errors, that can be summarized as "the cost of trying to be on the edge": - The M.2 port of the board is only wired for the USB protocol 2.0 (and not USB 3.0 or PCI Express). The link is very slow and is probably @@ -27,7 +28,8 @@ pluggable modems where only at the beggining and we paid the "early adopter" tax In the end, we bought very expensive components to get only very mediocre performances (only 10Mbps while LTE alone supports up to 100Mbps). Buying a NR5G modem was clearly a waste of money. ---- + +## Our research & experiment process Our case study is a NR5G router as the main Internet access point in a place where we have no signal on our cellphones. Thus, we need external antennas that are put in the roof.