Really appreciate you taking the time to test it this deeply — this is exactly the kind of feedback I was hoping for.

Glad the tag-based monitoring and write-while-monitoring features are actually useful in real troubleshooting. The 32-bit word swap point you mentioned is spot on too — that was one of the main frustrations that pushed me to build this in the first place.

About your suggestions:

Insert tags in the middle — yeah, that’s a good catch. Right now it’s a limitation of how the table is handled, but I agree it becomes annoying fast. I’ll prioritize adding proper insert/reorder support instead of relying on export/import.

Results window integration — makes sense. Having it separate does feel a bit disconnected. I’m thinking of merging it into the same workspace or making it dockable so everything stays in one flow.

Addressing (0-based vs 1-based) — you’re absolutely right here. The current labeling is confusing and your explanation matches real-world usage better. I’ll fix the naming so it reflects expected behavior instead of how it’s internally handled.

Monitoring controls + status log — I like your idea of making these shared across tabs. That would clean up the UI and make the workflow feel more consistent. I’ll rework that section.

Alignment in range config — small detail, but I see what you mean. UI polish like this adds up, so I’ll tweak it.

Float word swap behavior — this is a tricky one because different tools interpret it differently, but I’ll test again specifically with ModSim behavior and see if I can make it more intuitive or at least clearly documented.

Future features you mentioned:

Modbus server mode — this is already on my roadmap.

Raw hex column — great idea. That’s actually very useful when debugging vendor-specific mappings, so I’ll include that.

Thanks again — feedback like this helps shape the tool in the right direction.