Announcement

Collapse
No announcement yet.

X10 ERROR (Ti103) "...Argument 'Start' must be greater than zero" [Resolved]

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    X10 Error

    Originally posted by mfisher View Post
    Thanks for the additional log entries, they are most helpful. I just posted v.46b, please install this version and post the resulting log entries.

    It looks like something may have happened with a recent Windows update and/or the .Net library that is affecting how serial port data is being treated, and this debug version should help give better visibility into what's going on. Unfortunately I cannot get this to fail on my Win10 dev machine so I'll still need your help to continue testing.
    Happy to help. Installed .46B. Will post any results.

    BTW remember I am running Windows 7 Ultimate.

    Thanks
    Ed

    Comment


      #32
      Thank you Sir! Yes, I have notes in the source that this affects Win7 Ult.
      Best regards,
      -Mark-

      If you're not out on the edge, you're taking up too much room!
      Interested in 3D maps? Check out my company site: Solid Terrain Modeling

      Comment


        #33
        X10 Error

        Good Morning,

        Several seem to have some different data! hope this is a clue to what is going on. Once again many thanks for your time and effort in trying to find this issue.



        Feb-10 6:21:10 PM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=1, buf=[23], rbuf=[], strTemp1=[#], strTemp2=[#], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-10 6:21:10 PM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=1, buf=[23], rbuf=[], strTemp1=[#], strTemp2=[#], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-10 8:54:23 PM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=1, buf=[23], rbuf=[], strTemp1=[#], strTemp2=[#], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-10 9:43:38 PM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=1, buf=[23], rbuf=[], strTemp1=[#], strTemp2=[#], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-10 10:22:16 PM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=1, buf=[23], rbuf=[], strTemp1=[#], strTemp2=[#], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-10 11:15:29 PM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=8, buf=[42-00-00-00-00-00-00-00], rbuf=[], strTemp1=[B], strTemp2=[B], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-11 3:58:20 AM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=8, buf=[42-00-00-00-00-00-00-00], rbuf=[], strTemp1=[B], strTemp2=[B], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-11 5:52:10 AM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=10, buf=[24-3C-32-38-30-30-21-34-42-23], rbuf=[], strTemp1=[$<2800!4B#], strTemp2=[$<2800!4B#], Trips= 1: Argument 'Start' must be greater than zero.

        Feb-11 6:27:03 AM X10 ERROR Error in Ti103.MSComm1_OnComm() on line 170, c=0, buf.len=1, buf=[23], rbuf=[], strTemp1=[#], strTemp2=[#], Trips= 1: Argument 'Start' must be greater than zero.

        Comment


          #34
          Great data, thank you Ed! Please install v.46c and post the log entries. I think we're getting close...
          Best regards,
          -Mark-

          If you're not out on the edge, you're taking up too much room!
          Interested in 3D maps? Check out my company site: Solid Terrain Modeling

          Comment


            #35
            X10 Error

            Originally posted by mfisher View Post
            Great data, thank you Ed! Please install v.46c and post the log entries. I think we're getting close...

            46c is filling log on start


            Feb-11 3:43:37 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:37 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[]
            Feb-11 3:43:36 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:36 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[]
            Feb-11 3:43:36 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:36 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[]
            Feb-11 3:43:36 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:36 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=124, rbuf=[$<2800!4]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:35 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:34 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]
            Feb-11 3:43:34 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:34 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]
            Feb-11 3:43:34 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:34 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]
            Feb-11 3:43:34 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[]
            Feb-11 3:43:33 PM X10 ERROR Error in Ti103.MSComm1_OnComm(): call count=123, rbuf=[$<2800!4]

            Comment


              #36
              Yikes, sorry about that! v.46d will resolve that and I think should fix the problem. Please let me know what you find.
              Best regards,
              -Mark-

              If you're not out on the edge, you're taking up too much room!
              Interested in 3D maps? Check out my company site: Solid Terrain Modeling

              Comment


                #37
                X10 Error

                Originally posted by mfisher View Post
                Yikes, sorry about that! v.46d will resolve that and I think should fix the problem. Please let me know what you find.
                Don't see 46d in the downloads?

                Comment


                  #38
                  I thought I had saved that post but apparently I did not. Sorry about that, it's up there now.
                  Best regards,
                  -Mark-

                  If you're not out on the edge, you're taking up too much room!
                  Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                  Comment


                    #39
                    X10 Error

                    Originally posted by mfisher View Post
                    I thought I had saved that post but apparently I did not. Sorry about that, it's up there now.
                    OK, Have 46d online. Will keep you posted!

                    Thanks

                    Comment


                      #40
                      X10 Error

                      Thought we were going to make it for 24hrs without errors... Then

                      Feb-13 12:20:47 PM X10 ERROR Ti103.CommThreadLoop(): calls=0

                      Feb-13 10:09:01 AM X10 ERROR Ti103.CommThreadLoop(): calls=0

                      Feb-14 2:32:02 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                      Feb-14 2:32:02 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                      Feb-14 2:32:02 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                      Feb-14 2:32:01 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                      Feb-14 2:32:01 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                      Feb-14 2:32:01 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                      Feb-14 2:32:01 AM X10 ERROR Ti103.CommThreadLoop(): calls=0

                      These are the only thing in the log

                      Thanks

                      Ed
                      Last edited by edwilloughby; February 14, 2018, 05:08 AM.

                      Comment


                        #41
                        Hi Ed, this is great news! That message is not actually an error - I wanted these to stand out in the log so its logged as an 'error' but this is purely informational and indicates that MSComm1_OnComm is being called from a different place in the Ti103 code.

                        What we are looking for is the error message you originally posted about. If that does not rear its ugly head in the next few days then I would say the issue has been resolved. Please post all debug messages for the plugin that you see over the next few days, and if all we see are these debug messages I'll publish a final build of v.46.

                        Thanks for your help in debugging this!
                        Best regards,
                        -Mark-

                        If you're not out on the edge, you're taking up too much room!
                        Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                        Comment


                          #42
                          X10 Error

                          Originally posted by mfisher View Post
                          Hi Ed, this is great news! That message is not actually an error - I wanted these to stand out in the log so its logged as an 'error' but this is purely informational and indicates that MSComm1_OnComm is being called from a different place in the Ti103 code.

                          What we are looking for is the error message you originally posted about. If that does not rear its ugly head in the next few days then I would say the issue has been resolved. Please post all debug messages for the plugin that you see over the next few days, and if all we see are these debug messages I'll publish a final build of v.46.

                          Thanks for your help in debugging this!
                          That sounds good to me. Thanks for all of the hard work in debugging this issue. I will keep a keen lookout on the log for the next several days and post anything that comes up.
                          Again

                          Thanks

                          Comment


                            #43
                            X10 Error

                            So far the only thing showing up in the log is: No sign of the comm error


                            Feb-16 11:24:57 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:57 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:57 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:56 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:56 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:56 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:56 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:07 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:07 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:07 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:06 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:06 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:06 AM X10 ERROR Ti103.CommThreadLoop(): calls=0
                            Feb-16 11:24:05 AM X10 ERROR Ti103.CommThreadLoop(): calls=0

                            Comment


                              #44
                              Thanks Ed, this is great news! I have another change that I'd like to make and have you test before we call this one closed, and I'll try to get a build posted this weekend.

                              Thank you again for your help!!
                              Best regards,
                              -Mark-

                              If you're not out on the edge, you're taking up too much room!
                              Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                              Comment


                                #45
                                Hi Ed, I just posted v46e which changes how the issue is handled and reported. The debug messages will still be shown as errors so they stand out in the HS log, but they are not really errors.

                                Please load this version when you get a chance and post the results. I think this is resolved but I'd like to understand the timing of the interaction between the two calling mechanisms that were causing the issue.

                                Thanks!
                                Best regards,
                                -Mark-

                                If you're not out on the edge, you're taking up too much room!
                                Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                                Comment

                                Working...
                                X