Topic: Swedish ASIC miner company kncminer.com - page 1266. (Read 3049528 times)

the moment you are able to access the gui page, go to the inetworking tab/page uncheck dhcp, and assign the ip to your miner


but... it may be easier to use putty and get in directly thru cgminer..., you can keep the connection live if you make it in...  still change the info on the gui networking page

things change..  when you go back to .94 do you get the same result or even more HW errors now?

Thank you for sharing that.

i dont follow this but it sounds promising.

arp-a on my Ubuntu laptop shows me "Saturn-5F9" and the IP.

"NMAP -sP 192.160.0.0/24" will list all devices on the network that respond.

Maybe try that and hit up each device on your network one a time?
I had about 25 devices here at the house with all the laptops, cell phones, gaming systems etc. lol. But I found the device pretty quickly.

It will ask for the login and password (admin/admin) when you find it.

are you absolutely certain it's the correct I.P.?  labled with
kNC or Texas Instruments
it can be difficult to time it just right, I had similar woes...
gotta scan at just the right time to catch it for me it was...
The moment you get the ip....
then turn dhcp off on the gui asap, and assign i.p.'s before cgminer closes the connection.
good luck.

P.S.   during the green light flashing on ethernet. If it stops, start over.

if you can putty in... You will most likely find the workername  in CGminer is wrong.
you can change it there instead, just be sure to save to /config/cgminer.conf     and not the root address.
that will fix it.

I had to "Crack" into every Saturn this way because of the workername field contained too many character spaces in comparison to what was on my pool.

anyone have a suggestion for a miner unable to even get the GUI up?

12 hrs, 3 people, 2 laptops, team-viewer sessions.... nothing.

tried 5-5-5 reset - nada

changed ether cable - nada

found the IP easily with arp -a, solid green led, fans are purring, blue leds twinkling

'halp'

Nah, that can't be right as (4dies)(48cores)(6watts)=1152 watts.

So, at 100%, 180watts/(4dies)(48cores)=.9275watt/core.

cool, my offer of letting you play with a saturn is hereby offered to cklovas...... ! you da man, ty for being so understanding!



on another note (totally off -topic)  It's a goood morning...

When I fuss with my cardboard and fans, I sometimes get a reboot.  Since I run, at the present, without the top, center cardboard cooling the BBB, a 12v fan sitting inside blowing on the left side of the module, another 12v fan outside the case blowing on the right side of the 1 module (Mercury), I added another piece of cardboard to the right of the BBB, to the side and up to the module, taking the air pushed out the side and directing it to the module.  The miner white light came on and off as I moved the fans, perhaps a loose pin in an added fan connector, but it started again right away.  Put Bertmod back but earlier tried the 0.2.1 and found it works well with firmware 0.90, looked at my cores, which I could with the 0.2.1, and earlier their was a single core not up, but now there are four 100% cores and the BertMod says the power change from adding that one core on firmware 0.90 with ~0.9v to the 4 vmr's, was 174 watts with one core down and 180 watts with all cores running.

Hello,
For any of you want to try solo mining with KnCMiner follow these steps:
- In a windows or linux pc, modify local (appdata) bitcoin.conf, add line rpcallowip=localip e.a. 192.168.1.xxx
- Ensure that your firewall does not block bitcoin-qt
- restart bitcoin-qt
- In KncMiner mining tab set as pool 192.168.1.xxx:8332, user and password whatever you have in bitcoin.conf
- Restart CGMiner in KnCMiner Mining tab (web GUI)
Works just fine.
Depending on your luck you may find a block earlier that expected block finding time e.a. 51 days for a saturn or 24 days for a Jupiter.
Also you can save from the increasing difficulty.
Of course the risk remains.

It's up to firmware what Output Voltage are used. Now I use 0.94 with 0.9V (194W power output). If your boards are running fine with 0.7V I recommend you to use it. With 0.7V I only have half the output power (about ~100W) but more cores disabled (40 cores of 192 disabled).

Temps are rather high. Tried additional cooling? Cool down the bbb as well as the vrms etc.

Well I am at a total loss why my Jupiter does not get above 410Gh/s. (380 at BTC Guild)

Tried every firmware, tried the Enable cores patch and still the same.

Look at the results from bertmod, I have 1 Asic #4 showing (192 Cores all on hashing at 130Gh/s)

The other 3 Asics (# 0 , 2 , 3)

#0=80.58Gh's , #2=93.36Gh/s , #3=88Gh/s

The DC/DC are all showing 4 on and ok apart from Aisc #3 only showing 3 DC/DC on and ok , no other found.

Temps are as Follows

HW status:

ASIC slot #1: 53.5 ℃
ASIC slot #2: -
ASIC slot #3: 54.0 ℃
ASIC slot #4: 61.0 ℃
ASIC slot #5: 58.5 ℃
ASIC slot #6: -

Thought this was to be plug and play, I have spend Hours upon Hours trying to nurse this Lemon back into life.

Got in Mining on the Day it arrived Wednesday the 16th at 14:00 (UK time), Mining via BTC-Guild I have the grand total of :-

2.25 BTC's

Any Suggestions on what KNC should be offering to do when I call them again tomorrow.

I suggest, if you're running with the top off, cut a piece of cardboard the width of a front fan, about 5.75" wide, and high enough to abut the front of a front or both front ASIC module(s) and reach under the lip of the top front of the miner, and put it aside.  When the hashrate crashes down, try putting the cardboard between the two front fans so the outside halves are pushing air into the box but the center halves are pushing air down onto the BBB.  I think it's the BBB heating that causes the drop after hours of otherwise good hashing.  If I'm right, when you put the cardboard in place, you can watch the first figure in the cgminer hashrate, that you can view ssh'ing in using putty, immediately rise up.  If I'm wrong it won't.

Yes, and the efficiency looks quite good.  

I see that using 0.90, which I believe uses the most energy and produces a high percentage of duplicate shares that count as rejects, this on a Mercury, using a cheap 12vdc switching supply (the output voltage of which I can adjust) and an inexpensive BBB supply, I'm drawing 259½ watts (174 watts on BertMod) at the wall so it's an efficiency of 67% so that's not great.  Of course the BBB draws and it's 1 BBB to 1 module while with a Saturn it's 1BBB to 2 modules.  

I may be able to increase my efficiency even more by dropping the ASIC PCIE voltage down.  The onboard vrms aren't completely efficient and lowering that voltage might find a sweeter spot.  That's the only advantage of this cheap supply designed for powering a huge load of LEDs, the output is adjustable.  That and its cost, $27.88 free shipping and a few bucks for tantalum capacitors I added.

Still, 600 watts on 2 Saturns, that's 150watts per.  

I'm getting 134GH/s as the final settling point on 0.90 at 174watts on BertMod.  If you're getting 150watts at the wall per then I suspect you aren't getting 134GH/s per avg.  Of course you could be if the efficiency of the later firmware versions is great but I've heard that's at a cost of hashrate.  Eliminating the duplicate shares would have gone a long way to increasing efficiency.  I'll know later today when I go to higher versions of the firmware until the duplicate shares stop.

Such true words, I checked fans and flashed my saturn to 0.93 the day I got it and not even logged into the web interface since.

No worries, sent you a nice response in PM.

Sorry but maybe I missed some news along the way. Are you able to change voltage at will? Or are you saying that using 0.90 fw means using higher voltage, while 0.95/96 lower voltage?

edit1: very nice pics by the way

Hi guys,

so I played a little with firmware settings, voltage (0.7 / 0.9) and after a few restarts I now have my Mercury running stable at 130 GH/s and only have ~15 cores disabled instead of 40 cores with firmware 0.90 and enablecore.bin.

I made a few photos from the ASIC board and found out that the VRM with an output voltage from 0.9V they reach temperatures over 89°C.

Here is an album I made:

http://imgur.com/a/wVSbq