Swedish ASIC miner company kncminer.com - page 807.

CYPER

hero member

Activity: 812

Merit: 502

Quote from: Biffa on December 23, 2013, 01:05:27 PM

Quote from: CYPER on December 23, 2013, 01:01:12 PM

Quote from: minternj on December 23, 2013, 01:00:36 PM

did you custom build the rack for your jupiters? or just happened to find one of the same size?

Custom Built: http://www.youtube.com/watch?v=n_F83SbHMyg

Looks Shamazing mate

Thanks. Originally I intended to have a separate shelf for the PSUs, but it turned out each PSU next to its miner is the better way.
I even made holes for the cables to pass through the shelves, which are now unused.
I am now thinking to buy some CoolerMaster Megaflow 200mm and put them behind the miners for extra airflow as the height of each shelf is 210mm.

2 more pictures:

Biffa

legendary

Activity: 3234

Merit: 1221

Quote from: CYPER on December 23, 2013, 01:01:12 PM

Quote from: minternj on December 23, 2013, 01:00:36 PM

did you custom build the rack for your jupiters? or just happened to find one of the same size?

Custom Built: http://www.youtube.com/watch?v=n_F83SbHMyg

Looks Shamazing mate

CYPER

hero member

Activity: 812

Merit: 502

Quote from: minternj on December 23, 2013, 01:00:36 PM

did you custom build the rack for your jupiters? or just happened to find one of the same size?

Custom Built: http://www.youtube.com/watch?v=n_F83SbHMyg

minternj

sr. member

Activity: 434

Merit: 250

did you custom build the rack for your jupiters? or just happened to find one of the same size?

CYPER

hero member

Activity: 812

Merit: 502

Quote from: Bitcoinorama on December 23, 2013, 12:30:24 PM

Quote from: semaster on December 23, 2013, 11:51:02 AM

Can anybody link step-by-step instructions how to upgrade cgminer to the latest version on Jupiters?

Chill a few about to share the latest firmware with the latest CGMiner binary 3.9.0. compiled within as well as a couple of bug fixes.

Hold tight a few minutes...

Note: The problems addressed have been observed to manifest largely with the Eligius pool, however we can't say for definite it is exclusively associated with that pool, but the settings within Eligius previously compounded the issue. So expect to see a drop in HW error rate.

I will drop it in this thread, but don't currently have access to the site to update the main page, no doubt Sam will do that when he has an opportunity, but I have a flight to catch. V and I just want you to have this to play with sooner, than later...

In any case as always keep us abreast of what you observe and constructive feedback is always welcome! Tongue

Merry Xmas, God Jul, Joyeux Noel, Feliz Navidad, Fröhliche Weihnachten, Sheng Dan Kuai Le, S rozhdyestvom Hristovym! etc...sorry if i've missed anyone out I could be here all night otherwise, you get the idea Grin

Marry xmas

I have already prepared my red xmas outfit Grin

vesperwillow

hero member

Activity: 616

Merit: 500

Can I buy some Jupiters at invoice cost of $1,000 each? I'll buy a bunch

Bitcoinorama

hero member

Activity: 532

Merit: 500

Quote from: semaster on December 23, 2013, 11:51:02 AM

Can anybody link step-by-step instructions how to upgrade cgminer to the latest version on Jupiters?

Chill a few about to share the latest firmware with the latest CGMiner binary 3.9.0. compiled within as well as a couple of bug fixes.

Hold tight a few minutes...

Note: The problems addressed have been observed to manifest largely with the Eligius pool, however we can't say for definite it is exclusively associated with that pool, but the settings within Eligius previously compounded the issue. So expect to see a drop in HW error rate.

I will drop it in this thread, but don't currently have access to the site to update the main page, no doubt Sam will do that when he has an opportunity, but I have a flight to catch. V and I just want you to have this to play with sooner, than later...

In any case as always keep us abreast of what you observe and constructive feedback is always welcome! Tongue

Merry Xmas, God Jul, Joyeux Noel, Feliz Navidad, Fröhliche Weihnachten, Sheng Dan Kuai Le, S rozhdyestvom Hristovym! etc...sorry if i've missed anyone out I could be here all night otherwise, you get the idea Grin

CYPER

hero member

Activity: 812

Merit: 502

Quote from: Slartybardfast on December 23, 2013, 12:17:28 PM

Batch 2 jupiters released wtf
https://www.kncminer.com/products/neptune-second-batch?resellerid=352

BUY, BUY, BUY

ASIC-K

sr. member

Activity: 280

Merit: 250

Hell?

Quote from: Slartybardfast on December 23, 2013, 12:17:28 PM

Batch 2 jupiters released wtf
https://www.kncminer.com/products/neptune-second-batch?resellerid=352

those are neptunes, dingus.

Slartybardfast

newbie

Activity: 51

Merit: 0

Batch 2 jupiters released wtf
https://www.kncminer.com/products/neptune-second-batch?resellerid=352

Biffa

legendary

Activity: 3234

Merit: 1221

Quote from: semaster on December 23, 2013, 11:51:02 AM

Can anybody link step-by-step instructions how to upgrade cgminer to the latest version on Jupiters?

I dont think you can permanently upgrade cgminer, only temporarily. It won't survive a reboot

Actually if you install cgminer in the /config directory the binary will survive the reboot, but you would still have to manually stop the running one and run the new one after you did a reboot. *I think* . I've not worked out a way to get the cgminer binary onto the boot image partition that overwrites everything.

CYPER

hero member

Activity: 812

Merit: 502

Quote from: soy on December 23, 2013, 11:42:11 AM

Quote from: CYPER on December 23, 2013, 11:03:24 AM

Quote from: sickpig on December 23, 2013, 10:51:59 AM

Quote from: CYPER on December 23, 2013, 08:59:17 AM

Quote from: sickpig on December 23, 2013, 07:43:44 AM

Quote from: CYPER on December 23, 2013, 07:31:43 AM

Thanks.
How many of these should I see in the list?

323 root 2148 S udhcpc -b -x hostname Jupiter-1 eth0
14003 root 2152 S grep dhcp
29312 root 2148 S udhcpc -b -x hostname Jupiter-1 eth0

I think that one is enough. you should kill the one with the lower pid. But i'd prefer if you check it with someone else that is using the dhcp network settings.

usually there's only one dhclient for each network interface. If I were you I would simply reboot the miner and check how many udhcpc will be running.

but i'd dare to say that you could do this the next time a network glitch appear, this way you could use the downtime to test this solution without wasting mining time.

Thank you. I posted my problem at my ISP forum and someone suggested a possible solution where Static IP addresses would not get changed by the router - I should set Static IP addresses that are not in the DHCP pool - anything below .64:

https://i.imgur.com/3giMtIs.png

so you have set a static IP that belongs to your dhcp address pool, right?

the fact is that if you did not have any dhcp client hanging around there's no way that the BBB let the dhcp server change its own static ip address.

now that I've checked better /www/pages/cgi-bin/network.cgi I've found that there's also an avhai deamon involved...

Yes, before when I tried using the Static way. But once in a while the IP address of a random Jupiter would change and so I decided to go the other route, which was manually editing the DHCP table via telnet - I just gave my miners Indefinite lease time on their IP addresses. Fast forward to 2 days ago, when all of them started to disappear from my network all of a sudden.
If it happens again I will just set them Static again, but outside the DHCP pool range.

Spitballing here, high speed routers and switches use a complex signal to get the speed. Perhaps there's noise on your AC line that gets thru to your switch. If the Jupiters disconnect and other equipment doesn't then it might be as a result of the Jupiter signal quality. Are your Jupiters open or closed? Have your tried adding additional cooling to the controller boards and BBBs? Is something turning on in the area around the time the Jupiters show connection difficulties?

I think I might have solved the problem, so will leave it for now. If it happens again I will just set Static IP addresses outside the DHCP pool and see what happens.
Thanks for the suggestions though

thorvald

sr. member

Activity: 388

Merit: 250

Quote from: semaster on December 23, 2013, 11:51:02 AM

Can anybody link step-by-step instructions how to upgrade cgminer to the latest version on Jupiters?

ssh -l root ip address
screen -d -r
q
wget http://ck.kolivas.org/apps/cgminer/kncminer/cgminer
chmod +x cgminer
./cgminer -c /config/cgminer.conf

screen -dm ./cgminer -c /config/cgminer.conf

CYPER

hero member

Activity: 812

Merit: 502

Quote from: Bitcoinorama on December 23, 2013, 11:15:38 AM

Quote from: CYPER on December 23, 2013, 10:59:30 AM

Quote from: Bitcoinorama on December 23, 2013, 10:39:30 AM

Quote from: CYPER on December 22, 2013, 09:51:06 AM

Quote from: Bitcoinorama on December 22, 2013, 09:46:57 AM

There will be a tuning suite for Nov, but not this side of Jan, as everything there is winding down. There's just some ongoing Neptune work. There will also be the means to vary SPI clock frequency. I saw it in the original tuning suite as a feature, but that hadn't been developed into the recent release. It was purely part of a template I saw.

Can you please elaborate on what that option does as I believe many of us are just changing values without knowing what they actually do Grin

The voltage settings are clear, but the SPI voltage and frequency not so much. I know they are related to the communication between each board and the controller board, so do they increase the signal to noise ratio or am I talking rubbish Grin

By changing the voltage you are altering the power consumption and the noise to signal ratio (communication error rate - although reported by CGMiner as hardware errors they are not actual hardware errors so don't worry)

The less voltage the higher noise to signal ratio, the higher the probability of hardware errors.

The greater the voltage the less noise to signal ratio, the smaller the probability of hardware errors.

The higher the frequency, again the higher noise to signal ratio, which is not what you want.

If the SPI frequency is too low then there is not enough bandwidth to collect all the good nonces found. So you want to find an equilibrium where by SPI frequency is high enough not to miss any of the nonces found, but low enough to retain a healthy noise to signal ratio and thus minimise hardware errors.

Also, my bad, the future firmware update is not about SPI frequency, it's about configuring the PLL settings, which is directly correlated with the hashing speed as you are directly altering the clock speed of the die.

The SPI is not the hashing speed, but the speed of the communication between the dies and the controller board.

Hope that clears things up bud, and Merry Christmas, or if you're not into all that happy holidays all the same. Wink

Thanks for the info

I have one other concern in relation to changing certain hex values, that increase some other values, that lead to increased hashrate Grin

which bothers me lately: according to one KNC engineer, which I met in person Grin

anything above 50Amps per VRM is considered not safe for long term usage. Or 200Amps per board. He wasn't very clear about it. Yet the 0.99 Tune firmware has the option to increase the current per VRM up to 64Amps, which brings the question: if over 50Amps is considered not safe, why then we have 64Amps at our disposal?
What is considered safe? Judging by the latest firmware I would assume 64Amps to be safe or at least any logical, non-technical person would believe that as it is included in the Advanced tab options.

Happy holidays and don't drink too much Tongue

We need you back here in the new year Cool

The GE modules are rated for 40 Amps, but can safely be clocked above that. 64 Amps is the max where we feel comfortable clocking the VRMs to, and strongly advise against considering anything higher. Obviously pushing things too far reduces operational life expectancy, but if it's been included in an official firmware then be confident that we are comfortable releasing it as such.

Not sure where you can take the Ericssons. That said i was out of the office for a couple of weeks touring with a Nov Jupiter, and then back briefly for a week before heading home for Christmas tonight. I know precisely who you are talking about and will bend his ear when we next see eachother, he's not in today, they celebrate Christmas earlier here so i'll pick his brains when we next catch up, unless you catch him first. Wink

I am even more confused now Grin

He literally scared me and I lowered my Amps below 52 and you say that up to 64 should be OK as KNC feels comfortable with that.
I like your position better Cool

Please verify it with him and come up with a uniform position Roll Eyes

In regards to November Jupiters: they are hashing like beasts, so no point trying to change anything there.
But just as a comparison: the total current for a November board is around 200Amps (8x 25Amps), so maybe there is some correlation between that and the proposed max safe limit of 50Amps (200 in total) for an October board? But then again that 8x 25Amps might just be fairly reserved and not close to the true safe maximum.
I wish we can get an official response, just for the sake of people who decide to set all to max voltage (64Amps) and have no clue that it might be dangerous.

semaster

sr. member

Activity: 395

Merit: 250

Can anybody link step-by-step instructions how to upgrade cgminer to the latest version on Jupiters?

soy

legendary

Activity: 1428

Merit: 1013

Quote from: CYPER on December 23, 2013, 11:03:24 AM

Quote from: sickpig on December 23, 2013, 10:51:59 AM

Quote from: CYPER on December 23, 2013, 08:59:17 AM

Quote from: sickpig on December 23, 2013, 07:43:44 AM

Quote from: CYPER on December 23, 2013, 07:31:43 AM

Thanks.
How many of these should I see in the list?

323 root 2148 S udhcpc -b -x hostname Jupiter-1 eth0
14003 root 2152 S grep dhcp
29312 root 2148 S udhcpc -b -x hostname Jupiter-1 eth0

I think that one is enough. you should kill the one with the lower pid. But i'd prefer if you check it with someone else that is using the dhcp network settings.

usually there's only one dhclient for each network interface. If I were you I would simply reboot the miner and check how many udhcpc will be running.

but i'd dare to say that you could do this the next time a network glitch appear, this way you could use the downtime to test this solution without wasting mining time.

Thank you. I posted my problem at my ISP forum and someone suggested a possible solution where Static IP addresses would not get changed by the router - I should set Static IP addresses that are not in the DHCP pool - anything below .64:

https://i.imgur.com/3giMtIs.png

so you have set a static IP that belongs to your dhcp address pool, right?

the fact is that if you did not have any dhcp client hanging around there's no way that the BBB let the dhcp server change its own static ip address.

now that I've checked better /www/pages/cgi-bin/network.cgi I've found that there's also an avhai deamon involved...

Yes, before when I tried using the Static way. But once in a while the IP address of a random Jupiter would change and so I decided to go the other route, which was manually editing the DHCP table via telnet - I just gave my miners Indefinite lease time on their IP addresses. Fast forward to 2 days ago, when all of them started to disappear from my network all of a sudden.
If it happens again I will just set them Static again, but outside the DHCP pool range.

Spitballing here, high speed routers and switches use a complex signal to get the speed. Perhaps there's noise on your AC line that gets thru to your switch. If the Jupiters disconnect and other equipment doesn't then it might be as a result of the Jupiter signal quality. Are your Jupiters open or closed? Have your tried adding additional cooling to the controller boards and BBBs? Is something turning on in the area around the time the Jupiters show connection difficulties?

davewr2013

full member

Activity: 238

Merit: 100

Bitcoin For All

Quote from: bobsag3 on December 23, 2013, 11:20:51 AM

I understand this- I do the same myself.
But I would never ever ever ask a customer to lower the value, even if for a repair. That invites liability.

Im more pissed about having to ship back a $5000+ machine... after 2 weeks of unhelpful RMA emails that just confirmed what I told them. Or about the almost 1.2thash of lost mining due to 7 modules being DOA

You are conflating issues.....

The value of the repair or the "bricked" unit is under question. What is the machine worth in a "bricked" state? Myself -- I would say $1 USD.

Lost time is always painful... That's life.

bobsag3

hero member

Activity: 546

Merit: 500

Owner, Minersource.net

Quote from: davewr2013 on December 23, 2013, 11:14:36 AM

Quote from: bobsag3 on December 23, 2013, 10:27:28 AM

Quote from: CYPER on December 23, 2013, 10:25:50 AM

Quote from: bobsag3 on December 23, 2013, 10:24:28 AM

Quote from: CYPER on December 23, 2013, 10:23:10 AM

Quote from: bobsag3 on December 23, 2013, 10:16:30 AM

Out of 6 nov jupiters, I now have 3 dead moduals, and a completely dead Jupiter. RMA is pretty fast... but Ill be down almost $1k in shipping by the time this is done. Seriously thinking about just chaging back the dead one... Not worth it after 2 weeks dead then another 3 weeks in RMA.

They make you pay for shipping?

$100 per module back to sweden for each, then they want me to ship the entire Jupiter back that wont work. I don't even have RMA numbers for the last module yet.

Hm, I never knew they segregate customers like that. All I know is that us people in Europe don't pay for return shipping.
Have you asked them about this?

from them:
"We can see that there is an issue with your whole miner.
Please write in large writing on the box RMA 131223-08 and send the entire miner back to the following address:
KnCMiner
Birger Jarlsgatan 33
11145 Stockholm
Sweden

The shipping cost to us will need to be paid by customer and we will pay for the shipping cost back. Please declare value as 1000 US dollar."

And In the past I asked- never answered. Not only do they want me to pay return shipping, but also to undermark the customs. Pretty sure its illegal to do that... not happy with a establish company asking me to do that.

Bob:

I have moved a lot of equipment across borders.

We (almost) always pay to return the equipment. The company (almost) always pays to send to us.

The declared valuation is the "value added" of the repair or "standard repair cost" as established by the company. They can say whatever they want. This is accepted practice -- no customs agent, broker or border official I know has ever attempted to second guess repair costs or practices. If you upgrade the machine -- that is another issue -- the upgrade cost comes into play on the shipment back to you.

Customs have already been paid -- both ways. Any additional charges would be "value added charges" -- for the cost of repairs -- additional materials etc.

We have moved literally millions in high tech gear -- this would not have attracted any notice as being unusual or "out of place" -- just the usual grumbling about lost time and the money spent.

hth

I understand this- I do the same myself.
But I would never ever ever ask a customer to lower the value, even if for a repair. That invites liability.
Im more pissed about having to ship back a $5000+ machine... after 2 weeks of unhelpful RMA emails that just confirmed what I told them. Or about the almost 1.2thash of lost mining due to 7 modules being DOA

Bitcoinorama

hero member

Activity: 532

Merit: 500

Quote from: sickpig on December 23, 2013, 11:09:10 AM

Quote from: Bitcoinorama on December 23, 2013, 10:39:30 AM

Also, my bad, the future firmware update is not about SPI frequency, it's about configuring the PLL settings, which is directly correlated with the hashing speed as you are directly altering the clock speed of the die.

excellent.

any ETA for the new fw?

In the New Year, the only engineering between now and early Jan will be focused upon Neptune solely.

Bitcoinorama

hero member

Activity: 532

Merit: 500

Quote from: CYPER on December 23, 2013, 10:59:30 AM

Quote from: Bitcoinorama on December 23, 2013, 10:39:30 AM

Quote from: CYPER on December 22, 2013, 09:51:06 AM

Quote from: Bitcoinorama on December 22, 2013, 09:46:57 AM

There will be a tuning suite for Nov, but not this side of Jan, as everything there is winding down. There's just some ongoing Neptune work. There will also be the means to vary SPI clock frequency. I saw it in the original tuning suite as a feature, but that hadn't been developed into the recent release. It was purely part of a template I saw.

Can you please elaborate on what that option does as I believe many of us are just changing values without knowing what they actually do Grin

The voltage settings are clear, but the SPI voltage and frequency not so much. I know they are related to the communication between each board and the controller board, so do they increase the signal to noise ratio or am I talking rubbish Grin

By changing the voltage you are altering the power consumption and the noise to signal ratio (communication error rate - although reported by CGMiner as hardware errors they are not actual hardware errors so don't worry)

The less voltage the higher noise to signal ratio, the higher the probability of hardware errors.

The greater the voltage the less noise to signal ratio, the smaller the probability of hardware errors.

The higher the frequency, again the higher noise to signal ratio, which is not what you want.

If the SPI frequency is too low then there is not enough bandwidth to collect all the good nonces found. So you want to find an equilibrium where by SPI frequency is high enough not to miss any of the nonces found, but low enough to retain a healthy noise to signal ratio and thus minimise hardware errors.

Also, my bad, the future firmware update is not about SPI frequency, it's about configuring the PLL settings, which is directly correlated with the hashing speed as you are directly altering the clock speed of the die.

The SPI is not the hashing speed, but the speed of the communication between the dies and the controller board.

Hope that clears things up bud, and Merry Christmas, or if you're not into all that happy holidays all the same. Wink

Thanks for the info

I have one other concern in relation to changing certain hex values, that increase some other values, that lead to increased hashrate Grin

which bothers me lately: according to one KNC engineer, which I met in person Grin

anything above 50Amps per VRM is considered not safe for long term usage. Or 200Amps per board. He wasn't very clear about it. Yet the 0.99 Tune firmware has the option to increase the current per VRM up to 64Amps, which brings the question: if over 50Amps is considered not safe, why then we have 64Amps at our disposal?
What is considered safe? Judging by the latest firmware I would assume 64Amps to be safe or at least any logical, non-technical person would believe that as it is included in the Advanced tab options.

Happy holidays and don't drink too much Tongue

We need you back here in the new year Cool

The GE modules are rated for 40 Amps, but can safely be clocked above that. 64 Amps is the max where we feel comfortable clocking the VRMs to, and strongly advise against considering anything higher. Obviously pushing things too far reduces operational life expectancy, but if it's been included in an official firmware then be confident that we are comfortable releasing it as such.

Not sure where you can take the Ericssons. That said i was out of the office for a couple of weeks touring with a Nov Jupiter, and then back briefly for a week before heading home for Christmas tonight. I know precisely who you are talking about and will bend his ear when we next see eachother, he's not in today, they celebrate Christmas earlier here so i'll pick his brains when we next catch up, unless you catch him first. Wink

Topic: Swedish ASIC miner company kncminer.com - page 807. (Read 3050071 times)