Need Help on Weeder WTDIN

George Handley 12508HandWork at gmail.com
Mon Oct 10 17:25:51 EDT 2022 

James,

I just got finished sending you the email below, and upon sending it to you I looked at my copy, and it appeared to be in all Chinese characters, so I’m sending it again under a different email address.

James,

I thought for  sure I’d hear fro you over the weekend or at least today, but theres been no response to my emails requesting help.

I have tried each of your suggestions after first hooking your a WTDIN card directly to my main XTension machine and can make a WTDIN crudely communicate by tricking tt using the 1 off theory. From that I’ve already told you the WTDIN card communicates just fine with XTension, but what it does is not. I’ve told you about how it appears to be a “1 off” problem inside your supporting Weeder software, and when queried, Terry says it has to be something inside your weeder.isf plugin software. I even poked around inside your Plugins/weeder.isf folder and looked around, but without any guidance from you, it is totally greek to me. I need your help

I’ve waited all last week, last weekend and today and I don’t know why you’re ignoring me. Is there something from this end I can send you to allow you to help?

Terry says my problem all along is that his DIO cards have no protection from lightning, and that lightning even a mile away could burn up of his DIO cards, even ones that are behind a regulating UPS which I thought was impossible. 

Could you please step in a straighten this out!

Thanks,

George



> On Sep 27, 2022, at 8:03 AM, james at sentman.com wrote:
> 
> 
> Good morning George,
> 
> You’ve got some physical connection issues between XTension and the wiznet cards that I believe you’re using for the connection. For example this:  
> 
>> GarageWeederBank2: Digital Input received weeder packet: (?)A 
> 
> Is the return from the weeder when it doesn’t recognize a command. It received either only a partial packet from XTension or some other garbage that was not a valid command. This message:
> 
>> GarageWeederBank2: port error received 102
> 
> Is a networking error, this just means that the connection was dropped by the remote side for some reason or other. It might have lost power, thrown so many TCP errors that it was unrecoverable or something similar. This does not appear to be a configuration issue as the startup command is properly referencing a remote connection and a WTDIN board. It looks like a problem with the network layer to the wiznet card or possibly power to the wiznet cards or something similar.
> 
> Then you start receiving extra characters in the data as in the failed receptions logged like this:
> 
>> weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
> 
> That second part under “message” is actually the correct polling response. But it is inserting that accented A character at the beginning of each one. The only way I can think of that being inserted is between the weeder and the wiznet since it is not generating a TCP error. I would again suggest interfierence at the remote location. Bad power, bad cabling, something has gone bad physically. It may be the power supply filters or possibly induced noise on the serial line connecting the two, or a broken data ground on the serial connections or something. But you’re getting garbage data sent from the weeder to the wiznet, and possibly garbage data being sent from the wiznet to the weeder. 
> 
> It is also possible that the lightning hits in the past have damaged the UART on the wiznet card. I’ve got 2 outputs on a multi-port USB/Serial adaptor here that took an inductive hit from a nearby lightning strike and while they still appear to work the output and input are damaged and are very weak and receive garbage sometimes too, if I try to use them.
> 
> There is more of the same in the log:
> 
>> weeder message recieved for unknown weeder ID "ÿ" message: "A11110111" (GarageWeederBank2) 
> 
> This is a reasonable packet in the message section, but is preceded by that accented y which is just noise on the serial line. Again here:
> 
>> weeder message recieved for unknown weeder ID "Â" message: "B30AE" (BasementEastBank1) 
> 
> An A again, but with a different accent. More noise from somewhere. 
> 
> You’ve got a problem at the remote end. The most likely reasons for this I have mentioned inline above but will sum up:
> 
> Possibly damaged Wiznet UARTS. try a spare?
> 
> Possibly bad power supply running the remote boards, try a spare?
> 
> Possibly bad or failing wiring on the serial connection between the wiznet and the weeders. Failed data ground connection or failed power ground and trying to use the data ground for power or something similar.
> 
> Some induced noise from something nearby, the power supply maybe? Or something else. 
> 
> When dealing with noise or random errors like that it is difficult to debug. I might bring the wiznet and weeder up to the main machine and plug them directly into the switch next to XTension and see if they function there. You can power them with something else temporarily for testing. You can temporarily use a USB/Serial adaptor to connect the wiznet to XTension and test it that way to verify it is working properly, though I suspect the weeder is fine in this case I cannot be sure. 
> 
> 
> 
>> On Sep 26, 2022, at 6:43 AM, George Handley <ghandley at kc.rr.com> wrote:
>> 
>> Dear James and others who use a Weeder WTDIN (Digital Input) board,
>> 
>> I’m just beginning to convert my whole system from using WTDIO boards to using WTDIN digital input cards because they are supposed to be more substantial and have extra protection built in against lightning strikes from even a mile away even if your system is protected by a UPS and other power protection systems to my surprise. The board has 8 digital inputs meant for dry contact use.
>> 
>> My problem is I can’t get them to work. I get all sorts of crazy information in the log displayed below, but can’t find any error in my code that explains the invisible characters that sometimes appears shown separately.
>> 
>> The log snippets below are from just the  the launch of the app unit the app is stable, and just those lines pertaining to GarageWeederBank1 and GarageWeederBank2:
>> 
>> 
>> Sep 26, 2022 3:32:53 AM.6016 weeder config string(A1 B1) (GarageWeederBank1) 
>> Sep 26, 2022 3:32:53 AM.6019 Starting Interface "GarageWeederBank1" command: "/Applications/XTension.app/Contents/Resources/Plugins/weeder.isf/weeder.isf IP 127.0.0.1 52301 10 150 A1 B1 10.0.0.38 5000" (GarageWeederBank1) 
>> Sep 26, 2022 3:32:53 AM.6163 weeder config string(A3) (GarageWeederBank2) 
>> Sep 26, 2022 3:32:53 AM.6165 Starting Interface "GarageWeederBank2" command: "/Applications/XTension.app/Contents/Resources/Plugins/weeder.isf/weeder.isf IP 127.0.0.1 52301 11 150 A3 10.0.0.71 5000" (GarageWeederBank2)
>> 
>> Sep 26, 2022 3:32:53 AM.9240 GarageWeederBank1: Weeder ISF connecting... (GarageWeederBank1) 
>> Sep 26, 2022 3:32:53 AM.9801 GarageWeederBank2: Weeder ISF connecting... (GarageWeederBank2)
>> 
>> 
>> Sep 26, 2022 3:32:54 AM.2464 GarageWeederBank1: Weeder Chain v2.1 Ready. (GarageWeederBank1) 
>> Sep 26, 2022 3:32:54 AM.2468 GarageWeederBank2: Weeder Chain v2.1 Ready. (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:32:54 AM.5094 GarageWeederBank2: Digital Input received weeder packet: (?)A (GarageWeederBank2) 
>> 
>> 
>> Sep 26, 2022 3:32:54 AM.7038 GarageWeederBank2: received ON for address: A1 (GarageWeederBank2) 
>> Sep 26, 2022 3:32:54 AM.7089 GarageWeederBank2: received ON for address: A3 (GarageWeederBank2) 
>> Sep 26, 2022 3:32:54 AM.7097 GarageWeederBank2: received ON for address: A5 (GarageWeederBank2) 
>> Sep 26, 2022 3:32:54 AM.7104 GarageWeederBank2: received ON for address: A6 (GarageWeederBank2) 
>> Sep 26, 2022 3:32:54 AM.7110 GarageWeederBank2: received ON for address: A7 (GarageWeederBank2) 
>> Sep 26, 2022 3:32:54 AM.7117 GarageWeederBank2: received ON for address: A8 (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:33:19 AM.3135 GarageWeederBank2: port error received 102) (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:33:22 AM.1907  Interface "GarageWeederBank2" has quit with code: 0 () 
>> 
>> Sep 26, 2022 3:33:27 AM.4550 Retry connection to interface "GarageWeederBank2". Tries left: 9 (GarageWeederBank2) 
>> Sep 26, 2022 3:33:27 AM.4574 weeder config string(A3) (GarageWeederBank2) 
>> Sep 26, 2022 3:33:27 AM.4577 Starting Interface "GarageWeederBank2" command: "/Applications/XTension.app/Contents/Resources/Plugins/weeder.isf/weeder.isf IP 127.0.0.1 52301 17 150 A3 10.0.0.71 5000" (GarageWeederBank2) 
>> Sep 26, 2022 3:33:27 AM.5657 GarageWeederBank2: Weeder ISF connecting... (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.1245 GarageWeederBank2: Weeder Chain v2.1 Ready. (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.1610 GarageWeederBank2: Digital Input received weeder packet: (?)A (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.3469 GarageWeederBank2: received ON for address: A1 (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.3506 GarageWeederBank2: received ON for address: A3 (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.3512 GarageWeederBank2: received ON for address: A5 (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.3519 GarageWeederBank2: received ON for address: A6 (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.3525 GarageWeederBank2: received ON for address: A7 (GarageWeederBank2) 
>> Sep 26, 2022 3:33:28 AM.3531 GarageWeederBank2: received ON for address: A8 (GarageWeederBank2) 
>> 
>> 
>> Sep 26, 2022 3:33:54 AM.8224 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> 
>> 
>> Sep 26, 2022 3:34:55 AM.3007 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2)
>> 
>> Sep 26, 2022 3:36:57 AM.7889 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> 
>> 
>> Sep 26, 2022 3:37:28 AM.7018 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> 
>> 
>> Sep 26, 2022 3:38:43 AM.1470 GarageWeederBank2: weeder message recieved for unknown weeder ID "ÿ" message: "A11110111" (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:38:58 AM.5399 GarageWeederBank2: port error received 102) (GarageWeederBank2) 
>> Sep 26, 2022 3:39:01 AM.7328  Interface "GarageWeederBank2" has quit with code: 0 () 
>> Sep 26, 2022 3:39:02 AM.2281 BasementWestBank1: WTTCI card at address C timeout waiting for sample. (BasementWestBank1) 
>> Sep 26, 2022 3:39:06 AM.8550 Retry connection to interface "GarageWeederBank2". Tries left: 9 (GarageWeederBank2) 
>> Sep 26, 2022 3:39:06 AM.8576 weeder config string(A3) (GarageWeederBank2) 
>> Sep 26, 2022 3:39:06 AM.8579 Starting Interface "GarageWeederBank2" command: "/Applications/XTension.app/Contents/Resources/Plugins/weeder.isf/weeder.isf IP 127.0.0.1 52301 25 150 A3 10.0.0.71 5000" (GarageWeederBank2) 
>> Sep 26, 2022 3:39:06 AM.9891 GarageWeederBank2: Weeder ISF connecting... (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.6160 GarageWeederBank2: Weeder Chain v2.1 Ready. (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.6553 GarageWeederBank2: Digital Input received weeder packet: (?)A (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.8098 GarageWeederBank2: received ON for address: A1 (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.8173 GarageWeederBank2: received ON for address: A3 (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.8180 GarageWeederBank2: received ON for address: A5 (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.8187 GarageWeederBank2: received ON for address: A6 (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.8194 GarageWeederBank2: received ON for address: A7 (GarageWeederBank2) 
>> Sep 26, 2022 3:39:07 AM.8202 GarageWeederBank2: received ON for address: A8 (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:40:00 AM.7417 GarageWeederBank2: port error received 102) (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:40:03 AM.5437  Interface "GarageWeederBank2" has quit with code: 0 () 
>> 
>> Sep 26, 2022 3:40:08 AM.7148 Retry connection to interface "GarageWeederBank2". Tries left: 9 (GarageWeederBank2) 
>> Sep 26, 2022 3:40:08 AM.7172 weeder config string(A3) (GarageWeederBank2) 
>> Sep 26, 2022 3:40:08 AM.7175 Starting Interface "GarageWeederBank2" command: "/Applications/XTension.app/Contents/Resources/Plugins/weeder.isf/weeder.isf IP 127.0.0.1 52301 29 150 A3 10.0.0.71 5000" (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:40:08 AM.8151 GarageWeederBank2: Weeder ISF connecting... (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:40:09 AM.4388 GarageWeederBank2: Weeder Chain v2.1 Ready. (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.5294 GarageWeederBank2: Digital Input received weeder packet: (?)A (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.6197 GarageWeederBank2: received ON for address: A1 (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.6256 GarageWeederBank2: received ON for address: A3 (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.6263 GarageWeederBank2: received ON for address: A5 (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.6269 GarageWeederBank2: received ON for address: A6 (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.6276 GarageWeederBank2: received ON for address: A7 (GarageWeederBank2) 
>> Sep 26, 2022 3:40:09 AM.6283 GarageWeederBank2: received ON for address: A8 (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:41:58 AM.9378 GarageWeederBank2: weeder message recieved for unknown weeder ID "ÿ" message: "A11110111" (GarageWeederBank2) 
>> Sep 26, 2022 3:42:00 AM.9920 BasementEastBank1: weeder message recieved for unknown weeder ID "Â" message: "B30AE" (BasementEastBank1) 
>> Sep 26, 2022 3:42:00 AM.9928 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> Sep 26, 2022 3:42:01 AM.5316 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> 
>> 
>> Sep 26, 2022 3:42:04 AM.6670 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> Sep 26, 2022 3:42:05 AM.7203 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> 
>> Sep 26, 2022 3:43:00 AM.2423 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2)
>> 
>> Sep 26, 2022 3:43:03 AM.4063 GarageWeederBank2: weeder message recieved for unknown weeder ID "Á" message: "A11110111" (GarageWeederBank2) 
>> 
>> I’ve checked what little code is in the On and Off scripts, and everything appears normal. Also the specific interface WTDIN is selected, and the dip switches are properly set.
>> 
>> This log error can also happen in the log sometimes when trying to talk to it:
>> 
>> <PastedGraphic-1.png>
>> 
>> 
>> Another error not shown is that when I finally get it talking, it will save to B7 that has nothing connected to it yet, but not to B1 & B2 as it is programmed.
>> 
>> Now let me shift gears for a moment and advise at the first of the year, I had to learn how to install a Weeder WTDOT board which is Weeder’s digital output board, and it took me almost 6 months to perfect it because I was trying to use what I call conventional coding and wiring that bundles all the common grounds together and requites that the switch wire for each switch leg be connected to a switch’s terminal. 
>> 
>> Well James finally remembered that this particular board requires just the opposite. All the switching wires are bundled together, and the common wire from each sensor goes to the switch terminals on the board. This was such a departure from the norm for me, I went back to Terry's installation instructions of both types of boards which are very similar and neither instructed me to wire it this way, not even the schematic as far as I can see shows or tells this, yet that’s how the digital output board is wired, and as soon as I made those changes… Bingo.
>> 
>> I’m wondering if I’m fighting some of the same problems I fondly remember with the digital output board. I’ve asked Terry and James and they’ve both said it’s wired just like the WTDIO board I’ve used for years. So I’m at a loss about what to do next, and hope that James or someone who has dealt with this phenomanum before and speaks up because they hopefully see what the problem(s) are from what I’ve provided above.
>> 
>> Sorry for the long email, but as you can see it’s complicated.
>> 
>> Thanks for reading all this,
>> 
>> George
>> 
>> 
>> 
> 
> Thanks,
> James
> 
> 
> James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com
> 
> 
> 
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist

_______________________________________________
XTensionList mailing list
XTensionList at machomeautomation.com <mailto:XTensionList at machomeautomation.com>
http://mail.machomeautomation.com/mailman/listinfo/xtensionlist <http://mail.machomeautomation.com/mailman/listinfo/xtensionlist>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20221010/c6f48eca/attachment.html>

More information about the XTensionList mailing list