Quote from: jimmyD30 on Today at 11:39:23 PM

Quote from: kerney666 on Today at 11:17:15 PM

Quote from: jimmyD30 on October 13, 2020, 02:14:24 PM

Quote from: cornish_will on October 13, 2020, 01:47:14 PM

Quote from: jimmyD30 on October 12, 2020, 10:42:38 PM

Hi, does anyone know what this error is all about - Vega64 rig, trm 0.7.13.

'Err, cmd 000000000000000000'

last update?

Yes, v0.7.13

Ha, seems that is an error printout from the API that wasn't really expected to be hit (ever). Someone/something is sending a bad command over our API. What is connecting to port 4028 on your rig?

Otherwise, did you ever join our discord? Plenty of people there including myself who can have a go at your getting your Vegas going. Our support here is very limited these days, and I also don't think it's the best place to switch to a DM session, drop you a test build directly in our chat if necessary, etc.

Also, for the record, don't believe all the bs some users are posting. The only money exchange between us and Discord is me having to pay for a Nitro membership to even be able to post our (large) release files in the discord, and that's that.

Ah, I’m using Rig Cards for info reporting, might be that, thank you!

Any idea why miner (v0.7.13) sometimes shuts down on Vega64 rig (see details a page or 2 back)?

I do not, and I can't say I've seen any error reports around that topic that would indicate we have some general issue. I'd love to try and help you sort it out though. First thing would be to ask you to add a log file (unless you already have it) by adding --log_file as a command line argument. It'll write a file trm_ethash_yyyymmdd_hhmmss.log in the miner directory. Then it'd be great if I could get hold of it when you have a crashed/failed instance. Again, imho discord is easier for a 1-on-1 process, dumping log files in the DM chat etc, but you can also dump the file somewhere on the net and send me a link, it's totally up to you.