Files
squad/legacy/CCNetLogReader/CCNetLogReader/bin/Debug/FogbugzLog/29554.638205436810000000.xml
2025-07-22 11:34:56 -04:00

292 lines
9.7 KiB
XML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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>2023-05-24T20:48:01Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Jaime Lopez</User>
<Comment>Verified w/ DataPRO v.4.1.213, 4.0.861
Tested:
Reset arm and system attributes back to default via FWTU
Enabled logging via Tilt Sensor SW 
In DataPRO created a test setup and armed. 
Once complete navigated to Data folder -&gt; my test setup -&gt; event -&gt; Temperature folder</Comment>
<StatusString>Closed</StatusString>
<TimeStamp>2023-02-21T22:57:25Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>Closed</Status>
</FBEvent>
<FBEvent>
<User>Chris Balogh</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2023-02-13T16:44:57Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Jaime Lopez</User>
<Comment />
<StatusString>Assigned</StatusString>
<TimeStamp>2023-02-07T21:00:41Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>ReleaseNoted</StatusString>
<TimeStamp>2023-01-18T22:48:13Z</TimeStamp>
<ReleaseNote>S6DB will now download a temperature CSV into a temperature folder in dataset when available</ReleaseNote>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-18T22:47:45Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>4.0/4.1@48071
Need to also be tested with S6DB attributes cleared, like a brand new S6DB, and with and without RTC</Comment>
<StatusString>Resolved</StatusString>
<TimeStamp>2023-01-16T23:44:48Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>Resolved</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>I do not know of a why of ordering the channels in the output from the S6DB, my assumption is that they are in order that they are in the UI, so:
            OnBoardTemp,
            OnBoardHumidity,
            EnvironmentalCh1,
            EnvironmentalCh2,
            EnvironmentalCh3,
            EnvironmentalCh4,
temperature should always be before humidity if both are selected.</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-16T19:15:52Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>to download CSV of temperature logs you must have configured the S6DB to enable logging - you can use the TiltControl v 2.1 application to do this.
press discovery hardware, then connect to your S6DB
I had to go into the visual studio IDE to enable visibility on MCU temp/MCU humidity to try to log any other settings, but those didn't actually log for me.
Anyhow, you'll need to enable logger with at least 1 sensor, although only the MCU temp/humidity produced logs for me?
you will probably need to restart the S6DB before it starts logging temperatures.</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-16T19:04:29Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-16T18:51:31Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>added "Temperature time format" and "Temperature value format" into System settings-&gt;Test settings-&gt;Data export options
 
changing temperature time/output format in System settings-&gt;Test settings-&gt;Data export should change output in CSV, and restore should restore the settings to defaults.</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-16T18:45:42Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>Subject:
Temperature Logging Download in DataPRO
From:
Chad Ivan &lt;chad.ivan@dtsweb.com&gt;
Date:
1/11/2023, 12:31 PM
To:
Dan McFadden &lt;dan.mcfadden@dtsweb.com&gt;
CC:
Nathan Brown &lt;nathan.brown@dtsweb.com&gt;
 
Dan,
 
I was able to test the SLICE6DB3 unit today and here is what I found..
 
Tilt Sensor Control 2.0.68.46716 seems to work correctly, I was having issues with 2.1 versions.
 
 
After enabling logging and rebooting the ATD via the ON/OFF switch I was able to hit the “Read” button and get samples to show in the grid on the left and the graph updates.
 
Clicking on the Save to CSV creates the file attached.  I have added a (PREFERED) file that takes the “T” out between the Date and Time.  That imports into EXCEL nicely.
 
If we were able to download that file that should fulfill any customer requirement for logging the temperature, or at least its going to be a great starting point. 
 
Thanks for your help,
Chad
 
 
 
Attachments: Temp_S6DB30013_2023-01-11T15.21.24.csv 506 bytes Temp_S6DB30013_2023-01-11T15.21.24(PREFERED).csv 377 bytes</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-14T00:25:44Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>patch ready, waiting for chris as there's not enough information on the current temperature logger behavior</Comment>
<StatusString>Assigned</StatusString>
<TimeStamp>2023-01-06T16:05:09Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>note, you'll want to use the most recent FWTU when setting battery install date, etc, previous revisions may have filled in different fields than the UI shows.</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-04T18:37:01Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Assigned</StatusString>
<TimeStamp>2023-01-04T16:52:04Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>loading M7 on another S6DB to attempt to bypass issue with s6DB in question (could not communicate with ethernet switch according to EP)</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-04T16:51:53Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>Yuba/S6DB currently not booting, waiting for f/w to check it out</Comment>
<StatusString>Assigned</StatusString>
<TimeStamp>2023-01-04T16:18:16Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-03T19:10:00Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>note, current S6DB test board is set for WIAMan, requires 20V input</Comment>
<StatusString>Edited</StatusString>
<TimeStamp>2023-01-03T16:40:23Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Assigned</StatusString>
<TimeStamp>2022-12-13T22:56:49Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2022-12-13T19:50:58Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Chris Balogh</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2022-10-20T21:22:47Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Edited</StatusString>
<TimeStamp>2022-08-26T17:48:20Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment />
<StatusString>Assigned</StatusString>
<TimeStamp>2022-08-26T17:47:44Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>UNKNOWN</Status>
</FBEvent>
<FBEvent>
<User>Dan McFadden</User>
<Comment>§When downloading data from tests, temperature log should be downloaded into a Temperature folder added to the test data folder, data will be in .CSV file format, corrected for local time (not UTC) so it matches high speed data time stamps</Comment>
<StatusString>Opened</StatusString>
<TimeStamp>2022-08-26T17:47:44Z</TimeStamp>
<ZendeskNumber>0</ZendeskNumber>
<Status>Opened</Status>
</FBEvent>
</ArrayOfFBEvent>