 Show Posts
|
|
Pages: [1]
|
|
I just received a shipment of Antminer X3's. I configured them to Antpool and they seem to be turning in work, but AntPool is not reporting the work.
Has anyone else had success setting them up?
Will the X3's work on XMR or do we need to collect XMC and just hope they eventually get listed on an Exchange or Marketplace?
Any current feedback would be greatly appreciated.
|
|
|
|
|
Is this the wrong forum for this message? Where else should I post it?
|
|
|
|
|
I found a calculation to determine the number of BitCoins earned per hash:
=(86400*Hash*25)/(2^32*Difficulty)
86400 = Seconds in a Day
25 = Bitcoins in a block
2^32 = Shares to find a block
How do I apply this formula to another coin?
Do all coins list the number of shares to find a block?
How does inventor of an alternate coin normally list the number of shares to find a block?
Do all coins list the number of coins per block or do I need to find a block to determine it?
Where is difficulty normally listed for a coin?
Does this formula change when applied to Scrypt coins or other algorithm coins?
Thanks in advance for your assistance,
Sitaga
|
|
|
|
|
Ahh. but I didn't switch PSUs.. just the break (plug) in my house. Even stranger, huh?
|
|
|
|
|
No, I haven't slid it apart - but everything is working good now that I moved power. Still have 32ghs each.
|
|
|
|
|
Some news to report. All the Xs are gone (even the original single X from the beginning).
All I did was run an extension cord to the cube from a different circuit in the house (about 20' away). Previously it was connect to a battery backup (surge side) that my computer uses.
Its now hashing at 32GH/s in Low. I haven't tried High yet.
The status light still blinks whenever and however it wants, but o'well.
|
|
|
|
No manual included..  |
|
|
|
|
I've sent them a message as well. No reply so far, but I'm sure they will get back to me. Been good on all other purchases in the past. Thanks!
I don't want to open the case and re-seat until after I talk to them.
|
|
|
|
|
Do X's in the cube web console mean the chip is bad?
When I first got the unit there was only 1 X on the last blade listed (M_81-96), now there are 8 new Xs on M_65-80. Does this indicate that I need a blade (or the entire cube) replaced?
What does the red "Status" led indicate? I have two cubes - both have this status light blinking irradically, however they both seem to blink at the same time.
Thanks for the help!
Sitaga
|
|
|
|
|
Is there anyone that can help with this issue?
|
|
|
|
|
ok - thanks. I also have webEx - so I could let them direct me to places, but stay in control.
|
|
|
|
|
Re-Post from Newbie section:
Firstly, I searched every article I could on this forum and couldn't find a solution. I then spoke for hours in Slush's IRC chat to no avail.
After hours of troubleshooting I'm still having the same problem, though I have a lot more detail on what is happening. In a nutshell the blades continuously switch between the listed Server Addresses.
I have Slush's mining_proxy.exe configured on two local computers - both desktops, both configured not to Sleep.
Total MHS: 05121
Received: 0000062580
Accepted: 0000040226
Per Minute: 070.82
Efficiency: 064.27%
Up Time: 0d,09h,28m,00s
Current Server: 10.1.10.11:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
IP: 10.1.10.54
Mask: 255.255.255.0
Gateway: 10.1.10.1
WEB Port: 80
Primary DNS: 10.1.10.1
Secondary DNS: 10.1.10.1
Ports : 8332,8332
Server addresses : 10.1.10.11,10.1.10.10
user:pass : Any.worker1:xxxxxx,Any.worker1:xxxxxx
I have 10 blades on a backplane with an HP ATSN 7001044-Y000 979124-001 Power Supply, all of them act identical. They act the same weather I have 1 blade connected to the backplane or all 10.
I have tested switching out the proxy for 32bit bfgminer, linux bfgminer on a BBB, and different proxy software on each computer.
The voltage reads 12.81v, however I have not tested amperage as I'm not familiar enough with electricity to tinker that deep.
The blades to NOT restart - they just switch between the two servers (proxies) and remain around 5000 mh/s.
If I configure the blades with the same server separated by commas (e.g. 10.1.10.11,10.1.10.11), the blades will continuously reset after just over 2 minutes.
Happy to start up a Team Viewer Session if anyone is interested in poking around.
Many thanks to dmelvin, minigpenguin, MoonCat, bitguy, urgodfather, and honkeylips for helping me get this far.
New Info: I appears that one of the proxy servers does in fact go into hibernation. When this happens the the blade does process on the primary proxy and appears to stay at around 9800mhs. But again, if I start the place with the same server proxy IP listed twice, the blade just restarts over and over after a couple minutes.
|
|
|
|
|
Firstly, I searched every article I could on this forum and couldn't find a solution. I then spoke for hours in Slush's IRC chat to no avail.
After hours of troubleshooting I'm still having the same problem, though I have a lot more detail on what is happening. In a nutshell the blades continuously switch between the listed Server Addresses.
I have Slush's mining_proxy.exe configured on two local computers - both desktops, both configured not to Sleep.
Total MHS: 05121
Received: 0000062580
Accepted: 0000040226
Per Minute: 070.82
Efficiency: 064.27%
Up Time: 0d,09h,28m,00s
Current Server: 10.1.10.11:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
IP: 10.1.10.54
Mask: 255.255.255.0
Gateway: 10.1.10.1
WEB Port: 80
Primary DNS: 10.1.10.1
Secondary DNS: 10.1.10.1
Ports : 8332,8332
Server addresses : 10.1.10.11,10.1.10.10
user:pass : Any.worker1:xxxxxx,Any.worker1:xxxxxx
I have 10 blades on a backplane with an HP ATSN 7001044-Y000 979124-001 Power Supply, all of them act identical. They act the same weather I have 1 blade connected to the backplane or all 10.
I have tested switching out the proxy for 32bit bfgminer, linux bfgminer on a BBB, and different proxy software on each computer.
The voltage reads 12.81v, however I have not tested amperage as I'm not familiar enough with electricity to tinker that deep.
The blades to NOT restart - they just switch between the two servers (proxies) and remain around 5000 mh/s.
If I configure the blades with the same server separated by commas (e.g. 10.1.10.11,10.1.10.11), the blades will continuously reset after just over 2 minutes.
Happy to start up a Team Viewer Session if anyone is interested in poking around.
Many thanks to dmelvin, minigpenguin, MoonCat, bitguy, urgodfather, and honkeylips for helping me get this far.
|
|
|
|
|
