Writing DM-32UV with a lot of zones and channels crashes upload.

[firebelcher]

I ran into this issue when I had a bunch of zones and channels. The DM-32UV has enough space for both, but it seems to crash on upload.

NeonPlug Connection Debug
Timestamp: 2026-07-27T22:49:33.198Z
Error: Zone 29 would exceed block size

--- Recent logs ---
[2026-07-27T22:42:12.743Z][INFO][Connection] PSEARCH: 06 44 50 35 37 30 55 56
[2026-07-27T22:42:14.548Z][INFO][Memory] Reading metadata from 200 blocks from 0x1000 to 0xc8000 (endAddr was 0xc8fff)
[2026-07-27T22:42:26.869Z][INFO][Memory] Discovered 200 blocks: Channels=48, Zones=1, Scan Lists=1, Unknown=49, Empty=93
[2026-07-27T22:42:26.928Z][INFO][Protocol] Channel count: 331
[2026-07-27T22:42:26.929Z][INFO][Protocol] Found required metadata block 0xb at 0x08D000 (marked as unknown type, but will read)
[2026-07-27T22:42:26.932Z][INFO][Protocol] Found required metadata block 0x44 at 0x00B000 (marked as unknown type, but will read)
[2026-07-27T22:42:26.933Z][INFO][Protocol] Found required metadata block 0x42 at 0x008000 (marked as unknown type, but will read)
[2026-07-27T22:42:26.933Z][INFO][Protocol] Found required metadata block 0x43 at 0x00A000 (marked as unknown type, but will read)
[2026-07-27T22:42:26.933Z][INFO][Protocol] Bulk reading 19 blocks (channels, zones, scan lists, and fixed metadata blocks)
[2026-07-27T22:42:37.377Z][INFO][Protocol] Bulk read complete: 19 blocks cached
[2026-07-27T22:42:37.378Z][INFO][Protocol] All blocks read: 19 blocks, 200 metadata entries
[2026-07-27T22:42:37.493Z][INFO][Protocol] Channel count: 331
[2026-07-27T22:42:37.493Z][INFO][Protocol] Parsing 5 cached channel blocks for 331 channels
[2026-07-27T22:42:37.500Z][INFO][Protocol] Successfully parsed 331 channels (expected 331)
[2026-07-27T22:42:37.503Z][INFO][Protocol] Found 1 zone blocks (metadata 0x5c)
[2026-07-27T22:42:37.504Z][INFO][Protocol] Successfully parsed 20 zones
[2026-07-27T22:42:38.350Z][INFO][Protocol] Found 1 scan list blocks (metadata 0x11)
[2026-07-27T22:42:38.350Z][INFO][Protocol] Successfully parsed 1 scan lists: List 1
[2026-07-27T22:45:22.732Z][INFO][Protocol] Restoring cache from store: 19 block data entries, 200 metadata entries
[2026-07-27T22:45:22.732Z][INFO][Protocol] Restored 19 blocks from store cache
[2026-07-27T22:45:24.111Z][INFO][Connection] PSEARCH: 06 44 50 35 37 30 55 56
[2026-07-27T22:45:25.915Z][INFO][Memory] Reading metadata from 200 blocks from 0x1000 to 0xc8000 (endAddr was 0xc8fff)
[2026-07-27T22:45:38.285Z][INFO][Memory] Discovered 200 blocks: Channels=48, Zones=1, Scan Lists=1, Unknown=49, Empty=93
[2026-07-27T22:45:38.293Z][INFO][Protocol] Writing 45 zones to 1 block(s)
[2026-07-27T22:45:38.293Z][ERROR][Protocol] Zone 29 would exceed block size: offset 4076, data length 4096
[2026-07-27T22:46:56.695Z][INFO][Protocol] Restoring cache from store: 19 block data entries, 200 metadata entries
[2026-07-27T22:46:56.695Z][INFO][Protocol] Restored 19 blocks from store cache
[2026-07-27T22:46:58.156Z][INFO][Connection] PSEARCH: 06 44 50 35 37 30 55 56
[2026-07-27T22:47:00.004Z][INFO][Memory] Reading metadata from 200 blocks from 0x1000 to 0xc8000 (endAddr was 0xc8fff)
[2026-07-27T22:47:13.179Z][INFO][Memory] Discovered 200 blocks: Channels=48, Zones=1, Scan Lists=1, Unknown=49, Empty=93
[2026-07-27T22:47:13.252Z][INFO][Protocol] Writing 41 zones to 1 block(s)
[2026-07-27T22:47:13.253Z][ERROR][Protocol] Zone 29 would exceed block size: offset 4076, data length 4096
[2026-07-27T22:49:17.419Z][INFO][Protocol] Restoring cache from store: 19 block data entries, 200 metadata entries
[2026-07-27T22:49:17.419Z][INFO][Protocol] Restored 19 blocks from store cache
[2026-07-27T22:49:18.804Z][INFO][Connection] PSEARCH: 06 44 50 35 37 30 55 56
[2026-07-27T22:49:20.733Z][INFO][Memory] Reading metadata from 200 blocks from 0x1000 to 0xc8000 (endAddr was 0xc8fff)
[2026-07-27T22:49:33.072Z][INFO][Memory] Discovered 200 blocks: Channels=48, Zones=1, Scan Lists=1, Unknown=49, Empty=93
[2026-07-27T22:49:33.076Z][INFO][Protocol] Writing 37 zones to 1 block(s)
[2026-07-27T22:49:33.077Z][ERROR][Protocol] Zone 29 would exceed block size: offset 4076, data length 4096

[infamy]

are you sure it would support that many zones? does that work in the stock CPS? if so let me know.. it would be a boundary write/read issue. This radio does everything in 4k blocks it shuffles around out of order.. making this stuff tricky.

[firebelcher]

Yeah, I'm 100% positive. The specs are 4,000 programmable channels, 250 zones, 50,000 DMR digital contacts, and 800 quick-access favorites. Even the manual says 250 zones. Each zone can have 64 analog and/or digital channels.

[infamy]

Let me dig.. its a boundary issue... Zones and Scanlist both have bugs in the stock CPS. so "fixing" how write it to the radio is tricky!

[firebelcher]

Sounds good, and completely understandable! Very impressed by the work that you've done so far! The work hasn't gone unnoticed!

[infamy]

Figured it out.. give me 2-3 days to fully test it before I let others try it...

[infamy]

There will be a build in that PR shortly.. it needs more testing... but if you are brave... May turn the radio into a paper weight... Mine was fine :D

[infamy]

https://neonplug.app/test/bug-zonemax/ <- test branch. Give it a shot, if no issues will merge in 2 days or so. More testing all shows it working well.

[firebelcher]

WOW @infamy that was fast! Awesome! Yes, I'll be a test dummy!

[firebelcher]

Tested and it's working now on my DM-32UV. I'll play around with it a bit now to add more zones and clean up my existing ones, and I'll let you know if I find anything.

[firebelcher]

@infamy - I Found a glitch with the zone display.

The zone / channel mapping when read from the device looks weird in the Zones page.

It's like it's off by one or two channels. One or two channels belong to the next zone.

The channels aren't matching the channels you added to the zone. BUT, when you write to the device it does match.

So this looks to be a display issue only.

[infamy]

That is a good catch.. I tested it with just two channels over and over again.. so that may not have exposed that bug... let me reproduce.

[infamy]

So I can't reproduce and I did a few cycles with a few 200+ zones.. and one with 64 channels per zone.. can you get me some debug of the bad data and good data? enable debug in the about tab... and then metadata download. Discord DM is the best way to send that to me if you don't want to post it here.

[firebelcher]

Ok this is weird... I can't replicate it now either.

I pulled the data back from the radio, adjusted a zone, uploaded it, and read it back and it's fine now.

Sorry to throw this at you, if I run into it again I'll let you know and send you the debug info.

[infamy]

no worries... I check all the code and added a very aggressive read write test loop (my poor radio just did 100 read writes of zones) and no issues.. with all different combination and edge cases.

So I think this is fairly solid fix.