<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T16:15:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with v4.0.1068, 4.1.464, 4.2.168
 
While working at home I had multiple devices on same switch (Xbox, Raspberry PI, and DTS Laptop, and S6A connected via test device)
 
In Data Recorders tab I selected Auto Discovery to send out UDP command. S6A that was connected to this switch was discovered and no crash was observed. Queried and saved to Current DAS list:</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-10-11T17:31:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>will try this out with a raspberry pi on the same network (private) to verify no crash observed</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-03T22:25:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-09-28T18:44:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-08-01T18:17:07Z</TimeStamp>
    <ReleaseNote>Addresses a crash in hardware discovery</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1./4.2@49247
 
- might be hard to duplicate's issue pre-patch, but the way would be to have an ip that responds to pings (and maybe is in the HWIPRanges.txt file)
 
however it should still operate normally to hardware discovery, so I guess there's still something to test, just add a test setup, then discover hardware and save and done.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-07-25T17:18:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-25T17:14:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>##- Please type your reply above this line -##
 
You are a follower on this request (#12193, #dtsweb.zendesk.com/agent/tickets/12193). Reply to this email to add an internal note to the request.
 
 
 
          
Chris Balogh (DTS)
 
Jul 25, 2023, 09:20 PDT
 
Hi Kate,
  
 Not the log. I'm asking if you have the ip list file somewhere in your DP dir. That will always be used on discover to see if those IPs are live.
  
 Chris
 
 
         
 
          
Kate Martin (DTS)
 
Jul 25, 2023, 09:18 PDT
 
here you go
  
  
 === 2023-07-25 15:32:00.450    ping succeeded:  192.168.1.74  -&gt;  192.168.1.22
 === 2023-07-25 15:32:00.453    ping succeeded:  192.168.1.74  -&gt;  192.168.1.47
 === 2023-07-25 15:32:00.461    ping succeeded:  192.168.1.74  -&gt;  192.168.1.24
 === 2023-07-25 15:32:00.783    ping succeeded:  192.168.6.99  -&gt;  192.168.6.42
  
  
 
 
 
Attachment(s)
 ping.log
         
 
          
Chris Balogh (DTS)
 
Jul 25, 2023, 09:15 PDT
 
Kate,
  
 ping list file in your DP dir?
 
 
         
 
          
Kate Martin (DTS)
 
Jul 25, 2023, 08:30 PDT
 
Thxs Dan
  
 This is what I was refering to when I say devices respoinded to a UDP broadcast - else where would DataPro get these IP's from ?
  
 2023-07-25 15:31:59.854 User Admin pressed PageButton:Hardware_DataRecorders_HardwareDiscovery_Page_ScanButton
  
 2023-07-25 15:31:59.854 User Admin pressed Hardware_DataRecorders_HardwareDiscovery_Page_ScanButton
  
 2023-07-25 15:32:00.060 Starting ping process
  
 2023-07-25 15:32:00.060 192.168.1.100,192.168.1.22,192.168.1.24,192.168.1.47,192.168.6.42,
  
 2023-07-25 15:32:01.787 Ping function complete
  
 2023-07-25 15:32:01.787 status:  192.168.1.100 PING_FAILED
  
 2023-07-25 15:32:01.787 status:  192.168.0.34 UNKNOWN
  
 2023-07-25 15:32:01.953 Refresh
  
 2023-07-25 15:32:02.358 Connecting to 192.168.6.42 on 192.168.6.99
  
 2023-07-25 15:32:02.365 Failed to connect to 192.168.6.42 will retry
  
 2023-07-25 15:32:02.372 Connecting to 192.168.1.24 on 192.168.1.74
  
 2023-07-25 15:32:02.372 Connecting to 192.168.1.47 on 192.168.1.74
  
 2023-07-25 15:32:02.372 Connecting to 192.168.1.22 on 192.168.1.74
  
 2023-07-25 15:32:02.382 Connecting,  192.168.6.42:8301
 
 
         
 
          
Dan McFadden (DTS)
 
Jul 25, 2023, 08:18 PDT
    Private note    
 
interesting, I'm not aware of any other devices that respond to our UDP requests, I'm not sure why they would respond to them.
 
this appears to be the issue causing the crash, I'll safeguard it;
 
2023-07-25 15:40:14.069 !!  An exception of type: System.NullReferenceException occurred Module: DataPRO.exe, Name: AddGroupsToTestSetupMessage: Object reference not set to an instance of an object. StackTrace:    at DataPROWin7.Controls.HardwareDiscoveryControl.AddGroupsToTestSetup(IDASCommunication sourceDAS, List`1 staticGroupList, List`1 dasIdList, DASHardware hardware, TestTemplate testTemplate, Dictionary`2 sensorAndCalibrationList, Dictionary`2 eidList, List`1&amp; assignedEIDList, List`1&amp; conflictingEIDList) StackTrace:    at DataPROWin7.Controls.HardwareDiscoveryControl.UpdateChannels()    at DataPROWin7.Controls.HardwareDiscoveryControl.UpdateTableInfo()    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
  
 2023-07-25 15:40:14.070 DataPRO has experienced an issue.  The issue has been recorded.  DataPRO will now shutdown for safety.
 
 
                                                                                              Dan McFadden​   Software Engineering Manager               Diversified Technical Systems, Inc.  |  Seal Beach ,  CA                   e:     dan.mcfadden@dtsweb.com     |         o:     +1 562 493 0158 x137     |     www.dtsweb.com                                       CONFIDENTIALITY: This email and any attachments may contain information from Diversified Technical Systems, Inc. (DTS) which​ is confidential ​and/or proprietary. If you received this transmission in error, any use, reproduction or dissemination of this transmission​ is strictly prohibited. ​Please delete this message and notify sender immediately.  
 ​EXPORT CONTROL NOTICE: This e-mail may contain technical data whose export, transfer, and/or disclosure may be controlled by​ the US ​International Traffic in Arms Regulation (ITAR) 22 CFR part 120-130 or the Export Administration Regulations (Commerce).
 ​
 ​                                  
 On 7/25/2023 8:01 AM, Kate Martin (DTS) wrote:
 
 
 
         
 
          
Kate Martin (DTS)
 
Jul 25, 2023, 08:01 PDT
 
Hi Dan, Chris
  
 Here is a good example of DataPro crashing when trying to connect to non DTS devices that reply to a UDP broadcast ...
  
 The problem is devices at 192.168.1.22, 192.168.1.24 and 192.168.1.47 on my home network responded to a UDP broadcast from my wifi NIC @ 192.168.1.74 along with the actual DTS device on 192.168.6.42 on my ethernet USB dongle @ 192.168.6.99
  
 This is fine (better if we can MAC filter to remove these erroneous connections ?) but we shouldn't then bomb out ... 
  
 
 
 
 
Attachment(s)
 DataPRO.log
         
 
----------------------------------------------
 Customer Details:
 Name: Kate Martin ( kate.martin@dtsweb.com )
 Organization: DTS
 
----------------------------------------------
 If you no longer wish to see notifications for this ticket, please use the 'Unfollow' option in the Followers List.
 
 
You are an agent. Add a comment by replying to this email or view ticket in Zendesk Support.
    Ticket # 12193   Status On-hold   Requester Kate Martin   CCs -   Followers Chris Balogh, Dan McFadden   Group Support   Assignee Kate Martin   Priority Normal   Type Problem   Channel Web Form    
 
 This email is a service from DTS. Delivered by Zendesk.
 
 [PKNM2D-E4RVL]Ticket-Id:12193Account-Subdomain:dtsweb</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-07-25T17:14:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>