Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 21. (Read 53012 times)

Maybe this helps or maybe not . . . but I had some early wifi issues and I turned my unit on it's side and it seemed to help directionally - but I eventually hardwired it and that was much better. Also, something I found in Futurebit's guide mentioned the following . . .

"Please note our wi controller only works reliably on 2.4GHz wifi networks. 5GHz/Mixed 2.4/5GHz network
might not connect. Most routers have options to separate the networks on two separate SSIDs. Use the 2.4GHz
network to connect your Apollo if using wifi."

Cheers!

I was on wifi. I put it in the exact spot my old node was in and man its rough. I had 31 connections then it would just disconnect. I ended up moving and hardwiring.  It the internal node and all external miners disconnecting.

I check latency on wifi and im at 18ms-23ms

Hi, thanks for sharing the config! Regarding the two options:

"nonce1length": Usually set to 4 by default for solo mining.
"nonce2length": Typically set to 8 as a default.
Unless you're customizing your setup, leaving these as default values should be fine. Glad to hear your sync is complete and running smoothly! Keep an eye on that NVMe usage, though—71% seems like it's getting up there!

Hi All,

Do we need the bellow two options in the ckpool.conf or used as defaults?

 "nonce1length": 4,
 "nonce2length": 8,

BTW, Synch finished few hours ago and solo is up and running. Nvme is 71% Used  

What is disconnecting the network (are you hardwired or running on wireless?) , is it the internal node, internal miner, external miner (connected via USB) or network connected miner (on the LAN or coming through the WAN) ??

Are you seeing more than 12 connections to the node?

I have several PH remotely and locally mining through to my Apollo II full node with no issues at all. My node is hardwired though.

I highly recommend going hardwired if you are solomining to reduce network latency.

Also you may just want to actually shut the Apollo II down fully for a few minutes and restart and let the services come up gracefully without clicking on things. If that doesn't work I would reflash to play it safe.

Just set up the apollo 2 node. Fully synced and it seems to keep disconnecting. My apollo 1 node never had any issues and I just disconnected today. The Apollo 2 node has port 3333 open.

Also on the dashboard whenever it says i'm disconnected from the CKpool the power button at the top right flashes a yellow/orange and when I click it I see at the button under version a red exclamation point next to V2.0.5. Any ideas why I keep randomly getting disconnected even though my internet is still up?

Exciting! I'm so pumped to be sending some more hashrate to my own node.

Unfortunately not but I do know its a work in progress.

Awesome!! Did you ever get a rough estimate on release?

I know this was requested by me to be fixed in the next release. Hopefully we will see this soon!

I have miners about to be pointed from offsite locations to my apollo 2 node. Is there are way for me to see each offsite miner on the dashboard so I know if and when a minter is offline?

Right now I have 5 miners working but Only see 4 in the total pools and hashboards section.

Cheers

Much appreciated for your reply. Yes finally i will use only the custom settings.  LOW setup during Day Time (higher Temp and cost for Khw/h) and HIGH Settings during night time.
I set a crontab job to switch between these setting automatically. The only problem is that the GUI still shows the old values. (Not sure how to force a refresh)

I noticed also that increasing the Frequency (same Power) there are no changes in Speed,Watt/T,Temp etc.

Hard question to answer as your question actually creates more questions than answers. Regardless, the short answer is it's the luck of the silicon draw. In other words, it's simply all the variables involved that creates the inconsistency in the expected values. First of all, you're trying to replicate a hard-coded algorithm preassigned to accommodate all those variables when you try to do it via the custom settings. It's probably not going to happen. Maybe pretty close, but no cigar (which I think you already achieved). I have found for instance, if I do a simple reboot of the miner I will see a variation of 3-4 watts just because I restarted. Don't know why. And it will stay that way until another reboot in the future. Then it will change a little. Sometimes it's just because the fan is running at a slightly different speed. Sometimes it's because I'm pulling more power to other units on the same circuit and starving the Apollo a bit (guess). I've even noticed that some pools put more of a drag (slight) on my system than in other cases such as my own node or solo.ckpool. Then, of course, there's heat and humidity, and maybe even the alignment of the stars and moon phase (just kidding). All kidding aside, unless there's a good reason to try and replicate what the algorithm is doing I would sincerely suggest using the custom settings to your advantage in promoting higher hash-rates without overheating your units. Just my opinion but cheers anyway!

Hi, Just got also the New Apollo II.

Can someone confirm what are the ECO default values.

I saw in an older post that is Power:48 Freq:30 (-brd_ocp 48  -osc 30) but when i use these as custom i have totally different behavior.

After 10min

Power     Freq      Watt         Watts/T    Temp   Speed
48        30      173            35           62           4.97
eco   Mode      197            37           68           5.35


Thank you

Yeah, kind of annoying of course.  I ordered in April and received late July only to have to send it back after a short time.  Hopefully they rectify it right away and I can get to hashing.

Yeah, I was thinking heat problems as well but since you were running ECO it didn't really add up (unless there's intermittent fan issues / malfunctions). Oh well, I hope it all works out for you. On a side note, I've still got an overdue standard unit just sitting at the FEDX hub in Memphis now 3 days late with no updates or explanations as to why or when I'll ever see it. Three cheers for PATIENCE!

Will do.  They finally got back to me today and said it sounds like it's having an overheating issue and I'm shipping it back to them.  stinks I have to pay to ship it back but hopefully gets straightened out asap.  They said approx two weeks.

When you get this straightened out let me / us know what the cause was please. Appreciate it. Cheers!

Tried this.  When the issue happens it dissapears from the ip scanner as well.  Happened again for the 4th time last night.  Just turned it off at this point and emailed support.  Obviously I have a faulty unit so hopefully they will come through and give me a way to send it back for a fix or replacement since its only been in my home for around 30 days

If you cannot connect remotely again, try to access the miner, with a PC on the same network, as the Futurebit. If this fails, then try to ping it and last use a IP scanner to see all the devices, within your netwok.