Error Codes

Wed Sep 7 09:04:06 EDT 2022

Hi George. You message came through with no issues. The error is just a non-printable character. That simply means there was something in the data path that did not translate to an actual ASCII character. In my experience usually something like that is because of static on the wire of something similar. I would relate it to something similar to the error 54 or 102 you asked about earlier. It just happens to manifest it self in a slightly different way because it is being seen at a different level in the software stack, I believe. So again, it is not very helpful but tells you there is something going on there. I have no experience with the Weeder boards so I am afraid I will not be much help in troubleshooting things.

As to the graphics and the list, I have never had an issue sending screenshots, but I do know that various Macs can create very large screenshots. I try to reduce the size of any graphic I am sending via email. Easiest way to do that is to use the Preview App to open the screen shot. Then choose “export” from the file menu. That will allow you to choose the quality of the image. By choosing a lower quality, that will reduce the size of the graphic and you should have less chance of it being too big for the list server system.

-tom

> On Sep 7, 2022, at 2:23 AM, George Handley <ghandley at kc.rr.com> wrote:
> 
> Dear Tom and Jefferey,
> 
> Thanks for writing to say you received my earlier email. I didn’t, and in fact if Tom hadn’t attached my questions to his reply I would have again thought it was never received. Jeffrey, I subscribe to both the Digest as well as the realtime List
> 
> Tom, a special thanks to you for your explanations regarding your experiences with code errors. I gad completely overlooked that they might be AppleScript errors and I’m sure some of them have to be. but I didn’t want to take a chance sending even a small pix to the List, because it can’t handle it
> 
> This is what I really wanted to send last night, but knew the List would choke on it. That’s why I have also sent this to you personally. Hope it gets through one ay or the other.
> 
> <Pasted Graphic.png>
> 
> 
> I had to take a small pix of this new error symbol and am sending to you both as well as the list which will probably choke on it. One other time this these control type chars started up uninvitedly in new and (Most disconcerting) in some of my existing working code (For years) began getting them too.  I know you’re going to ask, and yes they disappeared after a while for another equally puzzaling problem. 
> 
> I hope you can see why I thought I was dealing with a Weeder problem. Any idea what could cause this sort of thing. Is it old hardware or a patch cord? Sometimes I find this diamond shaped character invisible.
> 
> Again, thanks,
> 
> George
> 
> 
>> On Sep 6, 2022, at 9:02 AM, Tom Yarmas <tom at yarmas.com <mailto:tom at yarmas.com>> wrote:
>> 
>> George,
>> 
>> I believe those errors are just passed through from Mac OS, so they are not specific to the W800 or the Weeder. XTension is just raising the error that it received from a lower level. 
>> 
>> In the case of Errno 54 and port error 102, they are communications errors. I would look at port error 102 as something that happened on TCP port 102. Could be a communication error, flow control, who knows. Just that the application saw something wrong on port 102. I have read reports of getting that error even though a file transfer completed successfully. In that case, the error likely happened during the close up of the transfer protocol and was just a remnant or something of the actual file transfer.
>> 
>> Similar for errno 54 - it is a communication error and the connection was reset because of it. Basically, one end of the communication threw up their hands and just said “reset, I can’t figure this out”. Not very good for troubleshooting, but all that the application and XTension can do since there is really nothing else to report. If these things keep happening, you might look at the physical connection and see if there are loose wires or something else that may hamper the communications.
>> 
>> The scripting error is an AppleScript thing. And historically, AppleScript has been horrific in providing helpful error codes or troubleshooting information. A little internet searching may help here. I found the following about that AppleScript error that may or may not help you.
>> 
>> It seems that the 1708 error may have to do with scoping of scripting calls. From this post https://stackoverflow.com/questions/2663812/handler-call-error-in-tell-block-in-applescript <https://stackoverflow.com/questions/2663812/handler-call-error-in-tell-block-in-applescript>
>> I learned that when using a Tell block and calling a script, AppleScript expects to find the script/function being called within the program being called by the Tell block. So they say defining the scope of the script with my in front of it may help. That basically help AppleScript to be aware of where to find the content of the script being called and not to look for it in the wrong place, not finding it and throwing the error.
>> 
>> I have no idea what actually was going on when you received the 1708 scripting error, but you may look to see what the script was trying to do and if scope of a script or function being called might have been the issue.
>> 
>> Anyway, using a simple google search on the errors that get thrown may lead you to some answers, but be aware that the search results will be many and weeding through them may be slow and painful.
>> 
>> Good luck.
>> 
>> -tom
>> 
>> 
>>> On Sep 6, 2022, at 1:09 AM, George Handley <ghandley at kc.rr.com <mailto:ghandley at kc.rr.com>> wrote:
>>> 
>>> Dear XTensioneers,
>>> 
>>> Everything, including me is getting older in my system. It’s now pretty much been up and running for 13 years and things are beginning to fail, just like my parts. :-)
>>> 
>>> I have found that when it comes to any of my Weeder chains (No more than 3 per chain) that a new Weeder card “might” be the solution, and surprisingly a new WizNet card can sometimes resolve the problem. Other times neither with help.
>>> 
>>> I’ve looked in all the obvious places, but can’t find a list of Weeder,  WizNet, MaxSonar or W800 error codes and are in hopes someone here happens to know what the following error codes are because I’m being besieged with them.
>>> 
>>> "W800 connection error [Errno 54] Connection reset by peer"
>>> 
>>> Weeder error  “port error received 102” is my biggest culprit 
>>> 
>>> Scripting error -1708
>>> 
>>> Can anyone clarify what those errors really mean?
>>> 
>>> Thanks,
>>> 
>>> George
>>> _______________________________________________
>>> 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>
>> 
>> _______________________________________________
>> XTensionList mailing list
>> XTensionList at machomeautomation.com <mailto:XTensionList at machomeautomation.com>
>> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20220907/36c5e249/attachment.html>