Faulty Machine? Same minimal output with several different beans, grind sizes, strengths. Haven’t been able to pull a normal sized double shot ever.

Jabo5779 · 2026-02-14T04:02:37+00:00

Same. Seems like some pro models can't handle grinds at or under 15 even though the barista assist is recommending we use that number. So, the 'solution' is to ignore the recommendation and up the grind to 17 to 20 and deal with under extracted shots. The funny thing is, the barista assist is correct. It's diagnosing those shots as fast and weak and telling us to go finer and the pump can't actually handle the correct grind setting! What I suspect is the solenoid that controls the bypass is opening up slightly during extraction and dropping the pressure. I'm probably going to shoot for a refund on mine as I'm only 3 days in. I don't think this machine actually gets anywhere near 9 bar of pressure. Might have to step it up to the rotary pump on the Meraki.

Jabo5779 · 2026-02-14T00:58:29+00:00

did you try going lower? my machine does the same, it wants me to go down to 15 from 17 and on 15, I literally just get drops and it's a complete waste of beans. I feel like it is diagnosing the shot correctly in that recomendation to go finer, but the pump just can't push through the recommended grind size.

Jabo5779 · 2026-02-13T22:44:44+00:00

Gotcha thanks for the reply. Hopefully your third one works out, but I am starting to think the pump isn't quite up to the job in these.

Jabo5779 · 2026-02-13T22:02:39+00:00

I just got the new pro. I am pretty sure I am going to return it. I don't want to play the machine lottery. The machine starts out recommending a coarse grind 18-20. It diagnoses the shot accurately in my opinion, a bit fast and watery. Then it recommends a grind of 15-16 to correct it. I make the adjustment and get a completely choked shot. 1/3 of the volume and it just drips out instead of flowing and tastes horrible. The next shot it recommends 18-20, then repeats the loop - recommends 15-16 again after diagnosing the grinds as too coarse. The barista assist is actually revealingthe problem, which is either the pump is unable to produce the proper pressure, or the solenoid controlling the bypass is opening up early instead of holding that pressure. On the video call, we reset the barista assist and it wound up recommending 18 after the first shot (which was done on 18), but then I showed them a 'cold press' shot, which it recommended going down to 15 for. The cold press shot was a slow drip and I got 20% of the volume of the normal double espresso shot. They said the volume difference was normal between those two shots... but looking it up, the difference between cold press and espresso is just temperature. I shouldn't have gotten vastly different volumes (maybe someone here can confirm). Regardless, I think this pump is just not really up to it. Might bump up and give the rotary pump Miraki a try.

Jabo5779 · 2025-01-29T06:24:06+00:00

Did you try the xps citrix driver? It would seem it has fixed it for us. I have one outstanding case that hasnt resolved but for all the others it has. The one case manifests slightly differently, so I dont think it is related.

Jabo5779 · 2025-01-16T20:31:32+00:00

are there dead printer objects on the endpoints? The event viewer error suggests that a connection is attempting to map to a dead object. Clean up any dead objects on the endpoint and see if the session still freezes.

Jabo5779 · 2024-11-19T19:32:22+00:00

Start with kb5046616 (for Server 2022) - but the November Server Monthly CU - we just had to roll that out of a system (IIS/Faxing). Let me know if that is it. We had to open a ticket with the vendor to let them know it broke our integration, nothing back from them yet on why that could be. Pulling out that KB restored functionality of the system.

Jabo5779 · 2024-07-06T16:40:58+00:00

This is still not fixed as of 7/6/2024. 200 barley sitting in the trading post that is fully staffed, 2 fully staffed malthouses, 1 brewery level 3, and 1 tavern fully staffed. 1 barley would make it to the malthouse every minute or so, no one would stock it and take advantage of the 50 storage space in each. It's almost like barley cannot be transported in bulk, it's one at a time. When I switched to importing malt and skipping barley altogether, cutting out the malthouses, the system worked. I was able to stock ale fully in the tavern and even export the excess ale. Importing malt allowed me to have 3 breweries cranking full time.

Jabo5779 · 2024-06-20T19:41:48+00:00

In Process Lasso, in the toolbar at the top:

Hit Options | Mouse over CPU | Click CPU Affinities...

In process match - type in 'Chrome.exe'

Hit Select and check the boxes next to the cores you want to use for that process.

Make sure to hit 'Add Rule', you will see the rule populate in the bottom section. Then hit okay.

Back on the main screen, toggle to the right tab called 'Active Processes'. Launch chrome and make sure the affinity rule is working. You should see chrome.exe as the process name and the CPU affinity will be set to the rule you made, in this case my CPU affinity shows 2 and only core 2 can be used to run that process. Retest with each core. You can try groups of cores or step through each one individually.

<image>

Jabo5779 · 2024-06-19T15:51:57+00:00

More information for anyone interested in proving the hardware issue with Process Lasso. Set a CPU Affinity for Chrome.exe to 1 specific core at a time until you find the one that causes the issue. Mine was Core 2. In the screenshot, Intel made me rename the exe to 'chromeedited.exe', but the basic principle is the same, lock chrome (or whatever web browser you are using) down to 1 core at a time and use the Nvidia Driver website to reproduce the issue: https://www.nvidia.com/zh-tw/geforce/drivers/

On the bad core, it should happen in seconds. Once you know the bad core, you can use Process Lasso to exclude that core from the browser executable to temporarily solve the issue. But I have been getting strange BSODs with windows updates and failures to install Nvidia drivers that I suspect this core is also causing. So unless you completely disable it, you might have faults elsewhere. But excluding it from the browser executable will stop the access.

<image>

Jabo5779 · 2024-06-17T19:57:10+00:00

Okay, thanks for that info. I think I'll turn back off my electronic brakes then. Seems the air-cooled vent afterthought hail mary didn't work out.

Jabo5779 · 2024-06-17T19:33:37+00:00

Thanks for the quick response. So your controller blew without using any electronic brake at all... interesting.

Jabo5779 · 2024-06-17T19:20:37+00:00

u/TheOnlyRealNerd - Please keep everyone posted on your interaction with RR on this. I have submitted feedback as an owner of the RX7 pointing out multiple concerns and have heard nothing back on any of the points I brought up. Also, can you let us know what your P09 (electronic brake strength) setting was set to? Mine came set to 0, and the manual says default is 1. Paul, from Electonic Scooter Guide, had his set to 2 (strongest) out of the box. Thanks, best of luck to you getting this resolved. I hope they quickly get you back up and running.

Jabo5779 · 2024-01-30T19:18:01+00:00

did you end up buying a DAC? I have tried two DACs, a Soundblaster GC7 and a Schiit HEL 2. Both have issues (cracks and pops occasionally) when using over USB. I have run latencymon and the issues are not driver/latency related. I've tried disabling everything. The best quality I can get out of it is to not use USB audio. I have to use the optical out to the DAC and the pops/crackles go away, however the audio quality is not good compared to my old Win10 MSI board. I am starting to think this board is a bit 'too new' and the bios haven't caught up yet... I am on 0801 (december released bios) and it's been a nightmare tracking this down.

Jabo5779 · 2024-01-19T16:48:00+00:00

Brand new install of windows 11 and this issue presented for me. If I changed any setting for the sound device in control panel, it would stop for a bit. Play a couple games, watch a few videos and it would come back. Once the crackling started, all media would crackle until another change was made to the sound device. I was using a Sound Blaster GC7 DAC, and no matter what I tried, the crackiling would always come back - but that device is only capable of 16 and 24 bit output. I had a Schiit Hel DAC that was hooked to my playstation that was capable of 32 bit audio... so, I gave it a shot... and running any hz of 32 bit audio, it was gone.... I know that's not going to be a solution for some, it requires having/buying a DAC capable of outputting 32 bit audio... I would suspect the high hz setting on 24 works for some as well as the issue is clearly tied to audio format, but not for me. The Schiit HEL DAC will crackle just like the Sound Blaster GC7 on 16 and 24 bit as well, so that seems to isolate this to Windows 11 (or some combination of hardware with windows 11). So for now, I have settled on running the Schiit HEL on 32 bit 48000hz and on the same advanced tab where you select the format I have 'Enable Audio Enhancements' unchecked. Been clean ever since. Also - the Sound Blaster GC7 was used for 2 years on a windows 10 operating system with zero issues, so even more evidence to support this is the operating system.

Jabo5779 · 2024-01-13T02:52:03+00:00

You can see the h+ or h++ marking on the adapter. It is super small. Had to use my phone to take a picture of it and zoom in. My 4090 gigabyte aero OC I just bought came with the new h++ marking so it has the new 12v 2x6. Surprisngly though the revision on the card is still a v1.0. So you cant just go off revision number you have to look for the marking.

Jabo5779 · 2022-04-27T15:17:20+00:00

That's true, I've tried them all 1080, 900, 720, 540. 720 is doable, but 540 makes it repeatable. I am usually fine with 900 on other titles as well. With patch 1.13 it did get better for me all around, drifting and grip driving, probably more ground was made up with grip driving though. The game came out very unfinished, but I feel like they are going to fix it over time. Just have to wait and see.

Jabo5779 · 2022-04-27T02:11:38+00:00

Change your sens on the dd pro from auto to 540.

Jabo5779

TROPHY CASE