From 59d7c15686757e1184553ac3892e792ab4303a64 Mon Sep 17 00:00:00 2001 From: Yoonseok Hur Date: Tue, 21 Nov 2023 13:16:04 +0900 Subject: [PATCH] Update README.md --- io/serialport/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/io/serialport/README.md b/io/serialport/README.md index dbadfd3f..c3c4a750 100644 --- a/io/serialport/README.md +++ b/io/serialport/README.md @@ -66,7 +66,7 @@ This `Serial Control` node provides the serial port control capability to 3. start the communication after stopped with this `Serial Control` node for above reason or the like.

In order to control the communication, just send these JSON messages to the control node.

-```json +
     {
         "serialport": "/dev/tty.usbmodem1234561",
         "serialbaud": 115200,
@@ -74,8 +74,8 @@ This `Serial Control` node provides the serial port control capability to
         "parity": "none",
         "stopbits": 1
         "enable": true
-    } 
-```
+    }   
+
changes the serial port and the configuration on the fly.

The following optional parameters will change the configuration only if they are present.

Any combination of them can be passed to change/control the serial communication

@@ -95,7 +95,7 @@ changes the serial port and the configuration on the fly.

When the `enable` property is not present, it will default to `true`

-`{"enable":true}` or `{"enable":false}` will start or stop the communication.

+{"enable":true} or {"enable":false} will start or stop the communication.

If `enable` is passed along wiht other parameters, the configuration will be changed and either be started or just be ready to be started(ie. stopped ) depending on its value.

**Here is the serial control node usage example flow**