Messages

1

Support Questions / Re: 3.58 - Comms are super unstable

« on: September 30, 2013, 11:19:55 AM »

Well I figured out when the comms go south.  It is anytime that RSLinx is running.  Comms were fine until I went online with the PLC, then they went bad again.  They stayed bad after I shutdown RSLogix and recovered once I dumped RSLinx.

2

Support Questions / Re: 3.58 - Comms are super unstable

« on: September 25, 2013, 04:46:11 PM »

I get the same result with another selector (no PLC tag) and a button, the value changed event always fires.  Still only 1 in 10 or 1 in 20 on my other selector. 

So I took the other selector and deleted it, then added a new one.  Set it up with PLC tag for click and value, and "toggle".  The selector indicator knob itself moves every time and shows the correct state, but the value changed event only fires off occasionally.

3

Support Questions / Re: 3.58 - Comms are super unstable

« on: September 24, 2013, 01:00:59 PM »

Well CRUD - Or maybe not!

I hadn't saved the WireShark log, so I went to create a new one and check it out.  Since it has been very simple to get comm errors I thought that would take about a minute to do.  Now, it won't error.  I have pressed the selector 500+ times, and run the polling as well without error.  I have seen some retries because of comm timeout, but no errors.

Only change was that I rebooted the laptop a couple times this morning - figures.

Still have no value changed events happening for the selector.  I see if the comm issues reappear in the next few days.

4

Support Questions / Re: 3.58 - Comms are super unstable

« on: September 23, 2013, 06:02:43 PM »

Archie,

Wireshark appears to show that I get about 10 msec turnaround (assuming I am reading it right),  then it just randomly goes bad.  I have attached a screen shot when it went bad.  In this case I was polling with timer events at 250 msec (no more Sleep/DoEvents).  The PLC is .152 in the screen capture.  I sampled all network traffic for 30 seconds and Wireshark said 65 packets/sec and 9.5K bytes/sec on average.

I continue to see the errors I have indicated above, and when the one in the screen capture occurred I received a "False" back from the PLC tag read to see if the test was in progress.  At this point I had only done about 40 cycles out of 500 that the PLC was working on.  I can get the comms to error as well when not polling by just clicking the selector switch over and over 10 - 20 times either slow, or fast.

For the value changed event, I never get it if I click the selector, wait a couple seconds, click it again, and do that like 10 times.  If I click the selector fast I will finally get 1 value changed event if I click it 10 or 15 times.

5

Support Questions / Re: 3.58 - Comms are super unstable

« on: September 19, 2013, 11:10:17 AM »

Archie,

Will do on the sleep.  I will restructure to use a timer to do the UI update and check for test completion.  I will report back after that.  For the DoEvents(), I wanted the UI to be responsive.  I do not have the issue you illustrate because my button is not reentrant, I disable it on click.  But it certainly can be a problem if button presses are reentrant, and in other cases as well.

After my app starts, I hit a button to set the number of test cycles, then start the PLC cycling.  On startup, my app is doing nothing until I hit the button.  So ignoring the polling for the moment till I change it, the selector switch continues to error just sitting there after startup.  It will just randomly get the above listed comm errors.  If you start pressing the selector it will error quicker and more often.   

Also, the selector switch value changed event does not work correctly.  If I have the value changed event implemented, it will go off like only once for every 8 or 10 presses of the selector.

6

Support Questions / Re: 3.58 - Comms are super unstable

« on: September 18, 2013, 04:46:16 PM »

On the selector switch, I am pulling on the corner.  I now see the multi-second delay before it takes effect.  Other buttons just start sizing almost immediately.  Guess I didn't wait long enough.

I currently have the click and value for the selector both set to the same tag.  When I tested it now it is in sync.  I must have had a time earlier when I didn't have the value tag entered.  I will try this again some more later, but it appears to be working now.  When testing this again, I did get all 3 comm errors on the selector that I indicated above.

Here is my polling code:

        Do While Not testComplete
            Try
                Application.DoEvents()
                Threading.Thread.Sleep(500)
                If PLCReadTag("program:Acuman.AcuPT_b_CycleCont_On") = "False" Then ' now, wait for the continuous test latch bit to go off
                    ' EIP Driver seems to like to return wrong value, so lets make sure
                    If PLCReadTag("program:Acuman.AcuPT_b_CycleCont_On") = "False" Then
                        testComplete = True
                    End If
                End If
                If mAbort Then ' or abort to be hit
                    testComplete = True
                End If
                If Not testComplete Then
                    LB_MultiRunProgress.Text = "Tests: " & PLCReadTag("program:Acuman.AcuPT_c_Cycles.Acc")
                Else
                    LB_MultiRunProgress.Text = ""
                End If
            Catch ex As Exception ' the comms errors often, and would normally bail out of here, so just keep going for now
                ' MessageBox.Show(ex.Message)
            End Try
        Loop

    ' read a single PLC value
    Private Function PLCReadTag(ByVal tag As String) As String
        Dim rtnVal As String()
        rtnVal = EthernetIPforCLXCom1.Read(tag, 1)

        Return rtnVal(0)
    End Function


I have seen the "Tests: 1" label count up for a while, then show "Tests: True".  The polling loop would always bail within a minute thinking it read "False" for the on bit until I added the double check

I attached the PLC rung for the ...CycleCont_On bit.

7

Support Questions / 3.58 - Comms are super unstable

« on: September 18, 2013, 03:14:16 PM »

I installed 3.58 and built a little project using it.  I am building this and running it on the same laptop that is running RSLogix 5000 without issue online with the PLC.

First off (not comm related), the Selector Switch component doesn't allow sizing.  You have to go manually change the size property.

Next, if you hit the selector switch once, it will work.  Hit it again after a second, all is OK.  But press it like 4 or 5 times in a row and it will then show the wrong state (the PLC tag will be on, but selector is off, or vis versa).

Then the selector text will randomly display comm errors, then recover.  The errors I have seen in the text are "Read failed result = -20.  No data returned.", "No response form PLC(21). Invalid value.", and "Object reference not set to an instance of an object."

So the selector button doesn't look very promising, but the comms gets much worse when I try to poll tags in the PLC for cycle counter and "running" state.  So I built a loop that pauses 1/2 sec, then reads the running state and cycle count.  I get he following errors on the tag reads:

- cycle count will occasionally return "True" rather than a number.
- "running" will return "False" (or Not "True") when the tag is latched up and the testing is still running in the PLC program.  If I read again immediately after the first "False" read, it will come back correctly as "True".  This bit is absolutely latched up in the PLC.
- No response from PLC(21).
- Read failed result = -20.  No data returned.
- Exception type MFGControl.AdvancedHMI.Drivers.PLCDriver.Exception was thrown.

It appears this is not ready for primetime, and is definitely not usable by me in its current state.  Are there any other comm settings besides those on the EthernetIPforCLXCom1 properties?