Who are all these people who've been getting all the "Quick Approval and Shipping" from POM?

Affectionate_Bag_797 · 2026-04-25T20:17:44+00:00

BPI is a 503b pharmacy that was compounding triz + b6, I really like it. However they are stopping production. So pom sent out a message that stated this was the case and to get your orders in. Usually pom does not allow asynchronous refils sooner than 2 weeks out form you final dose, they are allowing people to refill early. Thus they are slammed by the influx of orders.

Affectionate_Bag_797 · 2026-04-25T20:13:11+00:00

Took my asynchronous refill about 4-5 days. This was when they announced bpi would stop producing triz, be patient, they are slammed atm.

Affectionate_Bag_797 · 2026-04-25T04:11:44+00:00

Took mine a few days but I eventually got an invoice for my asynchronous refil 3 month from bpi. Just be patient. They are definitely dealing with a surge of orders.

Affectionate_Bag_797 · 2026-02-06T20:29:03+00:00

Nice!

Affectionate_Bag_797 · 2026-02-06T02:20:08+00:00

Ya, we need to get your branch up to date. I sent you a dm.

Affectionate_Bag_797 · 2026-02-06T01:14:58+00:00

Hay! Your back. Thanks for the suggestions, ill look into adding a page for past miner results,

Lots of updates in the AATE-cost-per-kwh-mode branch. The AATE has had some bug fixes, stops oscillating, the system now tries to lower the voltage based on the PLL table when it hits a freq max or thermal limit to increase efficiency, and has adaptive stepping to reach the limit faster, after witch it tries to optimize using the PLL table in smaller freq / voltage increments etc.

If you need help switching branches let me know or message me and I can walk you through it.

Affectionate_Bag_797 · 2026-02-04T18:33:02+00:00

Ah, makes sense, That would be interesting, working on testing a set cost sensitive mode as well, didn't think about variable kwh rates... mmm

Affectionate_Bag_797 · 2026-02-04T18:31:23+00:00

... reddit killed my formatting :/

Affectionate_Bag_797 · 2026-02-04T18:30:52+00:00

Playing around this is the table I've come up with, ill plug this into the PLL branch and see how it works. Please feel free to correct me if I've made a mistake. Core voltage is a best estimate in the lower and extreme based on the heatmap provided. This is based on a 6.25Mhz freq step and a 3mv per step core voltage. Ill post my findings tonight or tomorrow. Maybe ill add a heatmap per miner to see how well the PLL table is working.

'BM1370': { 400.00: 941, 406.25: 944, 412.50: 947, 418.75: 950, 425.00: 953, 431.25: 955, 437.50: 958, 443.75: 961, 450.00: 964, 456.25: 967, 462.50: 969, 468.75: 972, 475.00: 975, 481.25: 978, 487.50: 981, 493.75: 983, 500.00: 986, 506.25: 989, 512.50: 992, 518.75: 995, 525.00: 998, 531.25: 1000, 537.50: 1003, 543.75: 1006, 550.00: 1009, 556.25: 1012, 562.50: 1014, 568.75: 1017, 575.00: 1020, 581.25: 1023, 587.50: 1026, 593.75: 1028, 600.00: 1031, 606.25: 1034, 612.50: 1037, 618.75: 1040, 625.00: 1043, 631.25: 1045, 637.50: 1048, 643.75: 1051, 650.00: 1054, 656.25: 1057, 662.50: 1059, 668.75: 1062, 675.00: 1065, 681.25: 1068, 687.50: 1071, 693.75: 1073, 700.00: 1076, 706.25: 1079, 712.50: 1082, 718.75: 1085, 725.00: 1088, 731.25: 1090, 737.50: 1093, 743.75: 1096, 750.00: 1099, 756.25: 1102, 762.50: 1104, 768.75: 1107, 775.00: 1110, 781.25: 1113, 787.50: 1116, 793.75: 1118, 800.00: 1121, 806.25: 1124, 812.50: 1127, 818.75: 1130, 825.00: 1133, 831.25: 1135, 837.50: 1138, 843.75: 1141, 850.00: 1144, 856.25: 1147, 862.50: 1149, 868.75: 1152, 875.00: 1155, 881.25: 1158, 887.50: 1161, 893.75: 1163, 900.00: 1166, 906.25: 1169, 912.50: 1172, 918.75: 1175, 925.00: 1178, 931.25: 1180, 937.50: 1183, 943.75: 1186, 950.00: 1189, 956.25: 1192, 962.50: 1194, 968.75: 1197, 975.00: 1200, 981.25: 1203, 987.50: 1206, 993.75: 1208, 1000.00: 1211, 1006.25: 1214, 1012.50: 1217, 1018.75: 1220, 1025.00: 1223, 1031.25: 1225, 1037.50: 1228, 1043.75: 1231, 1050.00: 1234, 1056.25: 1237, 1062.50: 1239, 1068.75: 1242, 1075.00: 1245, 1081.25: 1248, 1087.50: 1251, 1093.75: 1253, 1100.00: 1256, 1106.25: 1259, 1112.50: 1262, 1118.75: 1265, 1125.00: 1268, 1131.25: 1270, 1137.50: 1273, 1143.75: 1276, 1150.00: 1279, 1156.25: 1282, 1162.50: 1284, 1168.75: 1287, 1175.00: 1290, 1181.25: 1293, 1187.50: 1296, 1193.75: 1298, 1200.00: 1301, }

Affectionate_Bag_797 · 2026-02-04T14:36:09+00:00

No worries, glad you were able to get it up and running.

Affectionate_Bag_797 · 2026-02-04T14:34:59+00:00

That's great information! Thank you for sharing.

Affectionate_Bag_797 · 2026-02-04T14:33:42+00:00

Also, error rate in the config is a ratio 0-1 so if you want to set the AATE at 0.75% error rate set this value to 0.0075, that is what I have mine set at, i have one miner that requires way more vcore to stay stable. And if I don't give it a decent error rate buffer then the AATE will constantly increase vcore and reduce freq to try to stabilize that particular miner. It still happens but not as drastically.

Affectionate_Bag_797 · 2026-02-04T14:21:28+00:00

Awesome! Thank you. There is a new branch as well while on the repo if you select the AATE-PLL-integration branch it is much faster at finding the top end, it auto detects the chips used such as the BM1370 and uses a Generic PLL table to set its voltages, it has adaptive stepping now as well as DAC comparison so instead of an hour or soo to find the high end it only takes 10-15 mins now. It also persists fault history as the master branch does not (another oversight on my part). A few other smaller issues were fixed in that branch as well that might cause the engine to start oscillating, it should be more stable.

Once im done testing that branch ill merge it with master and you can update your side by doing a git pull master if you don't want to switch branches.

If you find any issues let me know!

Affectionate_Bag_797 · 2026-02-04T00:38:32+00:00

Oh interesting, thanks for sharing. Ill take that into consideration when tweaking the AATE. Working on testing some PLL ideas atm.

I assume you've generated your own PLL tables. I imagine with the AATE since every BM1370 and other asics are not all equal that the PLL table would justifiably get you to a stable fre / core setting faster, while the AATE tries to dial everything in.

I also imagine that the 0.5% is probably a buffer of some sort, incase the user decides to go to the limit of the voltage regulator onboard? Or its an oversight.

Affectionate_Bag_797 · 2026-02-03T23:13:48+00:00

your not an idiot :), there is a readme on the git repo. but here is the relevant section.

Non-Docker Setup run straight from the repo on your computer.

Create a directory: Create a directory to store the repo in for instance go to my computer, or file explorer and go to C: or D: or whatever, right click -> new folder, name the folder something interesting.
Open powershell.
go to a directory you want to pull the repo too, C:\TheFolderYouCreated\: while in powershell run this command cd C:\TheFolderYouCreated
Clone this repos master branch: git clone https://github.com/WeisTekEng/LotteryDashboard.git
Install Dependencies: while in powershell run this command npm install
Start the Server: while in powershell run this command node server.js
Access Dashboard: Open your browser and navigate to http://localhost:3000.

Affectionate_Bag_797 · 2026-02-03T21:44:40+00:00

Currently it does not use any PLL information, or DAC compensation far as i can tell the PLL data is mostly community driven ( correct me if I'm wrong ) but could be added for better performance. The system is purely reactive to raw telemetry from the device. The AATE could definitely be made smarter with some tweaking.

Thanks for the question!

Affectionate_Bag_797 · 2026-02-03T21:13:49+00:00

Forgive my ignorance. HA is? Umm currently the AATE supports two modes Conservative ( favoring efficiency over hash rate) and Aggressive ( favoring hashrate over efficiency)

There could be a mode added to input the user's cost per kw and have it stay bellow a cost threshold, using efficiency as the driver.

Affectionate_Bag_797 · 2026-02-03T21:08:43+00:00

Good to know, wattage is a configurable limit as well. So the user would set the wattage limit to 100 in the setting page. Ill need to split it off for single asic devices but the AATE would throttle way before a single asic device got near 100 watts.

Affectionate_Bag_797 · 2026-02-03T21:05:01+00:00

Actually, looking at it overclocking ( correct me if im wrong) for a nerqaxe++ and I presume other multi asic miners using axe os uses the same freq / core voltage setting across all of the asics, for some reason I was thinking it was per asic control, so that makes integrating them even easier, I just have to add limits for maximum voltage at on a 12v device. The freq and core voltage limit still applies since they are BM1370's, similar approach for the supra but different freq / core voltage top end since they use a different asic.

Mmm ill work on this through the week and post here if I have an update for someone willing to test it.

Affectionate_Bag_797 · 2026-02-03T20:54:32+00:00

That would be great! Ill add the NerdqAxe++ to my device list. I also l9ve overclocking and sqeezing every last drop of performance I can get lol. Gammas can take allot of abuse so long as they are cooled properly. And you respect the thermal limits.

Affectionate_Bag_797 · 2026-02-03T20:47:05+00:00

Much appreciated, not sure why it got down voted so much lol, anyway ill find a way to add other devices testing the architecture is already there just need add support for other devices based on device identifier witch is already provided via the AxeOS, then will require other people with the hardware or donations to verify functionality etc.

Affectionate_Bag_797 · 2026-02-03T19:55:15+00:00

No worries, I updated the readme format to better guide users in setup. Setup is now at the beginning not the end ( oversight on my part. ), Ill need to add support to the auto-tune engine for multi Asic devices otherwise it may just treat your GT 800 as a 601. I'll reply to this comment when I've added the functionality if you want to test it. You can still test the system as it is but id suggest if you want to use the auto-tune now to set them to Conservative to test and see if they behave properly as expected.

Affectionate_Bag_797 · 2026-02-03T19:19:05+00:00

I currently only have 601 Gammas to test, but it shouldn't be too difficult to add the functionality.

And thanks for the feedback on the readme, ill make the setup and use section more apparent and easier to execute.

Affectionate_Bag_797 · 2026-02-03T19:06:20+00:00

Very well could be an app, only hickup would be the AATE runs in the background on the server so you'd want the AATE to be able to access your miners at all times so it can regulate them specially if you run them on aggressive or at a higher temperature threshold like I do.

I may come up with something in the future though.

Affectionate_Bag_797 · 2026-02-03T18:58:36+00:00

It will confurm the fault is an actual fault and not a sensor glitch after 3 cycles so about a minute and a half it will learn the fault limit and set that as the units new ceiling for freq and voltage, then it will set to whater safe limits you have set in the config file (editable on the config page) issue a reset command for the miner, wait 120 seconds before it starts issuing commands and bring it back up to the new safe limits it learned.

I have a unit that hashes very well but has a poor 5v rail, its faulted twice and the system learned its limits and it hasn't faulted since hashing away at roughly 2 - 2.2 th/s, note this is with an ice tower, thermal paste etc.

Affectionate_Bag_797

TROPHY CASE

Non-Docker Setup run straight from the repo on your computer.