<?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:17:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-13T16:10:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.0.1070, 4.1.468, 4.2.182
 
Tested:
 
 
With a S6DB and attached S6 I created a test setup with this hardware
 
In system setting I verified that "Use circular buffer trigger check" is enabled
 
 
 
 
Armed and verified that DAS (S6) were armed prior to arming "accessories"
 
 
 
 
 
Logs to verify S6DB (accessories) gets armed last:
 2023-10-13 09:01:59.567 Entering ArmingService.GetArmStatus on thread 13 with units: (S6DB0010, SL63174, SL60166) Called from: ArmSystem.GetArmStatus Line: 0
  
 2023-10-13 09:01:59.567 -&gt;  Arm - QueryArmAndTriggerStatus [00001451], SL63174, local: 192.168.1.177:52588, Remote: 192.168.4.174:8301
  
 2023-10-13 09:01:59.567 -&gt;  Arm - QueryArmAndTriggerStatus [00001450], SL60166, local: 192.168.1.177:52587, Remote: 192.168.7.166:8301
  
 2023-10-13 09:01:59.567 -&gt;  Arm - QueryArmAndTriggerStatus [00001449], S6DB0010, local: 192.168.1.177:52586, Remote: 192.168.6.10:8301
  
 2023-10-13 09:01:59.568 &lt;-  Arm - QueryArmAndTriggerStatus [00001451]\[00001451] - (0.9641ms), SL63174 Event number: 0, Arm Mode: 1 Armed: True, Started: True, Triggered: False, Faulted: False, Diagnostics: False, FlashClear: False, Arming: False, ArmState: 1 Samplerate: 10000, Current Sample: 10000, Total Samples: 21000, Fault Sample Number: 0 Input Voltage: 11.602V, Backup Voltage: 0.000V, Backup Percentage Remaining: 0% System Temp: 42.94336C, Actual Current Sample: 211600, Max Sample Available: 1355806037 Tilt Ch1: 0, Tilt Ch2: 0, Tilt Ch3: 0 Squib Ch1: 0, Squib Ch2: 0, Squib Ch3: 0, Squib Ch4: 0 Squib P17V: 0, Squib PV5: 0, Squib P3p3V: 0, Squib N5V: 0 PTP Enabled: False, PTP Clk Enable: True, PTP Clk Sync Status: False, ADC Clk Sync Status: True Fault Flags: none Extended Fault Flags: none
  
 2023-10-13 09:01:59.568 SL63174 has completed service ArmingService
  
 2023-10-13 09:01:59.577 &lt;-  Arm - QueryArmAndTriggerStatus [00001450]\[00001450] - (9.9397ms), SL60166 Event number: 0, Arm Mode: 1 Armed: True, Started: True, Triggered: False, Faulted: False, Diagnostics: False, FlashClear: False, Arming: False, ArmState: 1 Samplerate: 10000, Current Sample: 10000, Total Samples: 21000, Fault Sample Number: 0 Input Voltage: 11.876V, Backup Voltage: 0.000V, Backup Percentage Remaining: 0% System Temp: 39.19798C, Actual Current Sample: 215366, Max Sample Available: 1360349866 Tilt Ch1: -6, Tilt Ch2: 643, Tilt Ch3: -834 Squib Ch1: 0, Squib Ch2: 0, Squib Ch3: 0, Squib Ch4: 0 Squib P17V: 0, Squib PV5: 0, Squib P3p3V: 0, Squib N5V: 0 PTP Enabled: False, PTP Clk Enable: False, PTP Clk Sync Status: False, ADC Clk Sync Status: False Fault Flags: none Extended Fault Flags: none
  
 2023-10-13 09:01:59.577 &lt;-  Arm - QueryArmAndTriggerStatus [00001449]\[00001449] - (9.9397ms), S6DB0010 Event number: 0, Arm Mode: 1 Armed: True, Started: True, Triggered: False, Faulted: False, Diagnostics: False, FlashClear: False, Arming: False, ArmState: 1 Samplerate: 10000, Current Sample: 10000, Total Samples: 21000, Fault Sample Number: 0 Input Voltage: 14.912V, Backup Voltage: 8.396V, Backup Percentage Remaining: 0% System Temp: 30.57395C, Actual Current Sample: 10000, Max Sample Available: 21000 Tilt Ch1: 0, Tilt Ch2: 0, Tilt Ch3: 0 Squib Ch1: 0, Squib Ch2: 0, Squib Ch3: 0, Squib Ch4: 0 Squib P17V: 0, Squib PV5: 0, Squib P3p3V: 0, Squib N5V: 0 PTP Enabled: False, PTP Clk Enable: False, PTP Clk Sync Status: False, ADC Clk Sync Status: True Fault Flags: none Extended Fault Flags: none</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-10-13T16:04:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-11T19:35:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-09-12T17:38:00Z</TimeStamp>
    <ReleaseNote>Now arms SLICE devices prior to accessories and distributors</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Changes
 
 
Move Arm and AutoArm service calls to their own methods
 
Separate DAS between devices and "accessories" (EthernetDistributors)
 
Call Arm/AutoArm a second time to arm just accessories after first Arm call finishes
 
 
Testing
 
 
Create a Circular Buffer test with a mix of DAS and "accessories" (non-DAS, so DBs, PowerPro, etc. see Chad's report for details). "Use circular buffer trigger check" should be enabled
 
During arming, you should observe that the DAS are armed first, before the accessories
 
You should not get a status line fault
 
 
Possible Edge Testing to try
 
 
Try with only DAS, no accessories
 
Have accessories in physical system, but not included in test
 
 
Committed to v4.0 maint, v4.1 maint, and v4.2 dev in r49567</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-09-09T00:13:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-31T00:04:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-29T20:33:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-17T22:18:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-15T21:58:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-15T20:17:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-15T20:06:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-01T22:51:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-01T22:50:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>##- Please type your reply above this line -##
 
You have been assigned to this ticket (#12228).
 
 
 
          
Chad J Ivan (DTS)
 
Aug 1, 2023, 13:03 PDT
 
Attached is a set of log files and the test setup for a test that I've been running with the SPDB, SLICE PRO and I've added a POWER PRO unit for these tests.
  
 
 
  
 You end up with a status line fault coming from the PPR and the SPDB, I believe because they get armed first and the SPE/SPS/SPD unit need to have the memory cleared so they are not armed and that causes the status line to be low. 
  
 Maybe we should arm the SLICE PRO/SLICE6/SLICE NANO items first and then arm the accessory items?  
  
 Please advise.
  
 
 
 
Attachment(s)
 DataPRO.log
 2023_08_01 15_26.xml
         
 
 ------------------------------------------------------------
 CUSTOMER DETAILS:
 Name: Chad J Ivan ( chad.ivan@dtsweb.com )
 Organization: DTS
 Customer Details: 
 
You are an agent. Add a comment by replying to this email or view ticket in Zendesk Support.
    Ticket # 12228   Status Open   Requester Chad J Ivan   CCs -   Followers Chris Balogh, Nathan Brown   Group Software   Assignee Dan McFadden   Priority Normal   Type Incident   Channel Web Form    
 
 This email is a service from DTS. Delivered by Zendesk.
 
 [MYN2V4-393LV]Ticket-Id:12228Account-Subdomain:dtsweb</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-08-01T22:50:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>