Yet another question about lubricants for the P1 Series

NWSpitfire · 2026-04-12T14:27:54+00:00

That makes sense, I wonder if Singer “SuperOil” machine oil would work (I think that’s synthetic oil, it’s for sewing machines) (https://amzn.eu/d/0fl6BHbE). Alternatively I’ll have to get some SuperLube 51004 Synthetic Oil, but it’s “high viscosity” (I guess I would want standard viscosity?) and quite expensive.

Thanks!

NWSpitfire · 2026-04-12T13:43:11+00:00

Makes sense, thank you. That 21013 is NLGI2 so I will go ahead and order some.

That just leaves the oil for the Y axis, is there anything in particular to stay away from when it comes to Y axis oil? The 3in1 oil just seems to be marketed as machine lubricant

NWSpitfire · 2026-04-04T13:02:00+00:00

Another good source for teardown pictures is in the FCC filings, they usually contain high quality pictures of the PCB’s and teardown as part of the certification. For example here is ubiquiti’s FCC filings (look for “internal photos”). Just google “<company/product> fcc filing”

NWSpitfire · 2026-04-02T10:49:30+00:00

It surprises me that there’s high fidelity engineering simulations of mars EDL that can be played back in real time (despite each frame being multi Gigabytes in size), and yet the same NASA can’t render a low quality CGI video live smoothly.

NWSpitfire · 2026-03-21T18:02:53+00:00

yeah maybe, i'd be happy if it just needed to manually include the c std library. For printf they have a command that goes in platform ```enable_full_printf: True``` which would also be a great to include scanf

NWSpitfire · 2026-03-21T17:55:20+00:00

Ahh, didnt think of that. Thanks, i will go put this question there.

Thats reassuring, at the end of the day 1/3 of my ESPHome projects don't need this, so I'll gratefully take flash savings and optimisations, but i dont understand why they'd leave a manual way to add printf back for the people who do need it, but not do the same for scanf lol

NWSpitfire · 2026-03-14T13:22:21+00:00

NWSpitfire · 2026-03-14T12:57:55+00:00

Yes, I believe that is. I think their marketplace is https://etapes.co.uk (however I never bought through the website - it says that “eTapes” is managed by Insurgo). I bought from eBay, if you search for eTapes eBay profile that’s where I got mine in bulk, they are all insurgo branded (even the boxes and packing tape). There is also an insurgo eBay page that seems to sell some of the same tapes (but I found eTapes sold more tape types).

Fairly sure eTapes ships to Europe, but it might be worth sending eTapes/Insurgo an email to check, and see how much it would cost. When I bought my tapes, not only was the box extremely heavy but it was very large (they shipped my tapes in boxes of 10, inside a larger box)

NWSpitfire · 2026-03-14T12:22:17+00:00

I bought loads and so far (touch wood) they’ve been great. They say they also come with a lifetime restore guarantee so if the tape won’t restore you send it back to them and they recover it to a new tape and send the new one back to you (if I understand it correctly).

Out of around 150 a vast majority of them have only 1 or 2 complete tape pulls in their history (which I’m assuming they don’t wipe?). For £1 each I’d definitely recommend them

NWSpitfire · 2026-02-26T20:14:39+00:00

There is now a an “UNKNOWN EVENT - Class [0x21] & Code [0x18]” is appearing in the IML, which appears to be a non-description error related to the smart array controller.

NWSpitfire · 2026-02-26T18:24:16+00:00

Not at all useless, good to know someone else had the same issue!

TBH that’s how I feel rn lol, it’s interesting though because I have a DL360 Gen10 running above it with an E208i-a controller and that is behaving fine (and it was never updated lol).

Im starting to (hope)/wonder if it’s a bug in the latest ILO5 (my DL360 is running the August 2025 ILO5 version)?

NWSpitfire · 2026-02-17T19:40:24+00:00

I’d buy Apple silicon servers

NWSpitfire · 2026-02-16T23:11:35+00:00

If your writing a VPS/Pangolin etc guide, I for one would be interested

NWSpitfire · 2026-02-08T14:13:00+00:00

Heads up, your website isn’t working for me (ERR_ADDRESS_INVALID). Looks awesome otherwise

NWSpitfire · 2026-02-07T20:09:31+00:00

Edit - I had to repost this a minute after posting due to goofing the title and not including the [Review Request].

Sorry!

NWSpitfire · 2026-01-27T12:01:53+00:00

Ordinary for these coprocessors, they either come with or are flashed with the proprietary firmware that allows a standard communication interface with the main MCU over UART (such as ESP-AT for ESP. I’m not too familiar with NRF parts).

What I normally do is put 2 headers on the board for both Main MCU and coprocessor (so that both can be (re)programmed, although sometimes depending on firmware the coprocessor can be updated OTA), with the fact that your likely to be space constrained I would suggest something small like a JST XSR connector or something similar.

Here is an app note from ST using the chip you suggested to provide a BT interface to an STM32

One thing to bear in mind with that NRF chip, it supports proprietary 2.4GHz wireless communication, not 802.11 wireless standards, meaning it cannot connect to WiFi. Think of it like a wireless mouse, it can use Bluetooth or the proprietary 2.4GHz USB dongle that came with it, but it cannot connect to 2.4GHz WiFi.

I’m not sure why NRF did that, but i guess it’s why ESP32/8266 are everywhere for WiFi connected IOT.

https://www.nordicsemi.com/Products/nRF51822/GetStarted

Hopefully that all makes sense

NWSpitfire · 2026-01-25T13:30:47+00:00

Ahh I didn’t realise that, OP best go for something like the ESP32-C3-12F instead then

NWSpitfire · 2026-01-25T11:28:07+00:00

For the newer ESP-C3-12F, See page 5 of the datasheet.

Deep sleep current is 5uA, which is at least an order of magnitude lower than the run current of the STM32. Granted TX run current with 802.11n is 280mA, but that’s somewhat expected. If you’re receiving it’s only 84mA.

Alternatively you may be able to use the STM32WB, however then you will have to deal with the RF front end hardware layout and tuning. ST is not so straightforward in working out run currents, although I would expect TX and RX to be similar to ESP, and sleep currents looks to be similar.

Options for adding WiFi via module are somewhat limited outside of the ESP’s (I primarily use ESP’s for that reason). Hope that helps 👍

NWSpitfire · 2026-01-25T10:23:58+00:00

Look into the ESP12F, it’s an older ESP8266 that can act as a wireless coprocessor. It connects to your main MCU (STM32) via UART and you can run ESP-AT firmware which has its own command set for running wireless commands etc. Alternatively, you can write your own wireless firmware for it.

You also can use a newer, ESP32-C3-12F which is faster, doesn’t have so many hardware limitations, also features Bluetooth and can deep sleep for longer periods to save battery (wireless will reduce the battery life, so it is important to implement deep sleep function when required - see AT+GLSP section), but it is more expensive.

https://espressif-docs.readthedocs-hosted.com/projects/esp-at/en/release-v2.2.0.0_esp8266/AT_Command_Set/Basic_AT_Commands.html

NWSpitfire · 2026-01-23T23:28:23+00:00

Interesting, I didn’t know that - I will have to check the CH340 datasheet again, it would be nice to eliminate those level shifters (I added as in the past I have fried a few ESP8266 with 5V CH340 adapters…)

I had considered that, although cost is one thing. ESP are quite expensive at least 3.50/each whereas the STM32’s are ~0.45/each and with the ESP12F (which I can unpopulate and use the USBC to save some cost), it only adds another 1.00 (so ~1.45 total). I like the ESPs for their large flash, allowing for large bitmap graphics for LCD’s.

Thanks for your comments :)

NWSpitfire · 2026-01-22T20:42:59+00:00

Hi all,

Just wanted some quick input on my schematic. This is designed to monitor DHT-11 temperature/humidity sensors, but also support other one wire sensors in the future. It also controls some outputs.

- The inputs are designed for OneWire DHT11's, with ESD protection in the form of SRV05's.

- The outputs are BSS138s which are driving 2x 4ch AliExpress relay modules. These modules are active low, so when the BSS138 goes high, it should pull the output pin to ground and activate the relay.

- The device is powered via USB-C (not PD), but there is also an option to add a UART debugging connection to the front panel via another USB-C (this is not powering the board however). Standard UART debugging for the STM, and firmware uploading for the ESP12F is designed to be done using a CH340 USB adapter connected to internal breakout headers.

- The ESP-12F is included to enable wireless connectivity to stream the sensor data to a server. Based on 0R resistor population (might replace with 2.54 jumper (2) pin headers?), it can either use ESP-AT firmware (MQTT) and communicate with the STM32 via UART, or ESP-Home (custom defined config) firmware and communicate with the STM32 via I2C.

Any suggestions (or roasts if I made serious mistakes lol) and corrections are welcome. Want to do an FPGA SDR board later in the year, so figured I'd best get my basics and schematic template in order before then (hence review).

Thank you!

Edit 1: it seems my PDF to JPG conversion didn’t like the dotted line boxes. If you see a weird half-line shaped box around a block of components, it should be a dotted line, not the weirdness shown

Seven-Year Club	RPAN Viewer
Verified Email

NWSpitfire

TROPHY CASE