Bitcoin Forum
October 13, 2024, 02:44:30 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Avalon Nano 3 Loses Network Connection  (Read 143 times)
Haitian69 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 26, 2024, 05:02:40 PM
 #1

At least once a day the Avalon Nano 3 loses network connection for a few minutes.  The power is on, it does not reboot, it just loses network connection.  This has occurred on the High and medium mode.
See the constant ping I have running.
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=29ms TTL=64
Reply from 10.204.221.63: bytes=32 time=4ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=4ms TTL=64
Reply from 10.204.221.63: bytes=32 time=4ms TTL=64
Reply from 10.204.221.63: bytes=32 time=5ms TTL=64
Reply from 10.204.221.63: bytes=32 time=26ms TTL=64
Reply from 10.204.221.63: bytes=32 time=3ms TTL=64
Reply from 10.204.221.63: bytes=32 time=49ms TTL=64
Reply from 10.204.221.63: bytes=32 time=3ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=69ms TTL=64
Reply from 10.204.221.63: bytes=32 time=15ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=91ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=4ms TTL=64
Reply from 10.204.221.63: bytes=32 time=15ms TTL=64
Reply from 10.204.221.63: bytes=32 time=88ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=18ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=27ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=70ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=59ms TTL=64
Reply from 10.204.221.63: bytes=32 time=3ms TTL=64
Reply from 10.204.221.63: bytes=32 time=61ms TTL=64
Reply from 10.204.221.63: bytes=32 time=7ms TTL=64
Reply from 10.204.221.63: bytes=32 time=84ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Request timed out.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.62: Destination host unreachable.
Reply from 10.204.221.63: bytes=32 time=1170ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=87ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=4ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=3ms TTL=64
Reply from 10.204.221.63: bytes=32 time=3ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=51ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
Reply from 10.204.221.63: bytes=32 time=70ms TTL=64
Reply from 10.204.221.63: bytes=32 time=2ms TTL=64
BitMaxz
Legendary
*
Offline Offline

Activity: 3402
Merit: 3146

Is the $100k BTC possible?


View Profile WWW
August 26, 2024, 05:45:44 PM
 #2

This unit currently has an issue related to login credentials maybe someone is trying to hack your unit and steal your hash rate.

Would you mind to try to factory reset the unit you can find the guide from this link below.

- https://bitcointalk.org/index.php?topic=5480799.msg64304278#msg64304278

According to some post from that link canaan will release new firmware for this unit on December that's a long time to wait but try to factory reset the unit and try to reboot the internet router.

BTC Road to $80k...
NotFuzzyWarm
Legendary
*
Offline Offline

Activity: 3780
Merit: 2689


Evil beware: We have waffles!


View Profile
August 26, 2024, 05:48:07 PM
Merited by BitMaxz (1)
 #3

Please edit that using the code tag #. It makes that text wall into a scrollable box that's much easier to deal with...
My guess would be that you have a poor signal. How far away from the router is the miner? Anything metal between them like a filing cabinet? This BTW is exactly why having only a WiFi link and no LAN port was a bad idea...

- For bitcoin to succeed the community must police itself -    My info useful? Donations welcome!  3NtFuzyWREGoDHWeMczeJzxFZpiLAFJXYr
 -Sole remaining active Primary developer of cgminer, Kano's repo is here
-Support Sidehacks miner development. Donations to:   1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Haitian69 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 28, 2024, 10:52:48 AM
 #4

The miner is next to the router, about 2 inches apart.
I have a constant ping going to the router at the same time as the miner, and when the miner loses network connection, the ping replies to the router are fine.
I will try the factory reset to see if that helps.
Danzotron
Newbie
*
Offline Offline

Activity: 5
Merit: 1


View Profile
August 29, 2024, 03:31:40 PM
 #5

What power supply are you using?
ya5on
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
September 03, 2024, 07:29:08 AM
Last edit: September 14, 2024, 07:52:14 AM by ya5on
 #6

At least once a day the Avalon Nano 3 loses network connection for a few minutes.  The power is on, it does not reboot, it just loses network connection.  This has occurred on the High and medium mode.
See the constant ping I have running.

It's related, but add another problem: Avalon Nano 3 never manages to re-connect to last net after rebooting/restart (User Experiences wanted!)

I have to go through the complete first time init-net setup EVERY TIME a restart/reboot of the Avalon Nano 3 is needed/has happened? It just doesn't want to reconnect after being "offline" (has static IP)

So for every change to config that demand a reboot it will NOT find/reconnect to that the last network,  hence it demands a repeat of initial startup procedure (ie.finding network 'Avalon_nanoA51F' > 192.168.168.168 > Find Wifi, enter correct password)

So simple stask like wanting to change pools is a BIG HASSLE now: Cannot be done without having to go through init-setup every time (- and that is ....ridiculous! if this is the normal procedure: Anyone w/ similar experiences?)

PS. Many question type of poweradaptor, I have the USAMS (specs below: 140W 28V:5A)  that mines fine on 'High' for over +24 hrs, then: As I write over... So it cannot be the powerproblem as either the adapter would have shut off long before or the AN3 would have refused to mine at LVL 'High'

Firmware Version: 24071801_42c628d

POWERSUPPLY: USAMS Modell: US-CC168 / USAMS T52 140W ACC GaN Fast Charger (EU) + US-SJ581 / U82 Type-C to Type-C 240W PD3.1 Fast Charging & Data Cable USB-C1 Output: 5V:3A, 9V:3A, 12V:3A, 15V:3A, 20V:5A, 28V:5A (140W Max) (for instance here: https://lysiq.se/usams-us-um-gan-snabbladdare-140w-2m-usb-c-kabel-2x-usb-c-1x-usb-a-kit/)
whoismeanyway
Newbie
*
Offline Offline

Activity: 23
Merit: 1


View Profile WWW
October 10, 2024, 05:15:39 PM
 #7

If you are not using the official Canaan or the Lenovo adapter, then theres the problem.
NotFuzzyWarm
Legendary
*
Offline Offline

Activity: 3780
Merit: 2689


Evil beware: We have waffles!


View Profile
October 10, 2024, 07:23:32 PM
Last edit: October 11, 2024, 01:06:21 AM by NotFuzzyWarm
Merited by philipma1957 (3), BitMaxz (1)
 #8

If you are not using the official Canaan or the Lenovo adapter, then theres the problem.
Partly right - the PSU itself is fine - capable of the needed voltage and current. However, USB-C PD3.1 requires a cable that matches the power you are using. The PD cables have a chip in them that tells the PSU & device being powered how much power it can deliver. Anything over 65w MUST use a PD cable and the cable is required to have a label that tells you what it is good for. For example https://www.amazon.com/ULT-WIIQ-Charging-Transfer-Monitor-Samsung/dp/B0D3HLPNKT

Did the PSU come with a 240w or a 165w PD cable? If not, are you using a regular USB-C cable - if so that is the problem.

- For bitcoin to succeed the community must police itself -    My info useful? Donations welcome!  3NtFuzyWREGoDHWeMczeJzxFZpiLAFJXYr
 -Sole remaining active Primary developer of cgminer, Kano's repo is here
-Support Sidehacks miner development. Donations to:   1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!