When did we hire the engineering firm to help with the RTL code? What month, clearly we were doing test on w/e we had back in November so what happened between now and then? Did we wait till January to hire the team?
I'm fairly sure that the engineering firm was being sorted out in late Aug/early Sept but we left before it had been finalised. I think they were named but I don't remember those details. At the time, VBS thought they were fine from what we'd been told. That's why I'm so surprised to hear about problems this late. The boards should have been reasonably easy jobs, I'm told, for an experienced firm, perhaps except for the largest one.
We did have an issue was the 256 board as it was high risk due to the size, cooling etc. Ken was adamant it would be ok but we thought it not a sensible risk to take. We felt the overall product offerings could and should have been improved substantially. Ken did choose to make some minor changes.
We had actually designed completely different set ups, commercially much more viable & appealing, significantly cheaper to manufacture, more flexible, and much lower risk all round. Ideally we'd have dropped the 256 board altogether or reduced it by a few chips. Our options didn't include the expansion unit set ups - they didn't make economic sense and were detrimental to all products in our opinion. Ken disagreed and it's his business after all. I'd be interested in knowing how many expansion case set ups were ever paid for, particularly at the top end, and the profit margin on those sales (if any).
We weren't told anything different about code/engineering than you guys. Apparently Ken had done it all as required for the chips but at the time we quit he was spending time on the 'boost' technology. We did not believe it made sense and I'm still doubtful. Besides, we definitely thought it a bad spend of time considering everything else that needed doing and the lack of qualified staff in the company. That meant Ken was responsible for everything. Even if he were a brilliant polymath, that was not a good situation for a business. When we quit, only a few weeks after we started (it was about 4 weeks in total), we urged Ken in private and in public to hire people in.
I have told people on IRC since then that the product side wasn't where money would be now but that the mining side could still be wonderfully profitable. However, I have never known anything about Ken's mining plans beyond what he has posted in public.
The 'boost' technology I won't discuss because Ken would not wish me to. Note that he never told me what it was in the first place, I sussed it out. I'm also not under NDA about that or anything else.
All in all, ActiveMining could still do really well if it could get mining in bulk ASAP. That's why I think Ken should be a lot more up front about what's going on. I simply don't understand how this situation has arisen. Having eASIC on board was a real coup for which Ken deserves a lot of credit, but it's no good if there is no end result.
Was it because of the large board requirements?
Did Ken's code not run as required?
Did the experienced engineering firm completely screw up and if so then is there legal action in progress? When was the screw up known about?
What is the target date for mining and how much will there be initially/how much will be added per week?
What is the target date for deliveries to customers?
How many units actually went out and how come that was managed yet the current situation has arisen?