From the release notes: "This update fixes a few bugs and adds better support for multiple sticks on a hub. The update is recommended for everyone since it adds much needed low level restart logic."
>> I have no problem running the older version when a higher current supply is used on the hub.
Me neither, until the odd moment one MLD stops, or, for some reason, they all stop. Which has happened to me once every few days. I cannot babysit these units all the time, so being able to run them unsupervised for a long time without is very very useful.
>> Getting around 5Mh per x 5 and running at 876 in BFG miner bat file, extra usb fan for cooling.
Same here. Note that hashrate = 5.66 x clockfrequency, so 876x5.66= 5Mh/s (if all cores are working). I had to trim the core voltage a bit more compared to my previous 832Mhz. I tried first 856, then I got a bit more HW errors, then 876 and a lot more HW errors (>> 1%), that gave me an idea how much to change the core voltage pot. Now it is steady at just below 1% error rate. I have got two small but powerfull USB fans blowing on them, keeps them cool. I have 6 units, and 5 more on their way (thanks to jstefanop for finding time last monday to ship them over!!!).
With ~11 MLD2's one reaches (imho) the limit of what makes sense before it is time to move up the big step to an Antminer L3+, these are about 3x more costefficient (MH/unit_cost). With the expected increases in hashing power over the next 6mo, returns will fade fast (unless the price of LTC goes to the sky).
Great thanks for the info, do you actually measure your core and memory voltage on the board?
I just turned the Core voltage pots up a bit to approx .82 as per the photos at begging of the thread
and the Mem left as we got them.
I would like to know the settings for 5.7Mhs, Core and Memory settings and BFGminer Freq?