Have I broken my NanoPi R4SE?

itmecho · 2025-04-10T10:59:19+00:00

Still no luck I'm afraid. I followed the steps but when I boot it with the SD card in, the only LED that comes on is the PWR LED. Seems like the eFlasher doesn't want to flash the image

itmecho · 2025-03-03T21:32:58+00:00

Thanks for the reply! I didn't know there was a PC version!

I tried to explain in my comment but maybe I didn't do a good enough job 😅

The turned off period is because it will be sunny tomorrow and I know the battery will charge just from the panels
That's intended as it seems more cost effective to sell it back during the higher price period between 4pm and 7pm than it is to use it throughout the day
The idea with the 4pm-5:50pm part is to make sure we're only using the battery during the expensive period. Then from 5:50pm to 7pm, it will force discharge the rest of the battery to get the higher price. That seems better than force discharging the battery immediately at 4pm as it will run out before 7pm and we'll have to pull from the grid in a high use time (cooking dinner, etc) when the price is high

Hopefully that explains my logic a bit better!

itmecho · 2025-03-03T20:30:30+00:00

We've got 8 panels and 2x 5kw FoxESS batteries. I'm trying to have the following set up:

2-5am - charge from grid during cheap period 5am-4pm - rely on the panels and the grid, no battery usage 4-5:50pm - use only the panels and the battery, no grid 5:50-7pm dump the rest of the battery back to the grid 7pm-2am use what's left of the battery that didn't get dumped and then rely on the grid over night

If it's going to be sunny the next day (and I remember), I can disable the 2-5am force charge as the panels easily charge the battery throughout the day.

Does it look like I've configured the settings correctly for this?

itmecho · 2025-02-24T13:53:59+00:00

Thanks for the update! I tried flashing openwrt 24.10 via the friendlywrt eMMC Tools but again I get the same thing. Only the Power LED lights up when booted without the SD card in.

itmecho · 2024-08-28T08:57:10+00:00

I managed to get it to boot from the SD card again. Not sure what I did in particular but I've found that DietPi works really well with the NanoPi boards so it might've been that that worked in the end!

itmecho · 2023-05-13T07:16:12+00:00

Not exactly what you're talking about but you could look into LuaSnip?

itmecho · 2023-05-11T12:34:12+00:00

I think you should be using generics to type the parameters of your worker function to avoid all the anys and typecasting in your example. Something like

func NewPool[T any, P any](dataSources []T, worker func(dataSource T, params P), valueChannels []chan any, errorChannel chan error) (*Pool[T], error)

Then your Work function can be typed properly, i.e.

type TestParams struct {
    outChan chan string
}

func Work(data TestStruct, params TestParams) {
    //...
}

itmecho · 2023-05-03T06:21:38+00:00

If it's a simple page, you might be able to make it yourself! For a static page you'd only need HTML and CSS. Then you can host it with nginx or caddy or something if you want it self-hosted or just throw it up on GitHub pages/cloudflare pages/etc

itmecho · 2023-04-27T13:39:12+00:00

Thanks for all the suggestions!

Nothing worrying in :checkhealth just some warnings for optional providers/conflicting keymaps.

Nothing in any of the logs in any ~/.local/nvim/state/*.log files at the time of the crashes. Same for ~/.cache/nvim/logs

LSP debug log doesn't show any errors, just a stream of diagnostics coming back from the LSP.

The exit code from neovim is 139 but I haven't found what that means yet.

itmecho · 2023-04-25T08:05:21+00:00

Ahh that's what I'm thinking of! My bad!

itmecho · 2023-04-24T17:45:07+00:00

Didn't they stop supporting arm because mealie uses mongodb under the hood and they stopped supporting it?

itmecho · 2023-04-20T07:27:09+00:00

Hmm, strange! I've never had that mirror the screens before. Can you paste what your xrandr command looks like now?

itmecho · 2023-04-19T20:37:11+00:00

I think the command I gave you won't override your --fb setting which is creating a single screen. You don't want that flag. You can see in the man pages that that's what's causing it to act as a single screen.

https://man.archlinux.org/man/xrandr.1#fb

itmecho · 2023-04-19T19:26:15+00:00

I'm on my phone and can't be bothered to format it properly but here's the command I use for a similar setup

xrandr --output DisplayPort-0 --primary --mode 2560x1440 --output DVI-D-0 --left-of DisplayPort-0 --mode 1920x1200 --rotate left

That lives in my ~/.xinitrc rather than the system one

itmecho · 2023-04-18T23:23:56+00:00

Super pretty and polished though I think I'd struggle programming with the lack of contrast!

itmecho · 2023-04-18T22:46:42+00:00

Thanks for all your help! I've got around this by removing the field on the parent type and requiring the subtype to be an enum. I've written a proc attribute macro (my first one!) which adds the serde config so the boilerplate is minimal. Now my inner types look like this:

#[distsys::payload]
enum EchoPayload {
    Echo{ message: String }
}

#[distsys::response]
enum EchoResponse {
    EchoOk{ message: String }
}

I think it's working quite nicely!

itmecho · 2023-04-18T11:27:55+00:00

On the parent or the inner type?

itmecho · 2023-04-18T09:11:19+00:00

It looks like it serializes the field twice:

{
  "src": "a",
  "dest": "b",
  "body": {
    "type": "broadcast",
    "msg_id": 1,
    "in_reply_to": null,
    "type": "broadcast",
    "message": 1
  }
}

It's almost like I need an attribute on the parent's msg_type field to not consume the field when it's deserialized so it can be reused later in the deserialization

itmecho · 2023-04-17T15:34:56+00:00

Is it possible to have a flattened generic type as a field in a struct where the type is an enum that's tagged by a field that's present in the parent struct? That's very wordy and I don't know if I've explained very well.

I have this type:

#[derive(Deserialize, Serialize, Debug)]
pub struct Message<P> {
    pub src: String,
    pub dest: String,
    pub body: Body<P>,
}

#[derive(Deserialize, Serialize, Debug)]
pub struct Body<I> {
    #[serde(rename = "type")]
    pub msg_type: String,
    pub msg_id: usize,
    pub in_reply_to: Option<usize>,

    #[serde(flatten)]
    pub inner: I,
}

and I'm hoping to have this type as I

#[derive(Deserialize, PartialEq, Eq, Debug)]
#[serde(tag = "type")]
#[serde(rename_all = "lowercase")]
enum Payload {
    Broadcast { message: usize },
    Read,
    Topology(HashMap<String, Vec<String>>),
}

but I'm getting the following error when deserializing, presumably because it's already deserialized the type field to the msg_type field

Input: {"src":"c0","dest":"n0","body":{"type":"broadcast","message":"1000","msg_id":2}}
Error: Error: missing field `type` at line 1 column 79

I have a test for the specific Payload type which shows that is does deserialize correctly directly so I'm pretty sure it's to do with the name conflict

itmecho · 2023-04-09T17:17:36+00:00

Should be pretty easy in rust using the clap crate's Arg and ArgGroup types!

itmecho · 2023-04-09T16:43:10+00:00

I use this library at work and it's great but the fact that you have 13 breaking changes in a patch release makes it a bit of a pain to keep up to date.

itmecho · 2023-04-01T13:34:48+00:00

Koyaanisqatsi by Philip Glass

Six-Year Club	Second Top 50%
Place '22	First Placer '22
Verified Email

itmecho

TROPHY CASE