Skip to content

Modernise language and techical clarifications for modbus article - #5458

Merged
ZJvandeWeg merged 5 commits into
mainfrom
5447-clarifications-to-modbus-docs
Aug 4, 2026
Merged

Modernise language and techical clarifications for modbus article#5458
ZJvandeWeg merged 5 commits into
mainfrom
5447-clarifications-to-modbus-docs

Conversation

@Steve-Mcl

Copy link
Copy Markdown
Contributor

Description

Modernise language and techical clarifications

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

@Steve-Mcl Steve-Mcl linked an issue Jul 31, 2026 that may be closed by this pull request
@Steve-Mcl Steve-Mcl changed the title Modernise language and techical clarifications Modernise language and techical clarifications for modbus article Jul 31, 2026
@Steve-Mcl
Steve-Mcl requested a review from sumitshinde-84 July 31, 2026 15:05
@netlify

netlify Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit f5b8cbb
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a71c022a9edbb0008013a43
😎 Deploy Preview https://deploy-preview-5458--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 52 (🟢 up 27 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@sumitshinde-84 sumitshinde-84 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Steve 🙌


On a serial bus, valid device addresses are **1–247**. Address **0 is the broadcast address** — a write sent to unit 0 goes to every device on the bus and none of them reply, so a read addressed to unit 0 will always time out. Addresses 248–255 are reserved. Native Modbus TCP devices often ignore the unit ID altogether (`0`, `1`, and `255` are all common), but it matters as soon as a gateway sits in front of serial devices.

{% note %}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Yndira-E When we migrate the docs, we need to check for {% note %} support too

@ZJvandeWeg

Copy link
Copy Markdown
Member

I suspect this should've been merged @sumitshinde-84 ?
I'll do so in your stead.

@ZJvandeWeg
ZJvandeWeg enabled auto-merge (squash) August 4, 2026 00:15
@ZJvandeWeg

Copy link
Copy Markdown
Member

@sumitshinde-84 @Steve-Mcl The test failures seem related?

@sumitshinde-84

sumitshinde-84 commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

@sumitshinde-84 @Steve-Mcl The test failures seem related?

test were failing because of broken image fixed it here FlowFuse/flowfuse#8023 (review)

@ZJvandeWeg
ZJvandeWeg merged commit d1b5be5 into main Aug 4, 2026
7 of 8 checks passed
@ZJvandeWeg
ZJvandeWeg deleted the 5447-clarifications-to-modbus-docs branch August 4, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarifications to Modbus docs

3 participants