function wp_mail() {} {"id":299,"date":"2010-04-28T18:11:32","date_gmt":"2010-04-29T01:11:32","guid":{"rendered":"http:\/\/www.serialporttool.com\/sptblog\/?p=299"},"modified":"2010-07-29T02:15:59","modified_gmt":"2010-07-29T09:15:59","slug":"advanced-options-in-configuration","status":"publish","type":"post","link":"https:\/\/www.serialporttool.com\/sptblog\/?p=299","title":{"rendered":"Advanced options in Configuration for Relay Timer Series"},"content":{"rendered":"

We added \u201cAdvanced\u201d options in Configuration dialog for Relay Timer series products.<\/p>\n

There are three advanced items, \u201cOne-way Communication\u201d, \u201cRead Timeout\u201d and \u201cCommand Interval\u201d.<\/p>\n

\"image\"<\/a> <\/p>\n

 <\/p>\n

One-way Communication<\/strong><\/p>\n

In One-way communication mode, the program will send the command only one time and won\u2019t wait for return value. The advantage of this mode is that only Rx and ground line need to be connected with computer. Another advantage is that the program will have better respond to user\u2019s operation. The disadvantage is that there is no way to know if the board is still working.<\/p>\n

The default value of one-way communication is unchecked. That means the default communication is two-way. In two-way communication, there always is a return value from relay board for all commands. If the program fails to get the return value, it will send the command again. The same command will be sent 5 times if it can\u2019t get return value before it stops. The \u201cCommunication Error\u201d will be shown on status bar. Both Rx and Tx line has to be connected with computer in two-way communication mode. The advantage is that the connection problem will be know immediately. The disadvantage is that both Rx and Tx lines are needed, and if there is a connection problem, the respond of the program will be a little slow.<\/p>\n

Read Timeout<\/strong><\/p>\n

Timeout value for read data from controller. This option is valid in two-way communication. Default value is 100ms. For device that has slow processor, like R1X and R2X, it needs longer time, for fast connection device, like ProXR with RS232 or USB interface, the timeout value could be 10 \u201330 ms. The shorter, the faster the program response. In some circumstance, the program need have a longer read timeout value, like zigbee device, or ethernet\/wifi device on a slow connection. 100 ms should work for most of the device.<\/p>\n

Command Interval<\/strong><\/p>\n

Command interval is the time between sending two commands. If the interval is too short, none of the commands will be execute on relay board correctly. For boards that have slow processor, the command interval could be 50ms. For boards that have fast processor, 10 \u2013 30 ms works. Another factor is the interface of the device, for zigbee or network interface, a value between 30 \u2013 100 will make the board works more reliable.<\/p>\n

Conclusion<\/strong><\/p>\n

The default value should work for most of the device and you can just ignore those options. However, those options will solve most of the problem for zigbee mesh or 802.15.4 interface module.<\/p>\n","protected":false},"excerpt":{"rendered":"

We added \u201cAdvanced\u201d options in Configuration dialog for Relay Timer series products. There are three advanced items, \u201cOne-way Communication\u201d, \u201cRead Timeout\u201d and \u201cCommand Interval\u201d.   One-way Communication In One-way communication mode, the program will send the command only one time […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-299","post","type-post","status-publish","format-standard","hentry","category-relaytimer"],"_links":{"self":[{"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=\/wp\/v2\/posts\/299","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=299"}],"version-history":[{"count":4,"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=\/wp\/v2\/posts\/299\/revisions"}],"predecessor-version":[{"id":434,"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=\/wp\/v2\/posts\/299\/revisions\/434"}],"wp:attachment":[{"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=299"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=299"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serialporttool.com\/sptblog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}