Topic: Swedish ASIC miner company kncminer.com - page 45. (Read 3049521 times)

He is selling software that is not eligible for upgrades.  He knows it.  And he just put up another ebay auction this morning that goes on for a whole month. 

that happens to me (like once every few months) I just reboot (then again may just get lucky)

then again ..the orig OFF Dies I got on the orig Titan Nov 2014 have always been that way (knc would not rma any cubes with just 1 dead die)

so hell it is prob flaky 1st batch dies...or so knc used to say (why they changed the firmware from a max of 300 to 350 ..up from orig design specs of 250mh)

damn..I wish someone had archived knc forums i can drill down with way back machine to the title but not the msgs

What time is user vegasguy  scammer ? Share your knowledge with us.

EDIT.
January 11, 2016,

EDIT2

2 days later

This Titan did it again. Weird:

DC/DC   Voltage (V)   Current (A)   Power (W)   Temperature (°C)
0   0.7900   41.5625   32.834   59.900
1   0.7897   41.2500   32.575   73.400
2   0.7867   41.0625   32.304   57.400
3   0.7886   41.6250   32.825   52.700
5   0.0035   0   0.000   17.300
6   0.7883   40.3750   31.828   44.900
7   0.7928   39.8125   31.563   45.100

The above link is a scam.  NEVER buy the firmware from any website except the official one, which is...

http://gentarkincustomtitan.pcriot.com/

If you buy from any other website, throwing away $50 because you will not get updates.

Clarification update!!! PLEASE READ!!!!

I have NOT POSTED a new ebay ad yet. The one currently on ebay is not the official source of the firmware. Currently the only official source is my website: gentarkincustomtitan.pcriot.com or myself directly.
I will announce when & if this changes.
I will announce when & if I post a new ebay ad.

Until then, any purchase made from sources other than listed above will be NOT BE ELIGIBLE for free updates to the firmware!

Please dont link that ebay ad. Thats vegasguy's ad and any buyers of that firmware will not be available for free future updates of the firmware from the legitimate firmwae source(myself).
If you are really interested in such firmware and wish to have free updates & fixes in the future then it can be bought directly from my website - http://gentarkincustomtitan.pcriot.com

Thank you for doing this. Next, get Titan to hash with Beaglebone. Working on it.

And I'm sending out my first repaired Neptune/Titan controller boards.

From KFC ? Never.

KncMiner Titan custom  firmware 
http://www.ebay.com/ link deleted

When they will come out with new Titan firmware
From knc?

I tried KNC Jupiter controller plate with Titan bridge and Rasperry Pi.

The last 48 hours  everything works beautifully with v.99d software.

The only difference between the Titan software and Neptune software is, that both red and green LED lights are up with Titan.
With Neptune will eventually only  green led and red led turns off, if the miner works .

But these are LEDs, which are only in oktober and november controllers. They can also be removed.

Why not someone just email knc ... I emailed knc questions bout their firmware and they got back to me in a couple days.

So does anyone have any spare non-titan controller boards laying around or useless to them? I'm tired of everyone throwing around the idea that the titans could use a neptune board or vice versa. I'll pay someone for a working neptune controller board just to test it out and get everyone to stop talking about it and just have the information if they can be interchanged with an added Pi + Bridge or not. Who's willing to give up their neptune controller board for 70 USD? (= 100 CAD).

Disclaimer: I don't claim a Titan controller will work with a Mercury,Saturn,Jupiter, or Neptune or vice-versa.

I do state as fact from my own eyes that Merc,Sat,Hoop,Nepturd controllers are ALL the same hardware.
The only 'functional' difference between Oct&Nov 28nm ASICs was the change to Ericsson DC/DC converters.
The same controller works equally on either.
You MUST have correct firmware on the controller to handle this change on the ASIC PCB.
Oct. firmware will not work with Nov. ASICs but Nov. firmware _IS_ backwards compatable with the Oct. ASICs.
This is documented in the code kfc publicly posted.
They provide everything but the source code for the FPGA, but they do provide a working compiled image.
I never tested it but I recall from browsing the code that a Nepturd controller prolly works fine with either OCT or Nov 28nm ASICs also.
I also seem to recall posts saying it was an all or nothing proposition.

I run some nepturd cubes with an Oct Saturn controller HW reflashed with newest firmware.

The whole point of putting an FPGA on a controller between a PC(Pi or BBB) and the ASIC is that it _IS_  a "Field Programmable Gate Array".
There is no reason to think kfc would abandon one of the few good design choices they made.

Since you have both BTC and Titan controllers why not simply look at the forkin part number printed on the PCB?
Even if it is a different part # it has the same FPGA mounted on it.
Look for numbers etched in the copper specifically, new paint does not a new circuitboard make.

Occham's Razor says kfc is too cheap to have made any changes to a working PCB design.
I'd further speculate that they created the bridge board to AVOID having to change the controller in any way.


YMMV

Yeah, I just checked hashrate. I think its just variance, theres been a bunch of spikes up this high within the past few months but overall diff has very slowly risen. So ... theres not too much going on in ASIC world of scrypt. That is unless this hashrate keeps up then we are all in trouble LOL!

At least LTC's diff isnt rising like BTC's diff ... yikes!

Which factory

Put scypt power


At network

well I'm not gonna slam you for helping me...but has anyone tried this with an OCT jupiter/saturn/mercury ..they do not work with a NOV Jupiter cubes etc (mix/match)

that is my question as well...I have an OCT Jupiter Board...but to be safe ..someone should at least TRY this first with an LCD and the GUI with NO cubes and see
on ideally 1st a Neptune board in question..then next likely is the NOV jupiter board (last run) then perhaps my OCT Jupiter or others like saturn/mercury boards?

if it kinda works before tossing a Titan cube to sacrifice to the ASIC gods .....with this OCT Jupiter board

I agree it SHOULD work....at least as a test with the LCD and the GUI with no cubes to start...but again ideal would be with a neptune controller 1st imho

THAT is the main issue...i have a clone bridge coming..got it as a spare (miners are 14.5 months old orig titan warranty was 90 days sooooooo seemed prudent
with 2 titans and the 'possiblity' that is the missing piece to the controller problem ..a complete clone hardware work about

supposedly have the proper pi (nov 2014) as a spare also ...according to knc tech staff at that time (assuming they know zip) raspberry pi B+ 512mb model


just trying to help ....don't like the way i say or do such ...big whoop....at least I'm trying to ask some questions on this (ie will clone bridge work on neptune 6 port board?)

anyway thanks for the confirmation ..I will take it as help from you....no issues...BUT some confirmation of HAS SOMEONE ACTUALLY DONE THIS YET would be nice

If so I will gladly try to be the crazy 2nd guy to do so...even on my Oct Jupiter board....(the bridge clone is in the mail)

anyway thanks for the input ..if you have further info as to who has done this already shoot it out here as well for all of us....

Heh. I've been pulling power supplies from Neptunes and now a Titan. Sometimes it's because I am troubleshooting the supply reading 0.0 volts (dead short, usually under chip, bitch to reflow) sometimes because the power supply turned into a little cute inferno. In these cases advanced screen will show the skipped supplies like 0,1,4,5,6,7

This is a bit different. What I see is a Titan where it hashes away with supplies 0,1,2,3,4,5,6,7 all purring, then when I come back the next day it shows only supplies 0,1,3,4,5,6,7. 2 literally is not there from the advanced view. If I reset the second die, 3 will try to supply *all* the power. Which will probably cause a quick and fun fireball.

Power cycle the cube and 2 reappears and it hashes happily. But sometimes it's a different supply that "vanishes". Really odd.
If theres a true hardware problem w/ ur titan tho then of course my firmware cant do much bout that =P

That's it. Your firmware rocks, and while I think I can see how to fix this with appropriate calls, it's a billion times better to just say "Pay Tarkin $50, it's the best $50 you spend" than pay me substantially more to pull and swap power supplies. I will flag this as "logical sense solution exists" and focus on the fireballs.

Next up: Why a shorted Titan shorts down the whole FPGA by shorting pins 4,6 on the 10 pin header. What's that all about :-)

If you have PSU's randomly disappearing from your Titan then you have some burglary you should check into =P

On a more serious note, are you referring to dies which eventually stop hashing and a power cycle is needed to bring them back?
If so, then yes, that was the first thing I addressed when I bought my Titan, just to see if I could issue power cycling of the dies as needed, automatically.

That was one of the reasons I started writing the firmware mod, once I found out this was possible a whole galaxy of cool ideas were born and thats what my firmware is today =)

So, my firmware will power cycle the DCDC's of a cube when a die on that cube is detected as being "sleeping, dropped off, stopped hashing ... whatever you wanna call it" ... so far, taking into account peoples success w/ my firmware. Id say about 99% of the time my firmware brings those dies back hashing =) .. it works flawlessly 100% of the time on my titan.

If theres a true hardware problem w/ ur titan tho then of course my firmware cant do much bout that =P

Check out all the features of my firmware here: http://gentarkincustomtitan.pcriot.com

I just read my site and seems I didnt have that clearly stated in my list of features of firmware. I stated it in paragraphs above it but I can see how that can easily be overlooked. So, I just tweaked the list and wording a bit =)


Oh wait wait, I just reread what u asked. Are you talking about one of the DCDC's disapearing for a respective die but the die continues to hash?
If so, to answer that, my firmware on its current release does not address that problem. Its rare and I didnt catch it for a long time.
Sometimes when it does that it will drive the single remaining DCDC as hard as it can and pulls near 50-60A through the poor thing =( ... eventually the DCDC will simply just shut itself down because these DCDC's do have overcurrent protection & overheat protectio(both extreme cases) built in. If the DCDC doesnt entirely shut itself down it will go into a current limiting mode where it will give the ASIC all the power it can but in a very spurty manner, so the ASIC can hash at roughly just over half the speed(half the output from the ASIC will be HW errors) while the DCDC can remain powered on.

The next release my firmware will catch that condition and it will power cycle the affected ASIC and bring both DCDC's back online(given that one of the DCDC's arent permanently damaged).

Yes, they work fine if you load the correct firmware.

The controller never changed between Oct and Nov hoopiter.

For future reference, Searing has no clue, he just likes to hear himself talk and get his advertisement/sig more posts.
I would also point out that he easily could have a clue.
He has been given answers to most of the current questions but he is too busy talking to listen.

YMMV