{"id":1487,"date":"2017-12-06T22:31:03","date_gmt":"2017-12-06T22:31:03","guid":{"rendered":"http:\/\/wiki.intouchgps.info\/?page_id=1487"},"modified":"2019-02-28T10:48:01","modified_gmt":"2019-02-28T15:48:01","slug":"editing-a-driver-log","status":"publish","type":"page","link":"https:\/\/wiki.intouchgps.info\/index.php\/editing-a-driver-log\/","title":{"rendered":"Editing Driver Logs"},"content":{"rendered":"<p>Back to <a href=\"\/index.php\/eld-learning-center\/\"><strong>ELD Driver App<\/strong><\/a><\/p>\n<h3><strong>Editing Driver Logs<\/strong><\/h3>\n<div>\n<p align=\"left\">The <strong>Edit Log<\/strong> screen can update\/correct the driver\u2019s or driving duty data entries logged through the HOS app. It can also view the history of an edited log.<\/p>\n<ol>\n<li><strong>Daily Driver\u2019s Log Chart:<\/strong> Touch the driver\u2019s log chart to start editing it.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-402 size-full\" style=\"border: solid 1px black;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/logs1.jpg\" alt=\"\" width=\"500\" height=\"213\"><\/p>\n<ul>\n<li>You can navigate through the daily driver logs by selecting either the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-60\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/38.png\" alt=\"38\" width=\"43\" height=\"39\"> Previous Day or <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-61\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/39.png\" alt=\"39\" width=\"43\" height=\"39\"> Next Day Button.<\/li>\n<li>You can also view the cycle used and the Starting Hour of the day set by the carrier which is placed just above the grid chart<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<ul type=\"a\">\n<li style=\"list-style-type: none;\">\n<ul type=\"a\">\n<li>By default, secondary events are not displayed and only primary events can be viewed in the Event History List.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-702\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/08\/image00-min.png\" alt=\"image00-min\" width=\"350\" height=\"467\">You can show all events by tapping the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-614\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/06\/ShowAllEvents-min.png\" alt=\"ShowAllEvents-min\" width=\"155\" height=\"40\"> Show All Events option.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-703\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/08\/image12-min.png\" alt=\"image12-min\" width=\"350\" height=\"467\"><\/li>\n<li>You can add exceptions by tapping the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-508\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/add-exception-button.png\" alt=\"add exception button\" width=\"50\" height=\"39\"> <strong>Add Exception Button<\/strong>.<br \/>\nThe <strong>Exception Pop-up Dialog<\/strong> will then appear where you select as to which exception the driver will use.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1283\" style=\"border: solid 1px; border-width: 1px;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2017\/10\/US-Exceptions-1721.png\" width=\"350\" height=\"871\"><br \/>\nWhen adding an exception, the reference is displayed below the log grid and that it creates a remark event when an exception has been added. Also it creates another remark event when an exception is removed (or disabled).<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-704\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/08\/image14-min.png\" alt=\"image14-min\" width=\"350\" height=\"467\"><br \/>\n<strong>Note for the remark states:<\/strong> \u201cException added: \u201d example: \u201c<em>Exception added: 395.1(d)<\/em>\u201d and \u201cException removed: \u201d example: \u201c<em>Exception removed: 395.1(d)<\/em>\u201c<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul type=\"a\">\n<li style=\"list-style-type: none;\">\n<ul type=\"a\">\n<li>You can add new events by tapping the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-62\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/40.png\" alt=\"40\" width=\"34\" height=\"37\"> <strong>Add Events Button<\/strong>. The <strong>Create Event Pop-up Dialog<\/strong> will then appear where you can input the details of the new event.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1033\" style=\"border: solid 1px;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2017\/03\/dialog-CREATE-EVENT-1706.png\" width=\"350\" height=\"378\"><br \/>\n<strong>Notes:<\/strong><span style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"><br \/>\n<\/span><\/span><\/p>\n<ul>\n<li><span style=\"font-weight: 400;\">The current status of the app is disabled to prevent adding the same status consecutively.<\/span><\/li>\n<li><span style=\"font-weight: 400;\">The backward and forward time arrows are being disabled to prevent time from going before or after the current day. (eg. 12:00AM \u2013 11:59PM)<\/span><\/li>\n<\/ul>\n<\/li>\n<li>Select the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-64\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/42.png\" alt=\"42\" width=\"33\" height=\"41\"> <strong>Edit Log Button<\/strong> of the driver log event that you wish to edit.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-65\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/43.png\" alt=\"43\" width=\"485\" height=\"46\"><br \/>\n<strong>Note:<\/strong> <span style=\"font-weight: 400;\">The Edit Log Button will show <\/span><b>NOTE<\/b><span style=\"font-weight: 400;\"> instead of <\/span><b>Edit <\/b><span style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">because the driver will only be able to add a note to the following events:<br \/>\n<\/span><\/span><\/p>\n<ul>\n<li><span style=\"font-weight: 400;\">Intermediate log<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Login\/logout<\/span><\/li>\n<li><span style=\"font-weight: 400;\">CMV Engine power up\/shut down<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Malfunctions and diagnostic events<br \/>\n<\/span><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-795 size-full\" style=\"border: 1px solid;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/12\/image22-min.png\" width=\"516\" height=\"132\"><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">&nbsp;<\/span><\/li>\n<li>The <strong>Modify Event<\/strong> pop-up dialog will then appear.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1031\" style=\"border: solid 1px;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2017\/03\/dialog-EDIT-EVENT-1706.png\" width=\"350\" height=\"378\"><\/li>\n<li>You can update the duty status from the <strong>Status Drop-down List<\/strong>.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-364 size-full\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/status-2.jpg\" alt=\"\" width=\"500\" height=\"49\"><\/li>\n<li>You can also manually update the <strong>Location<\/strong> field.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-366 size-full\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/location.jpg\" alt=\"\" width=\"500\" height=\"51\"><\/li>\n<li>You may fill in the <strong>Note<\/strong> field for your notes or remarks.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-367 size-full\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/note.jpg\" alt=\"\" width=\"500\" height=\"76\"><br \/>\nIn creating or editing an event status, the ELD requires annotations to be 4 characters or longer, including embedded spaces if driver annotation is required and driver is prompted by the ELD. If the driver enters an annotation with less than 4 characters then a warning dialog will prompt the driver.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-511\" style=\"border: 1px solid;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/StaticShot_11-04-2016_12-31-02.png\" alt=\"StaticShot_11-04-2016_12-31-02\" width=\"354\" height=\"98\"><\/li>\n<li>Tap <strong>Reason<\/strong> dropdown selection to select a reason for updating the log.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-856\" style=\"border: solid 1px;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/12\/modify-event-reason-min-1.jpg\" width=\"500\" height=\"50\"><br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1032\" style=\"border: solid 1px;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2017\/03\/dialog-EDIT-EVENT-reason-1706.png\" width=\"350\" height=\"448\"><br \/>\n<strong>Note: <\/strong>Adding\/Editing a current\/previous record should not require a reason or a note, However, if a record is being added\/edited in the previous logs then the Note field should not be empty and must contain at least 4 characters.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul type=\"a\">\n<li>You may fill in the <strong>Odometer<\/strong> field for your odometer value.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-369 size-full\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/odometer.jpg\" alt=\"\" width=\"500\" height=\"55\"><\/li>\n<\/ul>\n<p><strong>Note: <\/strong>When the Odometer value was supplied for a previous driving status the value entered is carried over to the new driving status when making a status change. Hence, the Odometer value entered for the current day will set as the Begin Odometer value.<\/p>\n<ul type=\"a\">\n<li>Touch the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-107\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/53.png\" alt=\"53\" width=\"45\" height=\"33\"> <strong>OK Button<\/strong> to save the changes you made to the duty status event.<br \/>\nYou can select the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-108\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/54.png\" alt=\"54\" width=\"67\" height=\"34\"> <strong>Cancel Button<\/strong> to cancel the updates to the said duty status or<br \/>\nthe <img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-109\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/55.png\" alt=\"55\" width=\"65\" height=\"31\"> <strong>Delete Button<\/strong> to delete the said event.<\/li>\n<\/ul>\n<p><span style=\"color: #ff0000;\"><strong>Note: <\/strong>When the driver is in AOBRD mode then the edit \u201c*\u201d sign &amp; events will not be displayed in the <strong>Edit Logs<\/strong> screen and on the <strong>Certified PDF logs<\/strong>.<\/span><\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Created Events<\/strong><\/span><\/p>\n<p>Upon logging in and logging out of the HOS app, <span style=\"font-weight: 400;\">as well as connecting and disconnecting to a VBUS Device, new event types will display on the Event History List.<\/span> The New Event Types are as follows:<\/p>\n<ul>\n<li>Certify<\/li>\n<li>Remark \u2013 with a note of \u201cAuthenticate\u201d (if logging in) or \u201cUnauthenticate\u201d (if logging out)<\/li>\n<li>ELD Login \u2013 event that will be recorded when app is connected to VBUS Device<\/li>\n<li>ELD Logout \u2013 event that will be recorded when app is disconnected to VBUS Device<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-774\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/11\/image10.png\" width=\"600\" height=\"450\"><\/p>\n<p><strong>Note: <\/strong><span style=\"font-weight: 400;\">Auto events created are recorded in the app with a note stating: \u201c<\/span><b>Automatic Transition<\/b><span style=\"font-weight: 400;\">\u201d<\/span><\/p>\n<ul>\n<li><strong><span style=\"color: #ff0000;\">Personal Use<\/span> <\/strong>\u2013 If this is enabled, the status will be set to Off Duty automatically and will disable the Yard Moves checkbox. Selection of this option will be recorded within the events history list.<\/li>\n<li><strong>Yard Moves<\/strong> \u2013 If this is enabled, the status will be set to On Duty automatically and will disable the Personal Conveyance checkbox. Selection of this option will be recorded within the events history list.<\/li>\n<\/ul>\n<p><strong>Note: <\/strong><span style=\"color: #ff0000;\">Not all of the events statuses are displayed on the grid chart. <em><strong>Personal Use<\/strong><\/em> and <em><strong>Yard Moves<\/strong><\/em> are also displayed on the grid chart as an<strong> Amber<\/strong> color line to be visually different with the other event statuses, <strong>a dashed line<\/strong> represents the <em><strong>Personal Use<\/strong><\/em> event and <strong>a dotted line<\/strong> represents the<em><strong> Yard Moves<\/strong><\/em> event.<\/span> <span style=\"color: #ff0000;\">The legends for <strong><em>Personal Use<\/em><\/strong> and <em><strong>Yard Moves<\/strong><\/em> event will only display when the said events occurred.<\/span> <span style=\"font-weight: 400;\">A driver\u2019s indication that the CMV is being operated for authorized personal purposes may span more than one CMV ignition on cycle if the driver proactively confirms continuation of the personal use condition prior to placing the vehicle in motion when the ELD prompts the driver at the beginning of the new ignition power on cycle. <span style=\"color: #ff0000;\">In addition, upon disabling the events \u201c<em><strong>Personal Use<\/strong><\/em>\u201d or \u201c<em><strong>Yard Moves<\/strong><\/em>\u201c, it records a new event on the list stating \u201c<strong>ClearPU<\/strong> or <strong>ClearYM<\/strong>\u201d which indicates the clearing of the option for <strong>Personal Use<\/strong> and <strong>Yard Moves<\/strong>. Thus, it will not reflect on the grid chart.<\/span><\/span><br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-700\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/08\/image05-min.jpg\" alt=\"image05-min\" width=\"500\" height=\"227\"><br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1084\" style=\"border: solid 1px;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2017\/05\/Screenshot_20170523-120100.png\" width=\"400\" height=\"533\"><br \/>\n<strong>Note:<\/strong> When a co-driver is log into the HOS app, the co-drivers name is displayed on the daily logs which is placed right below the grid chart. <span style=\"text-decoration: underline;\"><br \/>\n<\/span><\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Re-assigning driving time to a co-driver<\/strong><\/span><br \/>\nThe Primary driver is allowed to re-assign his driving status\/time to his co-driver (if the co-driver logs in).<\/p>\n<ul>\n<li>Tap the Edit icon on the edit logs screen to re-assign the status<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-507\" style=\"border: 1px solid;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2015\/08\/StaticShot_11-04-2016_11-56-49.png\" alt=\"StaticShot_11-04-2016_11-56-49\" width=\"298\" height=\"217\"><\/li>\n<li>You will need to login the Co-Driver to make it active.<\/li>\n<li>You can also check on the event history list of the co-driver to confirm that the status is re-assign.<\/li>\n<li>When back to main driver, check also the event history list of the main driver to confirm that the driving status is no longer there.<strong>Note:<\/strong> Only driving events that are created automatically can be reassigned, non-driving events such as Login or Power On can only be annotated.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-682\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/06\/Annotate-Login-min.png\" width=\"400\" height=\"162\"><\/li>\n<\/ul>\n<p><span style=\"text-decoration: underline;\"><strong>Crossing Boundaries<\/strong><\/span><br \/>\nThe border crossing calculation uses the vbus gps coordinates if they are available, and the android coordinates if they are not. The following instances happens when the driver crossed boundaries between Canada and US (vice versa):<\/p>\n<ol style=\"list-style-type: lower-alpha;\">\n<li><span style=\"font-weight: 400;\">If the gps coordinates are changed to a different state or province, a remark event will be recorded in the driver log.<\/span><br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-738\" style=\"border: 1px solid;\" src=\"http:\/\/developer.vistracks.com\/hos\/wp-content\/uploads\/2016\/09\/CrossingBoundaries-min.png\" width=\"400\" height=\"309\"><\/li>\n<li><span style=\"font-weight: 400;\">If the current location is in canada, the driving rules will automatically switched to canadian rules; similarly, if the location is in the US, the driving rules automatically switched to US rules.<\/span><\/li>\n<li><span style=\"font-weight: 400;\">If there is a co-driver logged in, both the remark and the rules changes will be occurring for them as well.<\/span><br \/>\n<strong><br \/>\nNote:<\/strong> <span style=\"font-weight: 400;\">These remark events will be reflected in the portal\u2019s Logs Tab<\/span><\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Back to ELD Driver App Editing Driver Logs The Edit Log screen can update\/correct the driver\u2019s or driving duty data entries logged through the HOS app. It can also view the history of an edited log. Daily Driver\u2019s Log Chart: Touch the driver\u2019s log chart to start editing it. You can navigate through the daily &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/wiki.intouchgps.info\/index.php\/editing-a-driver-log\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Editing Driver Logs&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1487","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/pages\/1487","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/comments?post=1487"}],"version-history":[{"count":7,"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/pages\/1487\/revisions"}],"predecessor-version":[{"id":2814,"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/pages\/1487\/revisions\/2814"}],"wp:attachment":[{"href":"https:\/\/wiki.intouchgps.info\/index.php\/wp-json\/wp\/v2\/media?parent=1487"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}