Topic: BITMAIN AntRouter R1: 1st wireless networking device with bitcoin mining chip - page 22. (Read 77755 times)

he did and also has another batch coming in tomorrow.

I can vouch for CrazyGuy (asicpuppy.net) - I have bought from him multiple times and he's been reliable.

-r00tdude

I suggest getting one from CrazyGuy - https://bitcointalksearch.org/topic/asicpuppynet-terminus-moonlander-2-2pacs-in-stock-btcltcethbch-612390 .  Bitmain is out of stock and he he selling from stock.

And he is quite talented at programming.   He has the most advanced custom firmware I feel pretty safe saying currently.

It is cracked already, and you can now set up to solo or pool mine with the same interface as all the other Bitmain S series Miners. Several methods are covered in this thread and if you buy your Miner from CrazyGuy you can even choose to have it shipped with the Custom Firmware.  

https://bitcointalksearch.org/topic/m.6775261


Rich

If this firmware can be cracked I'd buy one.  Until then I'm on the sidelines waiting to play.
Just don't like the idea of being forced to mine on antpool. 

I'm pretty sure that the other day it was at 134, when I was trying to connect with the @BitMain username on the R1, which should have worked as I bought it from Bitmain direct. But it didn't seem to work, however within about 15mins of adding my usual antpool id the counter went up to 135.

Also has anyone got any compacs running off of the inbuilt cgminer on the R1?

i think it takes a bit, or might only count miners who are connected for several hours

It would be interesting to understand at what point a new R1 is counted as "Valid" at Antpool. My gut feeling is that it is very straightforward and will be when you connect your R1 with a valid Bitmain email address entered for the first time. However it's also possible that it is counted even if you connect when it is set to Bitmain, as it's address includes the MAC?

The only snag in confirming that the valid count goes up is that the Antrouter Mining screen is not visible until you have connected an R1... So if you were connecting a second R1 it would be easy and you could check the number, currently 141 which is only 1 up from Yesterday, and then plug up the new one and check again.

If anyone one here has one that has not been connected or is getting one shortly you could ask for a count and then go ahead and connect. Other interesting experiments would be to change a miner to another ID / Bitmain account and see if it's counted again, and finally to edit in another MAC and see what that does? 

Rich

OK well I will stick with my assumption that either there are not many out there or they have not been plugged in yet. Changing pools is easy when you have done it but far from easy first time in, particularly if you have not SSH'd before. I think most people presented with a new bit of kit follow the instructions first to check that it is working and even then many people are nervous about making changes at the file level.

Let us know how you get on changing pools and be careful not to allow internet access before making the changes or you will be counted. 

Rich

Considering they talked in invetviews about like dream to do the device, or something I think they would have sold a lot more then they did.  It seems they ran out. I think some switched to ck solo pool most likely.  But I would guess at least 1/2 kept antminer pool.  Just as I don't see over that moding them yet.   

So they sold I'm guessing around 200-250 maybe.   I'm speculating I could be wrong.  I just don't think it was the thousands like I would have thought before.  I suspect shipping was a factor.

Why wouldn't you think the majority switched the pool?  It is apparently very simple to do, someone figured it out and posted here within the first week or so the device was released.  This website is one of the world's largest repositories of bitcoin know-how, so most people that mine probably visit this site.

I get what you are saying about the initial setup and all that, but you made an assumption about how the stat is being reported so maybe your assumption is incorrect.

I would assume the majority have switched pools, since you can go through this thread and see almost everyone who commented said it was lame that it's set to mine on Bitmains antsolo pool and that they would change it if they had the device.  When I get mine I am configuring it to mine elsewhere right away, I do not want to mine for Bitmain at all or use any of their pools.

Thing is if you read their text "During the last 100 Days in 140 Valid Miners" I interpret this as meaning that in the last 100 Days 140 Different ID Miners have attached to the Pool? Now I am sure the first thing that anyone would do on taking delivery would be to plug it up, connect to the Internet, put in their email so that it stops mining for Bitmain and confirm that it is working.

Now if they do that then it would becomes a Valid miner and would be added to the total. I find it difficult to believe that anyone would have immediately dived in and edited the pool information without going through the above? So my gut feel is that there are not many out there, this is semi supported by ITop still not having delivery of theirs?

I rest my case. 

Rich

I cant decide if a lot went to CK's pool and just modified it or if they were limited at launch and sold out quick.  It seems they sold out quick, I'm assuming they will have another batch but I'm guessing they are focused on S7 ATM on next batch.

Antrouter is small in scheme to them compared to getting next batch of S7's up.

I have not yet been able to put my hands on one of these, but I am currently drafting up some code to be able to run monitor on one of these (already have the code partially working on an S1 controller), so here's a request to whoever has one of these.
Could you kindly run via SSH and post the output here from the command cgminer-api '{"command":"stats"}'?

PS. Copying from the SSH window (in MS Windows) involves simply selecting the text in the SSH window then pasting into a message (no need to look for a copy command via right-clicking ... automatically done when you select the text.

@ITop_James - did you manage to get your order delivered after all?

Have had the R1 for just over a Week now and one surprise is how few there are connected?



It was just under 100 when I first connected, and only 140 now. Is it that they have only shipped a few or have people not got round to plugging them up. I can't believe that the majority of people have worked out how to change the Pool?

Also think it would be good if Bitmain livened up the Stats. Would be good if they could have a leader board / Best shares achieved as we have a long wait before the first Coin is Mined.  The Mining Chart makes sense, however if you look at the Mining Record it's exactly the same data but with a different scale that always seems to adjust you to a max challenge index of 80. What's that all about?

Rich

Latest update is that fixing the dry joint on the power connector has significantly improved things, however the stops have not gone away. I can typically run for 4 to 8 hours without one but can the see 2 stops in 20 minutes? I have also seen a couple of times that after a stop and restart the miner reverts to it's standard rate of 5.5GH, this despite the frequency box still showing the higher frequency and doing a save and apply returns it to the higher frequency?

I have this "feeling" that there are more stops when I am in the office working on other projects and on one occasion a stop was completely coincident with switching off another PSU, so perhaps having the R1 uncased has made it more prone to EMC and that is the reason for some of the stops?

So I will leave the R1 running in the background and try a few more things while getting on with other projects. I have an outline plan to put it back in it's case, fit a DC socket so that it can be powered externally, a multiturn pot to adjust the Core Voltage, a socket for the serial port or if there is room put the USB serial inside, & an external antenna. I will also look into either a CPU cooler or just some holes & a fan bolted on to keep it cool.  

Thanks for the links to th API I will have a read and see if I can find any other things I can monitor that will be useful.

Overall I have got to say that the R1 has been great value for money as a device to play with and mod, and I think there is plenty more to come.


Rich

get the latest cgminer from this thread

https://bitcointalksearch.org/topic/official-cgminer-mining-software-thread-for-linuxwinosxmipsarmr-pi-4110-28402

various READMEs including the API is in there.

Threads like this one are why I love this community.  

I'm waiting for my R1 to be delivered today and soiling myself thinking about what I'm gonna do it it when it arrives. Not to mention that I love the fact that I am actually going to use it as a wireless router anyway (so it serves a purpose other than being a rig).

Latest news is that I have found  a dodgy soldered joint on the 5V socket to the Miner. I think this may have been responsible for most / perhaps all the stops? You only had to breath on it. I have been running now for 3 1/2 hours at 200MHz / 11GH/s and it has not missed a beat. Earlier before fixing the joint I had dropped right back to 100MHz and was still having regular stops.

So fingers crossed, will give it  few more hours & then crank up the frequency again. If I get another stop I will do as you suggest and disable the script.

BTW how do I use the cgminer API, is there a guide someone can point me at?

Rich

Those restarts are not necessary, but you can find out more / confirm that with output from cgminer-api. Basically, in your last example aka the Case B restart, cgminer has been restarted because no valid work was sent by cgminer for a certain duration, and in this case it is because the LVW is the same as that on the previous check. This may, in instaces, be due to cgminer not running (thus the need to restart it), but more likely be due to not finding any work at the minimum diff set by the pool you are mining on. I therefore think that is a buggy script in that sense, and since you are testing, I'd go as far as saying to you to completely disable that script, or at the very least remove the starts & stops in the script and just keep the logging and see what results you get.

PS. I am no expert at this, just my 2 cents...