<?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:21:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with 4.0.1081, 4.1.485, 4.2.218
 
Tested:
 
 
Using db from 4.2.218, 4.1.485, and 4.0.1081 (with S6A and UART test setup)
 
Attached this db to central db
 
Ran DataPRO 4.0.957 and set the following attributes.
       &lt;setting name="UseNTLMAuthentication" serializeAs="String"&gt;
         &lt;value&gt;True&lt;/value&gt;
       &lt;/setting&gt;
       &lt;setting name="DBType" serializeAs="String"&gt;
         &lt;value&gt;0&lt;/value&gt;
       &lt;/setting&gt;
       &lt;setting name="LocalDbHost" serializeAs="String"&gt;
         &lt;value&gt;asada&lt;/value&gt;
       &lt;/setting&gt;
 
Opened 4.0.957 and did not observe a crash</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-11-08T00:13:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-11-06T22:19:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Performance testing with 1 channel doesn't show improvement in 4.0. However, testing with many channels should, and testing with 1 channel in 4.1 shows a 33% improvement due to the performance improvements when getting all channel settings in a single db call.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-11-06T15:26:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Fixes for bug introduced in 4.0.985, 4.1.339, and 4.2.18 when implementing this feature:
49817 is 4.0; 49818 is 4.1; 49819 is 4.2

To test:
Run a version of DataPRO that has a native database version of 95 (4.1.312 or later) and create a Test Setup with a SLICE6Air with a UART channel.

Put that version 95 database on a central server.

Run a version of DataPRO that has a native database version of 94 (4.0.957 or later) and use the version 95 database.

Open the Test Setup for editing and ensure that a crash doesn't occur.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-27T18:59:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-25T21:26:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Reactivating based solely on 4.1.476 (4.0.1075 kept crashing for me)
 
Set up clumsy application with the details as mentioned:
 
 
Clicked start and immediately "run test" was clicked. This caused DataPRO to take over 1 minute (maybe 2 minutes) to get into run test. Reactivating based on notes that took over a minute after clicking run test and getting into basic info of run test. 
 
Log attached.</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-10-19T16:13:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-18T23:17:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-10T18:55:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>To test:

Install a Centralized HRA database appropriate to your version (4.0, 4.1, etc.) on asada or other server.

Import the attached Test Setup, SPS.xml.

Run clumsy.exe. In clumsy:
    1) choose "all ipv4 against specific ip" in the Presets dropdown, 
    2) change the ip addresses in the text box to the ip address of the server being used (if using asada the text would be "ip.DstAddr == 192.168.2.116 or ip.SrcAddr == 192.168.2.116") ,
    3) check the Lag checkbox, and
    4) Click the Start button.

Click on the Run Test tab.

Measure time from clicking on Run Test to the appearance of the Basic info step.  It should improve markedly from the time taken prior to the fix.

Additionally, clicking on the Done button should not cause a crash.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-10T18:53:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Don't crash when Done button is clicked and CurrentTestSetup.Groups is null.
49343 is 4.0; 49345 is 4.1; 49344 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-07T21:27:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Don't throw Exception when Done button is clicked and CurrentTestSetup is null. This bug was introduced in 4.0.983, 4.1.346, and 4.2.29.

49310 is 4.0; 49311 is 4.1; 49312 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-01T23:43:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-08-01T18:17:36Z</TimeStamp>
    <ReleaseNote>Improves central database performance</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-01T18:17:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Whoops, forgot to commit the database files.
49245 is 4.1; 49246 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-24T23:07:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The following patches reduce the number of calls to get Group Channel Settings (values in the Parameters step of Run Test) from one/channel to one, by passing a list of Channel IDs to the stored procedure, instead of only one Channel ID at a time.

To test:
Run a Test Setup and view the DB.log.

49238 is 4.1; 49239 is 4.2</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-07-24T18:58:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-20T19:33:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-20T15:02:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49218 is 4.0; 49219 is 4.1; 49220 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-19T22:39:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The following patches fix a bug that fails to show list of Test Engineers in the "Engineer preset" combo box in the Test Details section of Edit Test Setup that was introduced in 4.0.49178, 4.1.49179, and 4.2.49180.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-19T22:37:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T22:53:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-18T18:33:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-13T22:40:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-13T21:03:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-13T19:57:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-13T19:39:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The following improve performance by reducing the number of db calls via caching of Sensors, Sensor Calibrations, Customer/Laboratory/Test Engineer Details, and Channel Settings.

49178 is 4.0; 49179 is 4.1; 49180 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-12T21:59:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-06T17:21:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T17:22:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Added logging to db access points to aid in analyzing performance.

49183, 49184, 49185, 49187, and 49188 are 4.0; 49144 is 4.1; 49145 is 4.2</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-29T16:11:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-28T15:03:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Order of attack based on slowest steps when using a clumsy connection:
Run Test
    From Run Test button to Basic info step
    Leaving Run Test via the Done button
    Preparing for Diagnostics
    Check sensor ID, Check trigger, Diagnostics Run
    Hardware
    Download
Save Test Setup
Edit Test Setup
Initialization of DataPRO (to login screen or Test Setups tab)</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-23T22:50:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-20T16:09:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:58:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:53:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:47:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:41:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:34:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:31:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:29:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:23:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T21:22:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T20:52:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T20:47:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T15:55:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>created a 48 Channel S6DB test with the database on ASADA.
 
using 4.1:
 
on my machine it took 18s to start from the IDE until the test setups tab was shown.
 
double clicking on DansTestSetup it took 9s before the warning prompt was shown with all the warnings.
 
clicking on automatic and unclicking and saving it took 16s before the warnings were shown (and it still said modified for some reason after saving?)
 
trigger was shorted on SL60372, so I had to remove it and it's channels from the test.
 
had to give my equipment up to JR, so decided to switch to ECM+SPSx3, in the process Add test setup took about 11s before it showed up on the new page, took 42s to save new test (DANSPSTEST)
 
it took 2:19 skipping trigger check to get to download.
 
using clumsy to up the lag to 100ms makes the time to run a test unbearable, I gave up after 4 minutes.
 
this suggests there's a lot of tiny frequent queries where it might be possible to replace with single huge queries.
 
(like getting channels for example)
 
even if I wait till the test is fully loaded in run test in basic info to turn on clumsy the delay is unbearable.
 
many steps of run test become noticably slower, like check sensorid which becomes incredibly slow, it seems like there's database queries here that can be eliminated - setting a breakpoint and checking it out, sure enough I see database queries like "sp_SensorsAnalogGet", and I see this function getting called on a lot of pages of run test at the start.
 
it also seems stuck in "StoreTestSetupXML"
 
one example of this is s                        var sensor = CurrentTest.GetSensor(rch.Channel); in OutputReports which is called at the end of CheckSensorID before going to CheckTrigger
 
also note that none of these calls appear to be using the version which lets you get all sensor calibrations at once and pass them in rather than having multiple queries for calibration;
 
public SensorData GetSensor(DTS.Common.Interface.Channels.IGroupChannel groupChannel, IReadOnlyDictionary&lt;string, SensorCalibration&gt; calLookup = null)
 
note that it's possible to cached sensors in sensors list already;
 
public void SetCache(SensorData[] cachedSensors, SensorData [] originalCachedSensors)
 
by setting the cache in run test and making sure it's cleared when we are done there's probably a good performance boost.
 
there are functions app.StartTest and app.EndTest that mark the start and end of a test.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-13T15:53:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>First measurements using HRA's databases 3.1, 3.3, 4.0, and 4.1 with DbType = 0, 1, and 2 is attached.
Test was simple: 1 channel on a SPS, and took just over a minute to get from Basic Info to Armed.
Next measurements should use multiple TDAS racks with TOMs, etc. similar to what is shown in the Logs.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-09T14:54:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-06-08T14:25:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-07T20:14:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-07T14:16:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-23T18:29:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-23T18:29:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-23T18:08:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-17T21:36:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>HRA databases (3.1, and migrations to 3.3, 4.0, and 4.1) are here:
\\dts\files\Software\Private\Useful_Test_Files\DataPRO\DB_BACKUPS\HRA\zd11888

and here temporarily:
C:\Jerry\HRA on asada</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-05-17T21:36:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>