raphaelmanke / fzi-iota-showcase Goto Github PK

• vehicle channel
  • seed
  • channelId
  • trip-channels
    • seeds
    • channelIds
    • welcome-message
    • goodbye-message
    • reservation-channels
      • seed
      • root
      • message-format

• images can be pushed
• images can be downloaded

• grid
• vehicles
  • position
  • state (parking, waiting for payment, reserved, driving, etc.)
• users
  • position
  • state (waiting, issueing transaction, driving)
• payment-channels
  • user
  • vehicle
  • state (pending, open, closed)
  • micro-transactions
• transactions

• define stop model
• define road connection model

• messages
• states
• events

• checkout code
• test each component
• build each component
• create working docker image for vue apps and backend component
• push image to docker registry

Defining all events necessary to determine the visualizations capabilities.

• Add events to simple.ts for testing

• setup webserver
• define http GET endpoint sending stops and roadconnections

implement an http-endpoint returning available routes given start and destination stop and allowed vehicle types.

• filter connections that have allowed vehicle type
• add used connection to route result
• filter connections where a vehicle is available
• map available vehicles to used connections in route result
• calculate all routes using different combinations of available vehicles
• add http-endpoint that returns routes using current available vehicles

After issuing a stopTripAtNextStop the vehicle stops at the wanted stop, but the tripFinished Events still contains the old destination in the payload.

• create docker-compose.yml
• pull image
• deploy to stage

goal: use on seed to create/read/write all MAM/RAAM channels of a vehicle