mwcaisse / car-tracker-server Goto Github PK

Executing job throw an Exception Error running 01 0D, response: 410D38<RXERROR com.github.pires.obd.exceptions.UnknownErrorException: Error running 01 0D, response: 410D38<RXERROR at java.lang.Class.newInstance(Native Method) at com.github.pires.obd.commands.ObdCommand.checkForErrors(ObdCommand.java:203) at com.github.pires.obd.commands.ObdCommand.readResult(ObdCommand.java:123) at com.github.pires.obd.commands.ObdCommand.run(ObdCommand.java:77) at com.ricex.cartracker.android.obd.ObdCommandExecutor.runOBDCommandNoCheck(ObdCommandExecutor.java:113) at com.ricex.cartracker.android.obd.ObdCommandExecutor.runOBDCommand(ObdCommandExecutor.java:107) at com.ricex.cartracker.android.service.reader.BluetoothOBDReader.executeOBDJob(BluetoothOBDReader.java:201) at com.ricex.cartracker.android.service.reader.BluetoothOBDReader.read(BluetoothOBDReader.java:77) at com.ricex.cartracker.android.service.task.OBDServiceTask.performLoopLogic(OBDServiceTask.java:97) at com.ricex.cartracker.android.service.task.ServiceTask.run(ServiceTask.java:36) at java.lang.Thread.run(Thread.java:761)

Trip processor shouldn't pull the trip from the current request when processing a trip. It should pull the user id from the owner of the car.

Allow users to track maintenance performed against their car.

Car Maintenance types include

• Oil Change
• Tire Rotation
• Air Filter Change
• Cabin Air Filter change

Along with the maintenance type capture the following:

• Date
• Mileage. Pre-populate this with the car's current mileage, allow the user to modify if incorrect

Implement Authentication.

Add a forms based login for the UI
Add a token and header based login for API calls.

Implement https://github.com/ektrah/nsec once it is released.

Controllers should return a HTTP415 if request body was in an unexpected format. Not just parse it and return null to the controller/service.

Logger (IServerLogger) does not seem to work in the context of a Job.

Throws error "there is already an open datareader associated with this connection"

Create UI pages to view the request logs and to view the server logs.

Request Log

• Grid containing the following columns
  -- Type, Request Method, Request Url, Response Status, User, Request Date
• Popup modal that shows more detailed information
  -- Request Body / Response Body
  -- Request Headers / Response Headers
  -- Grid of Server Logs that correspond to the given request

Server Log

• Grid containing the following columns
  -- Request Uuid, Type, Message, Create Date

Update the footer to not be sticky.

The request is not authenticated when the class is instantiated, resulting in IsAuthenticatedalways being false.

Trip page should only fetch trips once, not 5 times

Add logging to the server. Log all requests.

On the login page, if user doesn't enter a username/password the form still posts, but the endpoint isn't found (likely because no parameters) and user sees a blank page with status of 404

Add ability to add a destination / starting place when viewing a trip

Trip Possible places creates duplicated entries when re-run. Should have it clear out the old entries if trip is reprocessed.

Automatically process finished trips.

Implement a queing/job service to implement trips independent of a web request.

Investigate best way to implemented Webpack. Then implement it.

If the GPS coords at start is vastly different than following readings... GPS snaps from one location to another at the beginning, don't use the first readings GPS coords as trip start.

Add navigational bread crumbs to page to allow user to more easily navigate back and forth between pages in the application.

Automatically select the start / destination place based on previous choices.

Use history of start / destination places for a the GPS ending point of a trip to guess the correct start / destination.

• Keep a mapping of GPS coordinates and chosen places for those coordinates and a count of times chosen
• This could possibly be calculated on the fly, rather than updating everytime. Explore which is better option.
• Allow the user to correct the the automatically chosen place and update the mapping
• Using approximate coordinates, chose the place that has chosen the most

The mapping will need to be introduced first to train the selection.

Combine the UI and API projects into one project. Nothing is being gained by having them as separate projects. Combining them together removes the issue of how to handle authentication between both applications.

re-processing a trip increments car mileage each time.

If the trip was already processed, should subtract the trip's mileage from the car before updating. Or only change it by the delta between processings.

Update the selection of the Start/Destination place on a Trip to be a modal.

It will show the list of possible places and allow the user to select one.

Remove the start/destination panels from the main trip page.

Trip Destination name is not displaying on Trip Grid

Create a bulk attribute that allows bulk requests to an API endpoint without modifying the endpoints code.

Create a theme/style to use for the UI.

Something to make the site look not like a basic bootstrap site and add some color/styyyyyyyyyyyyyyyyyyyyle.

Create a script to backfill the TripId in PlaceVisit based off the Latitude/Longitude and Visit Date. Compared to Latitude/Longitude on the last reading for the trip and the End Date of the trip or date of the last reading (whichever the code uses to PlaceVisit)

Add a method for adding page alerts / displaying error messages to users.

Remove the use of window.alert for displaying error messages when API calls fail.

Heat map of trips for last day, week, month, timeframe, etc

Determine a way to handle the Enum/Database conversion

• Convert the current string based values in database to integer
• Perform string to enum conversion in application
• Other options?

Converting in the database loses database readability. Converting in the application performs the string conversion on every read.

Add a start/end date filter on reader logs.

Car Supported Command results are different in Java and .NET implementations.

Likely just a mis-mapping of Commands to PIDS.

There are a few typos / spelling issues on Command Names.

Add swagger or similar for API documentation

Start/Destination places aren't set on automatically processed trips

Show the relevant reader logs on the trip page for that trip.

Reader Logs from between start/end date of that trip.

Add information of the currently logged in user to the Request Logging