node-red / node-red/node-red-nodes
Add field to set different trigger pulse time
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
The JSN-SR04T uses a different trigger pulse time (20uS) than the als HC-SR04 (I guess 10uS ?!).
Could you please let the user adjust the trigger pulse time in the node-red PI-SRF node?
Which node are you reporting an issue on?
node-red-node-pisrf
What are the steps to reproduce?
What happens?
Measurement seems to be unstable.
The documentation of the JSN-SR04T says that the trigger time set to 20uS could stabilize that:
https://protosupplies.com/product/jsn-sr04t-v3-0-waterproof-ultrasonic-range-finder/
What do you expect to happen?
Better, stable measures
Please tell us about your environment:
- Node-RED version: 3.0.1
- node.js version: 14.17.3
- npm version: 6.14.13
- Platform/OS: Rpi
- Browser: Firefox/Chrome
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies the node-red-node-pisrf node but no source file or test path. Start by locating its trigger-pulse handling and review how the current pulse time is set. Done means users can configure a different trigger pulse time, including the 20uS value needed by the JSN-SR04T, without breaking existing sensor use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100