- it needs it's 2A peak current recommend connecting power to a battery
- APN doens't really matter what you call it (at least Etisalat egypt)
- there is a 30char hard limit on token names
- Expected Hz is .5Hz
- i.e 30 logs is a minute of data
-
- We have 2 kinds of tokens
-
Client Tokens
- Set by "login" on the client
- Used for Push notifications and everything else client related by car_token agnostic
-
Car Tokens
- Preset in QR code on the Device it self
- Multiple Client tokens can be registered to the Same Car Token
-
- ALL Tokens are expected to look like ```xxxx-xxx-xxxx`` this is very critical for Car Tokens since the client expects this to be the case before sending them to the Server
- We have 2 kinds of tokens
- email is the email to register the token with
CAR_DATA_KEYS
is the JSON keys expected as the output of the API for for the getDataTOKEN_METADATA_KEYS
is the JSON keys expected outputs of the API for get_metadataNOTF_KEYS
is the JSON keys expected output of the API for get_notfsreal_hz
how often (in hertz) do we send the data to the server?min_of_speeding_to_alert
how many minutes should pass before warning the user to a speed_exceeding event?- see #17
server_uri="http://localhost:7060"
email="mohamed.emad4bubble@gmail.com"
CAR_DATA_KEYS=["car_token","lat","lot","speed","accuracy","Unixtimestamp"]
TOKEN_METADATA_KEYS=["car_token","client_token","max_spd"]
NOTF_KEYS=["client_token","title","msg"]
real_hz=.5
How many logs should pass before sending a warning notf?
self.MAX_THROT_ENTRIES=15 # 30 logs means a min of speeding