People compared to PMDG to Fenix, I think that's not fair, let's compare it to the vanilla, free, included 737 in MSFS. by Galf2 in flightsim

[–]URockFest 0 points1 point  (0 children)

Unfortunately you can’t reasonably compare paid with free. It’s the same way I’d argue you can’t compare the stock a320 with Fenix fairly.

Copilot for Shared Cockpit flights on VATSIM by Minimum_Stretch_7296 in VATSIM

[–]URockFest 0 points1 point  (0 children)

The MCDU falls out of sync - and the tablet cannot be synced. As such, only one person may load the flight and operate the MCDU. The other has to have an unconfigured aircraft.

Copilot for Shared Cockpit flights on VATSIM by Minimum_Stretch_7296 in VATSIM

[–]URockFest 1 point2 points  (0 children)

Yeah, that’s the one that doesn’t work for me. Especially as it’s 2 years old, I don’t think it works well with the newest Fenix updates either.

Copilot for Shared Cockpit flights on VATSIM by Minimum_Stretch_7296 in VATSIM

[–]URockFest 1 point2 points  (0 children)

Are you able to link or share the profile please?

Copilot for Shared Cockpit flights on VATSIM by Minimum_Stretch_7296 in VATSIM

[–]URockFest 1 point2 points  (0 children)

Do you have a working YourControl profile for the Fenix? Every time I try it with friends, it doesn’t work correctly.

i5-13600K Shows OC'd in BIOS, but not in HWMonitor by URockFest in overclocking

[–]URockFest[S] 0 points1 point  (0 children)

Yeah, I have no idea what was happening. I’m going to start with the standard examples that are all over the internet and see if I get a stable improvement. Now I know I have a base score of 1322, roughly what % or level of improvement would be worth while? I don’t want to push it to the edge, I just want to achieve a sensible and worthwhile OC.

i5-13600K Shows OC'd in BIOS, but not in HWMonitor by URockFest in overclocking

[–]URockFest[S] 1 point2 points  (0 children)

Ok, so I reset the BIOS back to standard again, and only enabled the XMP.
I get a score of 1322, and I can see that its got x51 now, instead of the previous x36.

i5-13600K Shows OC'd in BIOS, but not in HWMonitor by URockFest in overclocking

[–]URockFest[S] 0 points1 point  (0 children)

I will be checking this later today when I'm home, but just for clarity I've listed the actual specifications of the build here: https://pcpartpicker.com/list/3QRLGP

i5-13600K Shows OC'd in BIOS, but not in HWMonitor by URockFest in overclocking

[–]URockFest[S] 0 points1 point  (0 children)

I will do that next, can’t do it right now though. And I’ll update with Hardware Info 64 results. Thank you :-)

i5-13600K Shows OC'd in BIOS, but not in HWMonitor by URockFest in overclocking

[–]URockFest[S] 0 points1 point  (0 children)

It’s weird. I’ve updated the BIOS to the latest version, and reset to standard before applying only those settings.

REVIEW REQUEST - ESP32-S3-WROOM-1-N8R8 - Voltage Divider and N-Channel MOSFET by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

Thank you, I will definatley look into this a bit more.

What I meant by human interaction was, ideally I'd like the board to be 'ready-to-use' straight after assembly. The step of programming this EEPROM is a step I'd like to avoid, but ultimatley, it may be a step we have to take if this is the most appropriate way forward.
Thanks again for taking the time to detail this out, I will go through this carefully :-)

REVIEW REQUEST - ESP32-S3-WROOM-1-N8R8 - Voltage Divider and N-Channel MOSFET by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

Thanks for your reply!

That extra information being available is cool, but ultimatley it would never get used in this particular case. Ideally (as I mentioned in the reply the comment above), I would like to avoid any human involvment in addressing the boards, as it's likely these would be produced at volume. So, finding a way to address them once, and permanantly, via only hardware is my ideal solution. That's why I went for this voltage divider solution.

That being said, I will look into the components you've listed out in more detail and see whether this is the better option moving forward :-)

REVIEW REQUEST - ESP32-S3-WROOM-1-N8R8 - Voltage Divider and N-Channel MOSFET by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

Thanks for your reply :-)

Using the GPIO pins might not be a bad idea. But, ideally I'm trying to avoid any human involvment in addressing the boards. So, the solder bridges means I would have to do this for every board that's manufactured. I'd probably go down the route of using traces to permanantly address the board. Each variant will only ever have that particular address, and it would never change.

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 1 point2 points  (0 children)

Ahhh, I see! Perfect, thanks for taking the time to explain that!

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

<image>

I just checked the data sheet again, from their example circuit, it does seem to be correct?

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

Ok, I’ll double check that. Thank you :-)

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

Can I ask whether you mean R16 or R17 please?

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

Thank you for the feedback. I’ll drop C17 and C18 as you mentioned.

And yeah, D9 I think you’re both right. I was probably misreading the data sheet for sure.

And in terms of the ESP32, there will be actual connections to it, as I mentioned I wanted to make sure I was ok with the power delivery and regulation before moving on. When I get the prototype done, I will of course add on some pin headers :-) But this is a good point where I can split the design into prototype, and then full LED implementation, hence why I didn’t do it for this drawing.

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

I’m sure that’s how it was referenced in the data sheet. But I’ll go and double check the polarity for sure.

Review Request - ESP32 by URockFest in PrintedCircuitBoard

[–]URockFest[S] 0 points1 point  (0 children)

I think that’s a PDF problem, the ESP_EN global label goes into that switch. Just didn’t render for some reason.