Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S Solaar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pwr-Solaar
  • Solaar
  • Issues
  • #21
Closed
Open
Issue created Apr 27, 2013 by Administrator@rootContributor

Concurrent device access causes interference between programs

Created by: Lekensteyn

When I tried to run scan-registers.sh while solar was running, it tagges wrong messages as a response to another (solar periodically reads the battery register 07).

Part of the solution:

  • Use the following hints to match responses and requests:
    • the device index, type and register.
    • in case type=ERROR_MSG (8F), compare the device index and the Sub ID plus register of the error message to the request.
  • Let messages be asynchronous (in a dedicated I/O thread?), on submission it will be queued. A queue item could have the attributes time of submission (for expirity), a callback function and the actual message.
Assignee
Assign to
Time tracking