Topic: ANTMINER S3+ Discussion and Support Thread - page 451. (Read 710164 times)

well UK customs done me over, held up on to be released by the clearing agency.
was due to be today and is now Monday (UPS), its not even that, that really gets me its the fact i live 15 minutes away from the dept!

Bitmain:

C'MON MAN!!!!


Let us know what's going on

Two B1 orders for a total of 14 S3's and still no shipment info.  WTF?

when did the payment clear?

+1

I've done the same for years, both at home and at work.

Reports for S3s on p2pool are so far very encouraging, expected hash rate being met and very low HW errors, nice work Bitmain!

Glad to have you on my node, If you have any problems or questions don't hesitate to ask

It's hard to see in your pic, but I think you have what you want. You want a dedicated PCIe cable to each blade (2 blades per miner), so for 2 miners, that's 4 PCIe cables, should not be a problem to run both off the 860Watt PSU.

Depends on lease length and how long the devices are away from the network. If the lease expires before the device reassociates and another device associates in the meantime, it will end up taking the IP and they will rotate. If however the devices aren't moving around much, they will just keep renewing their leases and keeping the same IPs.

Interesting, because my family iphones, ipads and laptops IPs are always rotating when on DHCP; same with PC that went for repair of the power source.
Once it came back-different IP, even completely out of previous range. Maybe it is different for miners.

Report on performance: after 14 hr one S3 shows 440.8Gh and another 439.3GH average at default settings.

I went ahead and moved both miners to one Seasonic 860Watt Plat PSU and just plugged in 2 PCI-E's like you said






yea, I have mine pointed at a p2pool (coincadence) and it looks like it's working.  I just turned the miner back on after switching out the PSU's in this shot.

In my case, I have IPs all handled from a central DHCP server. Prevents weird conflicts occurring and I can assign a static lease from the server to ensure a device always has the same IP if it really bothers me. Just a matter of personal choice, I find it a lot easier to administer given I have dozens of various devices running across a whole bunch of different private subnets...

ive always done DHCP and my IP addys have never changed, even after reboots and shut down's to move hardware around the garage

I guess its up to you.. I only decided to look at mine because it was getting a lot more HW errors on one.  

You will have to remove the 4 screws on the outer heatsink and lift it and slide it out the top.. it won't clear the case any other way.  You will see what I mean if you try it.

You won't be able to see any leakage like you could on the S1, its all enclosed by heatsinks on both sides.

I didn't like the fact that the one side had heatsink paste completely enclosing the chips, on the pins and everything.

Surely using thermal pads like a GPU uses would be a better choice here... I'm considering purchasing some thin thermal pad sheets to replace the thermal compound and see if it works better.

Rich

No problems

The reason all the router functionality is exposed is that the OS is OpenWRT, which is designed primarily for use on wireless routers. You can do a heck of a lot with it on a good quality router, and in the case of the S3 the controller board is really little more than a specialised wifi router board with some extra circuitry to allow it to talk to some USB devices. This appears on a cursory glance to be wired directly to a PIC32 microcontroller which has some glorified firmware on it that does the actual talking to the ASICs. I'd imagine this wouldn't be dissimilar to how the older BFL gear worked, with a MCU to handle all the discussion and job handing between the ASICs, and converting it all into a nicer format that gets shunted across the USB serial port set up between the AR9331 and PIC.

The blades themselves don't seem to talk as ethernet devices, they need that PIC in there to handle things properly.
Could probably make the blades as PCI-e cards if they really wanted to...

What would be the advantage of DHCP vs static? With DHCP you will need to check it (IP) every time you want to login or ssh.
Not a big deal, of course, but why bother?

It happened to me once with S1 shipment. Quick shower-heard something like a bell-UPS was gone. Had to call to ask to divert to UPS store later in the day.
It DOES happen.

Regarding S3-does it have a reset button? There is a small opening to the right of lights on the ethernet port. I wonder if this is it, but I hardly see any button there.
Manual says nothing as far as I can see. I will open it up later to try to locate the reset button.

Ok, here is my quickstart guide. Please correct and make additions/removals/clarifications as required...

1. Plug up your power supplies to your AntMiner S3. Minimum of one PCI-e power connector per side (2 recommended to avoid meltymelty)
2. Plug up a network cable to your AntMiner S3. Plug the other end of the cable up to your LAN or directly to your PC (if your local network is set up on a different subnet - see below)
2a. If your local network is not running on 192.168.1.0 with a subnet mask of 255.255.255.0, use the direct cable connection method and set your wired interface IP to a static IP (such as 192.168.1.1 subnet mask 255.255.255.0, no gateway).
2b. If your local network is running on 192.168.1.0 with a subnet mask of 255.255.255.0, ensure no devices are already using 192.168.1.99 (use ping 192.168.1.99 to check) and plug the AntMiner S3 directly up to a free port on your switch or router.
3. Connect to your AntMiner S3 by going to your web browser and typing http://192.168.1.99/ (username is root, password is also root)
4. Configure your miner settings under the Miner Configuration tab, then save and apply the settings.
5. Go to the Network tab. Select "Edit" on the WAN line.
6. Change protocol from "Static Address" to DHCP client. Set an appropriate hostname (such as antMiner) then click Save and Apply.

You will now lose access to the device. If you had it connected to your network, check your router to find out what IP it now has. If you had it connected directly to your PC (from having a different subnet, such as 192.168.0.0), disconnect it now and connect it to your local network instead, then do as above to find its new IP.

7. Log back in and confirm everything is working correctly. You should also feel a fair bit of warm air coming from the output end of the miner.

That is it!

Additional Steps:
Enabling Wireless - This will require some hardware modification and will probably void warranty, do so at your own risk!
The following is more technical than the previous instructions. It assumes you know how to connect devices to your wireless network, configure them, and how to safely drill holes in metal. If you have any doubts on how to do this, STOP NOW and ask someone who does know what they are doing.

Open the case of your AntMiner S3. Identify the controller board, mounted on the top of the inside of the unit (where the network port is). On this board is mounted a smaller board containing an AR9331 system on chip. Near the bottom left corner of this board (Labelled ThinkPHY 2) is a U.FL antenna connector. You will need a suitable pigtail and antenna (both can be sourced from ebay for about $1.50 each, some of the most common are the U.FL to RP-SMA ones, and antennas are easy to find).
Carefully drill a hole the correct width for the pigtail to be mounted (do this without the board in the way, and ensure no metal filings end up in bad places), mount the antenna end of the pigtail in the case, then carefully and gently fit the U.FL connector to the antenna connector on the board.
Reassemble the unit, then attach the antenna to the pigtail's now protruding wireless antenna socket.

1. Power up the unit (connected by wire to your LAN) and confirm everything is functioning normally through the web interface.
2. Go to the Network tab, then select the Wifi subtab.
3. Next to Generic MAC80211 802.11bgn (radio0), click the Add button.
4. On the new page displayed, set the ESSID to your wireless network name, the mode to client, and set the appropriate security settings under the Wireless Security subtab (about half way down the page, near where you set the ESSID). Set the network to "Create" and call it wifi.
5. Click Save and Apply. (And wait a while for everything to apply)
6. Select the Interfaces subtab, there should now be a third network option called WIFI (along with the two original ones, LAN and WAN). Click the edit button for WIFI.
7. Change the protocol from Unmanaged to DHCP client. Set an appropriate hostname, then click Save and Apply again.
8. Confirm the AntMiner S3 has successfully associated to the wireless network and acquired an IP. If it has not, confirm your security settings are correct and check the device Kernel Logs from the Status page.
9. Once correctly associated, you should now be able to access the miner through its wireless network IP. If this is possible, disconnect the wired network connection and confirm the unit keeps mining.

K, I appreciate the advice but I was supposed to mine during my holidays

If I don't have a choice, I will follow it but...I would prefer to not have to. 

Depends

Create a UPS account on UPS.com. Login to UPS MyChoice. It may or may not be available for your region but if it is, you can change your delivery and have them hold it at a UPS location, or deliver it on a certain date.

still no ship for my 2 orders

payment confirm: 2014-06-30 19:42:03

payment confirm: 2014-06-30 20:58:49