Maybe wait till it stops synching and see if it starts mining, CPU might be overloaded
Thanks! I'll also inspect the wiring harness for any wires that may have disconnected or snapped during shipment--another user suggested that.
Weeeeeell...same issue. I stopped the node (thus removing the load on CPU) and restarted the miner(s). No change--solid red light on FULL but STANDARD hashes away in Eco fine.
Will wait for blockchain to fully sync (90% currently) and retry all the rebooting steps.
I can't see any loose wires or anything, so if there's no progress after full sync, I guess it'll have to be returned and swapped out for a new FULL?
You did not follow my advice.
I suggested leaving the full unit alone, do not connect anything to it.
Just put full unit on the table, freshly flashed SD card, connect power and Internet, configure pool, wait for node to start syncing and miner to start mining. Its not mining? Its damaged and you must RMA, or investigate this unit until you find the fault. Leave standard unit out if this troubleshooting procedure, your standard USB miner is fully operational.
Well of course not, since I posted at "September 21, 2022, 12:52:46 PM" and replies to my post do not include yours.
I've investigated the unit. What my troubleshooting HAS shown might be helpful to others--as I stated in my post moving the SBC from one miner to the other did two things...
1) caused the miner it is installed in to also NOT mine
2) show a significant HW error rate of the miner that it had been installed in
So, if I were a dev or working on the HW side, I'd be VERY VERY curious why my product was disintegrating itself.
Miner 1 (original FULL) did not hash and originally held the SBC
Miner 2 (original STANDARD) did hash but now when hosting the SBC does not hash, all the while Miner 1 is now hashing but averaging a HUGE hardware error rate
This might be an example of what happens when QC is extended to your buyers and not fully done in house?