CPE210(UN) V3.2

22 posts / 0 new

Sat, 02/08/2020 - 01:45

vk4kws

CPE210(UN) V3.2

Hi All. Very new here so hope this question hasn't already be asked.
I have some TP LINK CPE210(UN) V3.2 and when I try to install the AREDN firmware I get a Not supported hardware error.
I have tried the nightly builds as well as the stable ones "aredn-3.19.3.0-cpe210-v3-factory.bin"
What am I missing.
Kent
PS I am trying the update from the factory UI

Sat, 02/08/2020 - 14:00

K5DLQ

this is a newer device that

this is a newer device that is supported on the nightly builds.
https://www.arednmesh.org/content/nightly-builds

Sat, 02/08/2020 - 19:59

(Reply to #2) #3

vk4kws

Thanks

Thank you for the response.
I'll give the nightly builds another go. Still no go but I'll try over the next few weeks/months. :)
Kent

Thu, 02/13/2020 - 20:27

(Reply to #3) #4

vk4kws

Still no go :(

Hi All
Nightly build 12-02-2020 still gets the not supported hardware error.
Anyone else been able to change the firmware on V3.2?
Kent

Sat, 02/15/2020 - 15:28

(Reply to #4) #5

AE6XE

Please upload a support data,

Please upload a support data, link on Administration page.
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_config.html#administration

Joe AE6XE

Fri, 02/21/2020 - 22:34

(Reply to #5) #6

vk4kws

Hi Joe,

Hi Joe,
Sorry to be a pain but the attached link, is it a screen shot of the AREDN firmware? I still have the factory firmware on my CPE210.
and can't see the support data link on the system page (no administration page)
I have attached the config.bin.. Is this what you need?
Kent

File Attachment:

The config.bin downloaded from the cpe210

Fri, 02/21/2020 - 23:53

(Reply to #6) #7

AE6XE

Sorry, I originally read this

Sorry, I originally read this too fast and misunderstood. I get it now. I'm not seeing any support for anything but 3.0 versions. Nothing is listed in the code for a 3.1 or a 3.2 version:

.support_list =

"SupportList:\r\n"

"CPE210(TP-LINK|EU|N300-2|45550000):3.0\r\n"

"CPE210(TP-LINK|UN|N300-2|00000000):3.0\r\n"

"CPE210(TP-LINK|UN|N300-2):3.0\r\n"

"CPE210(TP-LINK|EU|N300-2):3.0\r\n",

It might be as simple as adding the strings, but if they changed a flash, RAM, or ethernet, etc. chip, then more changes are necessary. To assess how easy/hard this is, are you able to ssh into the device to get a command line (are you familiar with these commands?)? From a prior forum example, you may have to enable ssh in the Pharos UI somewhere. If you can access, we'd need to capture output from the following commands:

dmesg
cat /proc/cpuinfo
cat /dev/mtdblock2 | grep CPE210

Refer to this prior and similar post: https://www.arednmesh.org/comment/13645#comment-13645

Joe AE6XE

Sat, 02/22/2020 - 01:46

(Reply to #7) #8

vk4kws

I have attached the text

I have attached the text reported back by the CPE for each command. Thank you for your help.
Kent

File Attachment:

tp210V3.2.txt

Sat, 02/22/2020 - 12:31

(Reply to #8) #9

AE6XE

Perfect. Assessing...

Perfect. Assessing... relatively easy to allow the image to be accepted. I'll create this image shortly to try. Then it is a combination of reviewing the data more and testing to discover if this model revision has other hardware changes, or it simply works. I may have more time to create an image today, it is actually raining is SoCal :) .

Joe AE6XE

Sun, 02/23/2020 - 01:02

(Reply to #9) #10

AE6XE

Kent, try this image: https

Kent, try this image: https://drive.google.com/drive/folders/1qUasjByCKLv1-iBjgSdgNC8N9difcCUL?usp=sharing

The device should accept loading this image. Once it is loaded, I need a support data download. It probably still needs some settings to recognize the device for AREDN power settings and channel options.

Joe AE6XE

Sun, 02/23/2020 - 01:25

(Reply to #10) #11

vk4kws

Working now

Hi Joe,
Nice work. The upgrade worked and rebooted ok. I have attached the file you requested and i am about to do a second unit and have a play.
Kent PS. I have updated two units now and so far so good. They talk to each other.

Support File Attachments:

Requested data

Sun, 02/23/2020 - 11:00

(Reply to #11) #12

AE6XE

So far so, good. Looks like

So far so, good. Looks like there may not be any further changes needed. Please try different channels and the highest power setting allowed on each channel. After a reboot, check to see if the power setting showing in basic setting is still the same. We're looking to see if it changed lower. Not all dot versions have allowed the same power output.

Let me know if any issues after taking through the paces with typical use.

Joe AE6XE

Mon, 02/24/2020 - 02:43

(Reply to #12) #13

vk4kws

CPE210V3.2 test

Hi Joe
Home from work now so gave it another try.
Changed to any power setting and rebooted..It didn't keep the power setting. went to 21dbm
I have attached the frequency list in the combo box. It goes back to 2.412 after each reboot..
Thank you so much for your work so far :)
Kent

Image Attachments:

Mon, 02/24/2020 - 22:51

#14

AE6XE

Please try the updated images

Please try the updated images here:

https://drive.google.com/drive/folders/1qUasjByCKLv1-iBjgSdgNC8N9difcCUL...

The channel selections should now work. One more round of support data, to review.

Joe AE6XE

Tue, 02/25/2020 - 02:03

#15

vk4kws

Thanks again Joe

Thanks again Joe
The channel list now shows -2 -1 ect ;) shows highest power level as 21dbm specs say up tp 27dbm
I selected channel -2 and 16dbm after reboot was back on channel 1 and 21dbm
EDIT Scratch that, some dummy didn't press save changes before reboot DOH rebooted keeping the new settings fine.

Kent

Support File Attachments:

support data

Tue, 02/25/2020 - 09:53

(Reply to #15) #16

AE6XE

Tplink shows the max power

Tplink shows the max power across all of the channels. The power is tapper off at the edges. Currently the settings (for all v3.x models) allows:

21 dbm: ch -2, -1, 1
25 dbm: ch 2
18 dbm: ch 3+

I need to understand the max power specs for each of the different 3.0, 3.1, and 3.2 models. If they are different, then a new way of detecting the model needs to be implemented, to set the power.

You can play with the definition by editing the file /www/cgi-bin/perfunc.pm and changing 'chanpower' here. See if it will take, save, and keep a higher power setting on any of the channels. Elsewhere in the vendor firmware settings, there are hardcoded maxes by channel.

'TP-LINK CPE210 v3' => {

'name' => 'TP-LINK CPE210 v3',

'comment' => '',

'supported' => '1',

'maxpower' => '25',

'pwroffset' => '0',

'usechains' => 1,

'rfband' => '2400',

'chanpower' => { 1 => '21', 2 => '25', 11 => '18' },

Joe AE6XE

Wed, 02/26/2020 - 02:34

#17

vk4kws

Thank you Joe.

Thank you Joe. I will have a play and let you know how I go. Kent

Wed, 02/26/2020 - 21:15

(Reply to #17) #18

AE6XE

Kent, all the changes for

Kent, all the changes for this device are in the nightly build images as of today. Recommend upgrading to this new build image.

Joe

Sat, 02/29/2020 - 02:12

#19

vk4kws

Nightly Build

Hi Joe
All working from the nightly build. I restored one to the OME firmware to check power levels and it allows 27dbm on all available channels. :)
I am going to try editing the perfunc.pm file and seeing if I can break it.
Can't thank you enough for your help. I'll send a little donation in to help with on going costs.
Kent

Image Attachments:

Sat, 02/29/2020 - 14:21

(Reply to #19) #20

AE6XE

We've known tplink to have

We've known tplink to have different max power settings for different channels. I suspect the 27 dBm setting may only mean "if it can do 27, otherwise the max it can do". In the support data previously sent, when querying the wireless driver of what settings it can do, we are seeing this:

HT TX/RX MCS rate indexes supported: 0-15

Frequencies:

* 2397 MHz [-2] (25.0 dBm)

* 2402 MHz [-1] (25.0 dBm)

* 2412 MHz [1] (25.0 dBm)

* 2417 MHz [2] (25.0 dBm)

* 2422 MHz [3] (25.0 dBm)

* 2427 MHz [4] (25.0 dBm)

* 2432 MHz [5] (25.0 dBm)

* 2437 MHz [6] (25.0 dBm)

* 2442 MHz [7] (25.0 dBm)

* 2447 MHz [8] (25.0 dBm)

* 2452 MHz [9] (25.0 dBm)

* 2457 MHz [10] (25.0 dBm)

* 2462 MHz [11] (25.0 dBm)

* 2467 MHz [12] (25.0 dBm)

* 2472 MHz [13] (25.0 dBm)

* 2484 MHz [14] (25.0 dBm)

There's still some complexity and mystery, but the thinking to date has been there are hard coded max values by channel stored on the flash as set by vendor. In AREDN firmware, change the max settings in perfunc.pm and see if you can get any channel to to save and keep a setting above 25. If spec says 27dBm and we can confirm it will keep and take that setting on any of the channels, then let's make that a permanent update to the images.

Joe AE6XE

Sun, 03/01/2020 - 01:59

#21

vk4kws

Power level

Thanks Joe
I guess the other thing is if it is real world power output or a random figure they picked :)
I did try one edited firmware and bricked one cpe210 :( I have reinstalled the factory firmware for another try.
My plan now is to compile a standard firmware to make sure it works first then experiment.
Kent

Sun, 11/05/2023 - 20:01

#22

K7XTN

Updated firmware on TP-Link CPE210; getting "unsupported device"

I have a TP-Link CPE210 v3 and tried updating the AREDN firmware via the “Download Firmware” drop down menu on the Administration tab, as directed here: https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_config.html#administration. I was presented with several options in the dropdown and selected what I thought was the most recent build. I wasn't paying close attention, think it was build 3.23.8.0. After it rebooted, I got an !!!! UNSUPPORTED DEVICE !!!! error. I am unable to return to the Setup page to reinstall the prior version of the AREDN firmware.
I tried resetting the router using the reset button (press and hold for 8 seconds, per the router instructions), but that didn't work. I then tried to use the Tiny PXE app to reinstall the AREDN firmware (following the instructions for installing the firmware on Windows: https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installin...) but after I click the "Online" button and power on the router holding down the reset button, I never get the message, TFTPd: DoReadFile: recovery.bin, and instead it say 4:33:05 PM DHCPc:no other DHCPd discovered
This is the second time this has happened with a TP-Link CPE210. The first one I wasn't able to recover and gave to a ham friend to try to recover and have yet to hear back from him. Any idea what's up? And any suggestions about what to try? Thanks very much!

Amateur Radio Emergency Data Network

Menu SF

You are here

CPE210(UN) V3.2

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

CPE210(UN) V3.2