DmitrySidorow

DmitrySidorow

python developer.

Member Since 3 years ago

R-Solutions, Saint-Petersburg

Experience Points
10
follower
Lessons Completed
6
follow
Lessons Completed
172
stars
Best Reply Awards
6
repos

678 contributions in the last year

Pinned
⚡ Simple translator | translation for Grafana, developed for Unix-like systems
⚡ Create Modbus app easily with Python
⚡ Grafana map plugin to visualise coordinates as markers, hexbin, ant path, or heatmap.
⚡ Custom Selenium Chromedriver | Zero-Config | Passes ALL bot mitigation systems (like Distil / Imperva/ Datadadome / CloudFlare IUAM)
⚡ Python logging handler for Loki
⚡ The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
Activity
May
20
3 days ago
May
19
4 days ago
started
started time in 4 days ago
May
14
1 week ago
May
4
2 weeks ago
started
started time in 2 weeks ago
Apr
25
4 weeks ago
Apr
24
4 weeks ago
started
started time in 4 weeks ago
Apr
19
1 month ago
Activity icon
issue

DmitrySidorow issue comment BiancoRoyal/node-red-contrib-modbus

DmitrySidorow
DmitrySidorow

"Modbus Failure On State sending" warn due to timeouts

I'm submitting a ... (check one with "x")

Problem

  • (x) bug report => please search github for a similar issue or PR and test Modbus problems with the modbus-serial package before submitting
  • ( ) unexpected behavior => please visit the Wiki before

Current behavior When ANY read/write Modbus node timeouts on a request (es. unit-id nonexistent/disconnected/broken) a warn message is written in Node-Red debug log: "Modbus Failure On State sending Get More About It By Logging"

Expected behavior Not getting such a warning that clogs the log and may make the journal of the device grow exponentially.

Minimal reproduction of the problem with instructions

  1. Create a Modbus Read (or Flex) node over any serial you have and configure it to query a non-existent device
  2. Enable both "Show Activities" and "Show Errors"

Your Environment

Please tell us about your environment:

  • (x ) I am using just the Node-RED package and got modbus-serial package installed with it
  • ( ) I have installed modbus-serial package global from source (using git clone)
  • ( ) I have installed modbus-serial as a global package (using npm i -g)

Yes, modbus-serial is the name but it does all, TCP and Serial. The node-modbus package is just for the Modbus Server node.

  • Device :

    • ( ) macOS: v
    • ( ) Linux: v
    • ( ) Windows: v
    • (x ) Raspbian: v
    • ( ) Other:
      • Name:
      • Version:
  • Description of the connecting Modbus system:

    • Name :
    • Version:
    • Vendor :
    • Link : https://
  • node-red-contrib-modbus version: v5.21.2

  • Node: (v14.19.0)

DmitrySidorow
DmitrySidorow

I also don't like constant warnings after each restart of flows. I would like a separate checkbox to disable their output to the console.

Apr
16
1 month ago
Apr
9
1 month ago
started
started time in 1 month ago
started
started time in 1 month ago
Apr
7
1 month ago
Activity icon
issue

DmitrySidorow issue comment BiancoRoyal/node-red-contrib-modbus

DmitrySidorow
DmitrySidorow

"Modbus Failure On State sending" warn due to timeouts

I'm submitting a ... (check one with "x")

Problem

  • (x) bug report => please search github for a similar issue or PR and test Modbus problems with the modbus-serial package before submitting
  • ( ) unexpected behavior => please visit the Wiki before

Current behavior When ANY read/write Modbus node timeouts on a request (es. unit-id nonexistent/disconnected/broken) a warn message is written in Node-Red debug log: "Modbus Failure On State sending Get More About It By Logging"

Expected behavior Not getting such a warning that clogs the log and may make the journal of the device grow exponentially.

Minimal reproduction of the problem with instructions

  1. Create a Modbus Read (or Flex) node over any serial you have and configure it to query a non-existent device
  2. Enable both "Show Activities" and "Show Errors"

Your Environment

Please tell us about your environment:

  • (x ) I am using just the Node-RED package and got modbus-serial package installed with it
  • ( ) I have installed modbus-serial package global from source (using git clone)
  • ( ) I have installed modbus-serial as a global package (using npm i -g)

Yes, modbus-serial is the name but it does all, TCP and Serial. The node-modbus package is just for the Modbus Server node.

  • Device :

    • ( ) macOS: v
    • ( ) Linux: v
    • ( ) Windows: v
    • (x ) Raspbian: v
    • ( ) Other:
      • Name:
      • Version:
  • Description of the connecting Modbus system:

    • Name :
    • Version:
    • Vendor :
    • Link : https://
  • node-red-contrib-modbus version: v5.21.2

  • Node: (v14.19.0)

DmitrySidorow
DmitrySidorow

I also don't like these messages in logs that can't be disabled.

Apr
3
1 month ago
Mar
25
1 month ago
Mar
21
2 months ago
Mar
18
2 months ago
started
started time in 2 months ago
Mar
13
2 months ago
started
started time in 2 months ago
Mar
11
2 months ago
Feb
26
2 months ago
started
started time in 2 months ago
Feb
25
2 months ago
Previous