background

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Buy bitcoins anywhere in the world at localbitcoins.com

Buy Monero at local Monero

Trade BTC for Monero at AgoraDesk

Use Anonymous Ads
Use Anonymous Ads

API Output

edited February 2014 in General
Hello,

It seems the API Output window is not reporting the correct number of accepted and rejected shares in the respective "Accepted" and "Rejected" columns. Instead those numbers appear in the "Diff. Accepted" and "Diff. Rejected" columns. Am I understanding the API output correctly?

Comments

  • Accepted/Rejected is a measure of shares, diff acc/rej is showing the difficulty range of the shares your miners are accepting - does that make sense? 
  • edited February 2014
    The Accepted/Rejected number of shares is what you see next to the MH on the top of the miner window? Correct? If so, those numbers are not those being reported into the API Output Accepted and Rejected Columns. The share numbers are reported in the Diff. Accepted/Diff. Rejected columns. In other words, the difficulty and the number of shares have been inverted in the API Output!
  • That's really weird. Can you email me the text part of the API Output window please?
  • For everyone else - it's a bug in the maxcoin version of cgminer, for accurate readings please check the API Output window!
  • Oh, so the correct number of shares are the ones in the API output, not the ones on the miner window. Too bad... :D
  • A few more issues re: the API Output window.

    Minor: the sorting mechanism is incorrect for the numeric columns (e.g. 7351 is considered > 180000 because 7 > 1).  Having the ability to right-justify numeric columns would be nice, too :)

    A more serious issue in my case is that the temperature value reads incorrectly for my Avalon devices, despite the fact that it reads correctly in cgminer's API output.    In the cgiminer API log it reads:

       [temp1] => 27
       [temp2] => -1
       [temp3] => -1
       [temp_max] => 27

    wheras MacMiiner's API log merely shows:







      [Temperature] => -1.00

    For devices like the Avalon that have more than one temperature sensor, there needs to be a way to specify which sensor to use if MacMiner is only going to display a single value.  Cgminer makes all of them available in its output, but MacMiner seems to be arbitrarily choosing temp2 or temp3.

    Lastly, for the suggestion box, it would be nice to have a summary row at the bottom of the API Output table to show the totals for the various columns.  Better yet, why not have a single mini-window that shows the aggregate hash rate, just like you do for all the other miner types (CPU, GPU, FPGA/ASIC, etc.)?

    Thanks for the networked miner features, btw--they're definitely nice now that I no longer have my miners directly connected to my Mac :)


  • can you post the whole section for one of the avalon units from the text output of the API Output window please? I'll have it read all that aren't -1! I'll take a look at the sorting too, and totals are definitely on the cards soon. What information would you like in a separate window?
  • This is what cgminer's API log offers for the Avalons:

    [STATS0] =>
    (
       [STATS] => 0
       [ID] => AVA0
       [Elapsed] => 33630
       [Calls] => 0
       [Wait] => 0.000000
       [Max] => 0.000000
       [Min] => 99999999.000000
       [baud] => 115200
       [miner_count] => 16
       [asic_count] => 10
       [timeout] => 9
       [frequency] => 1400
       [fan1] => 360
       [fan2] => 360
       [fan3] => 360
       [temp1] => 27
       [temp2] => -1
       [temp3] => -1
       [temp_max] => 28
       [Device Hardware%] => 3.2601
       [no_matching_work] => 17497
       [match_work_count1] => 108083
       [match_work_count2] => 107489
       [match_work_count3] => 107789
       [match_work_count4] => 107863
       [match_work_count5] => 107595
       [match_work_count6] => 108215
       [match_work_count7] => 65
       [match_work_count8] => 107227
       [match_work_count9] => 29
       [match_work_count10] => 21522
       [match_work_count11] => 107711
       [match_work_count12] => 107770
       [match_work_count13] => 107195
       [match_work_count14] => 107740
       [match_work_count15] => 107814
       [match_work_count16] => 107629
       [Controller Version] => 0
       [Avalon Chip] => 55
       [USB Pipe] => 0
       [USB Delay] => r0 0.000000 w0 0.000000
       [USB tmo] => 1854398 0
    )

    MacMiner's API Output for that device is:

    [ASC0] =>
    (
       [ASC] => 0
       [Name] => AVA
       [ID] => 0
       [Enabled] => Y
       [Status] => Alive
       [Temperature] => -1.00
       [MHS av] => 177892.77
       [MHS 5s] => 184340.32
       [Accepted] => 8778
       [Rejected] => 5
       [Hardware Errors] => 38947
       [Utility] => 18.91
       [Last Share Pool] => 0
       [Last Share Time] => 1393410989
       [Total MH] => 4953458795.7680
       [Diff1 Work] => 1153324
       [Difficulty Accepted] => 1151424.00000000
       [Difficulty Rejected] => 640.00000000
       [Last Share Difficulty] => 128.00000000
       [No Device] => false
       [Last Valid Work] => 1393410991
       [Device Hardware%] => 3.2666
       [Device Rejected%] => 0.0555
       [Device Elapsed] => 27845
    )

    As far as the temperatures go, I'd be interested in the highest of the available sensor readings I suppose (the -1 readings are from empty sensor sockets, obviously).  The data I tend to want to see at a glance are hash rates and temperatures.  With multiple miners it would be great to have an aggregate figure for the hash rate--something to keep in a small window in the corner of the screen, perhaps, possibly with a little alarm for when the aggregate hash rate drops below some configurable threshold.
  • Hmm, that's odd - what command are you sending the cgminer API to get the first output? 
  • Hmmm...it isn't cgminer's output.  It turns out that's the output of a CGI app called 'luci' that Avalon includes in its web app suite.  The menu heading reads "Cgminer API Log", but the details it returns are not the same as I get from a "summary" or "devs" API call to cgiminer.  I'm beginning to suspect that I'd have to hack Avalon's patch to cgminer to get it to set the temperature variable correctly.  I'll see if there's a newer firmware release that might fix that.
  • Ah, that's interesting - is that data just on a web device interface page? That could probably be parsed. Unfortunately I don't have an Avalon to test it with though!

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file