Tdxminer integration for Hive

@HaloGenius

It is really nice that the system is free up to 3 rigs, but I really think you do need to make a distinction between your paying and non-paying customers. Perhaps some sort of support level agreement would also be beneficial, but it all depends on Hive’s team business development and strategies. As for knowing which miner is popular, i think a look at every pool’s (at least YIIMP style pools) will give you any current popular miner for specific algorithm, here is a look at https://bsod.pw/site/miners and you’ll see tdxminer is on the second one. Lolminer and that entire coin (minexcoin/mnx) which i believe is some sort of a scam anyways, is a special case. A general rule of thumb would be for example that if a miner only supports “one specific coin” then it probably shouldnt be in your list of priorities.

Finally and as far as a am concerned, i dont think the tdxminer was a bad story, for me it was a learning curve and i got to know your system a little better and it shows that we can make HiveOS stronger with the community’s support and input.

@hamednik

Lyra2z, tdxminer - it can be or will be a short story for some coins or not - this is not the main thing.
And in fact, the issue is not only in business, if you are about this. It’s just a fragment or part of something.
With your opinion why we did not integrate the TDXMiner and the opinions of other users about where this or that miner, we came to the conclusion that in fact we rested on the wall of our development. This is a dead-end road. Sooner or later it would have happened.
We start to make changes on this and I’m hope it’s really help to make system more strong and flexible.
Now we make changes on the fly for upcoming release HiveOS 2.0 to be ready for next steps of changes.

@givo i’ve tested your “sed ‘/0.000/d’” addition and decided not to include it in the tdxHelper, if a GPU has fallen of the bus and is no longer hashing, you may want to know which one it is, if you simply remove the the GPU with zero hashes from the trail you are effectively sending one less GPU to the hive api and hive will always incorrectly show the very last GPU to be offline, instead of showing which gpu has stopped hashing. thank you anyways.

@hamednik Fair enough :slight_smile: It would be excellent if Hive could adjust its dashboard presentation of GPUs with 0 hashrate so to make a note of such GPUs at the top of the page where there are numbers of active/inactive miners and GPUs. Because, those are failing GPUs and we need some kind of presentation of that info on one screen. With several pages of miners on dashboard, you need to scroll up and down looking for a failing GPU.

In terms of (in)correctly showing failing GPU - please note (as I have mentioned before) your parsing of a log file is not sorting the result, so it sometimes starts with GPU0 (correctly) and sometimes with any other random GPUxx. Here, part of log file from hive agent where you can see that miner stats show 0 hashrate on GPU5 and 10 secs later on GPU4:

[Tue Jul 3 19:18:27 +04 2018] > {“method”:“stats”,“jsonrpc”:“2.0”,“id”:0,“params”:{“rig_id”:“xxx”,“passwd”:“yyy”,“miner”:“dstm”,“miner_stats”:{“hs”:[2.745,2.745,2.745,2.745,2.745,0,2.745,2.745,2.745,2.745,2.745,2.745,2.745],…

[Tue Jul 3 19:18:38 +04 2018] > {“method”:“stats”,“jsonrpc”:“2.0”,“id”:0,“params”:{“rig_id”:“xxx”,“passwd”:“yyy”,“miner”:“dstm”,“miner_stats”:{“hs”:[2.745,2.745,2.745,2.745,0,2.745,2.745,2.745,2.745,2.745,2.745,2.745,2.745],…

It is not such a big deal, since one can identify failing GPU by comparing temps and power usage among GPUs, but this is one small potential improvement that can be addressed…

@givo I actually looked for this scenario to see if tdxminer is outputting GPU stats in an unsorted list, but what i saw in every instance was the same format which happens to be sorted and shows the correct reflection of what GPU is producing what hash. Here is a copy of tdxminer which i based my parsing on. Check your miner log and you should see something similar.

[2018-07-03 19:28:52] Stats GPU 0 - lyra2z: 3.365Mh/s (3.364Mh/s)
[2018-07-03 19:28:52] Stats GPU 1 - lyra2z: 3.365Mh/s (3.364Mh/s)
[2018-07-03 19:28:52] Stats GPU 2 - lyra2z: 3.365Mh/s (3.364Mh/s)
[2018-07-03 19:28:52] Stats GPU 3 - lyra2z: 3.365Mh/s (3.364Mh/s)
[2018-07-03 19:28:52] Stats GPU 4 - lyra2z: 3.365Mh/s (3.364Mh/s)
[2018-07-03 19:28:52] Stats GPU 5 - lyra2z: 3.365Mh/s (3.364Mh/s)
[2018-07-03 19:28:52] Stats Total - lyra2z: 20.190Mh/s (20.185Mh/s)

In the case of t-rex miner however i noticed that its exactly as you said and GPU listing is all over the place:

[2018-07-03 19:30:35] GPU#2: MSI GTX 1070 Ti, 2796.99 kH/s
[2018-07-03 19:30:35] GPU#2: MSI GTX 1070 Ti, 0.026MH/W, 0.0015MH/Mhz
[2018-07-03 19:30:35] GPU#2: MSI GTX 1070 Ti, 64C(F:48%) 1878/4233MHz(109W)
[2018-07-03 19:30:58] GPU#3: MSI GTX 1070 Ti, 2767.19 kH/s
[2018-07-03 19:30:58] GPU#3: MSI GTX 1070 Ti, 0.025MH/W, 0.0015MH/Mhz
[2018-07-03 19:30:58] GPU#3: MSI GTX 1070 Ti, 63C(F:49%) 1873/4233MHz(109W)
[2018-07-03 19:32:09] GPU#1: MSI GTX 1070 Ti, 2787.37 kH/s
[2018-07-03 19:32:09] GPU#1: MSI GTX 1070 Ti, 0.026MH/W, 0.0015MH/Mhz
[2018-07-03 19:32:09] GPU#1: MSI GTX 1070 Ti, 64C(F:48%) 1886/4233MHz(109W)

For t-rex miner parser (which i havent realsed) i just pipe the log to "sort -V -k 3 " and that deals with the problem. If you think for whatever reason you’re not getting sorted results on tdxminer, play around with the sort command and you’ll get a sorted list.

Noob here. I have a few rigs with mostly Sapphire RX 580s. I am using tdxminer, integrated with HiveOS, to mine two different coins on two separate pools. I am not earning anything close to what the calculators estimated. Any ideas on what is causing this?

@hamednik tdxminer logs are fine and in order. But, when you tail 100 lines - sometimes it happens that this cuts into the middle of portion of the log with GPU stats and then you grep n lines but not starting with GPU0… Also, regarding sorting, first ten GPUs have space between GPU and number (i.e. ‘GPU 0’) while other don’t (i.e. ‘GPU10’) so sorting wasn’t quite doing the job for me. This is why I changed the order of commands in parsing - first grep and then take last n lines since in log they are already sorted.

@MoutainMining I wont take any blame for raising the difficulty :smiley:

Try to use a different calculator that does shorter average timespans which should give you a closer projection on what you should be earning. But realistically you should always consider between 10-20% margin of error on these calculations. Having said that, and without considering your luck on finding a block on any given time span, some pools dont play it fair but its always the case of difficulty levels raising at certain hours to have a noticeable effect on the revenue.

@hamednik Thanks. I have a lot to learn. What are some pools doing to not play it fair?

Just fyi, if someone want to mine with tdx without this full integration, but want fan/temp control, I have made my rigs to mine with claymore but with -li 1500…so really no pressure from claymore, tdxminer miner in shell almost not affected, but I can keep a view of temp and fans from the gui

Прошу помочь найти решение. На одной из видеокарт рига поочередно снижается хэшрейт. Было ли такое у кого-то? как устранили?http://forum.hiveos.farm/uploads/editor/47/qogvnz2ht911.jpg
http://forum.hiveos.farm/uploads/editor/jd/cdtoveglbz5m.jpg
http://forum.hiveos.farm/uploads/editor/7l/4npjfd8xmepv.jpg

attached files are no longer available ?

Use “custom miner” feature - Custom Miner Integration

You can find example of usage on bottom at Wallets page “Custom tdxminer”

just use the custom miner feature, does the same job and less complicated.

can you help me with tdxminer + Hive 2.0 Tdxminer integration for Hive 2.0 ?

Why can’t use tdxminer with arcpool and hashpool? I don’t have custom option with this pool and don’t start with « configure in miner » on pool option.