Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "always open" mode. #10

Open
grodansparadis opened this issue Apr 27, 2016 · 1 comment
Open

Add "always open" mode. #10

grodansparadis opened this issue Apr 27, 2016 · 1 comment
Assignees

Comments

@grodansparadis
Copy link
Owner

Scenario 2

  1. The test rig is powered on and the daemon and VSCP Works are started.
    
  2. Events (temperature measurements) are received in the VSCP Client window.
    
  3. The power from the Frankfurt module is powered off and 2 seconds later on.
    
  4. No temperature events are received. // I waited > 10 minutes
    
  5. VSCP Works is closed and the Daemon is restarted.
    
  6. The Daemon reports a driver failure for the Frankfurt module (see attached pic).
    
  7. The Frankfurt module is powered off and the daemon is closed.
    
  8. The Frankfurt module is powered on and the daemon is started. The driver is successfully loaded.
    
  9. VSCP Works is started and the temperature events are received in the client window.
    
  10. The scenario does NOT always happen when I cycle the power on the Frankfurt module.
@grodansparadis
Copy link
Owner Author

This will close the channel (it is opened when the driver is opened). A common problem with all CAN adapters also. It makes me think if if it wouldn't be a good thing to have a configurable always open mode for it. I will make a note for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant