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

ForceSample() does not cause SampleReceived event to fire #46

Open
PaulHeitkemper opened this issue Mar 5, 2018 · 6 comments
Open

ForceSample() does not cause SampleReceived event to fire #46

PaulHeitkemper opened this issue Mar 5, 2018 · 6 comments
Assignees

Comments

@PaulHeitkemper
Copy link

PaulHeitkemper commented Mar 5, 2018

Is there a way to get the state of the digital input pins on startup? I tried manually setting IR to 1, to 100, changing the value of IC, but nothing works. node.ForceSamples() does not seem to have any effect.

What should I set up for periodic sampling? Sorry, I guess this inadvertently became two questions.

@jefffhaynes
Copy link
Owner

ForceSampleAsync should fire the SampleReceived event and you can use SetSampleRateAsync to set the sample rate. I can't think offhand of any way to synchronously read the pin values.

@PaulHeitkemper
Copy link
Author

PaulHeitkemper commented Mar 7, 2018 via email

@jefffhaynes
Copy link
Owner

jefffhaynes commented Mar 7, 2018 via email

@PaulHeitkemper PaulHeitkemper changed the title How to determine initial Input state? ForceSamples() does not cause samples received event to fire Mar 21, 2018
@PaulHeitkemper
Copy link
Author

Title changed to better reflect problem description.

@jefffhaynes jefffhaynes self-assigned this Mar 24, 2018
@jefffhaynes
Copy link
Owner

jefffhaynes commented Mar 31, 2018

Do you know if you were trying this with an end device or a coordinator? I have a S2C here that I can't get to send a sample locally, even with the X-CTU...

@PaulHeitkemper
Copy link
Author

The local device was a XBee PRO 900HP 200K set as Standard Router (CE=0). The remote device I was trying to send the ForceSample() command to was the same type device set as Non-Routing Module (CE=2)

@PaulHeitkemper PaulHeitkemper changed the title ForceSamples() does not cause samples received event to fire ForceSample() does not cause samples received event to fire Apr 2, 2018
@PaulHeitkemper PaulHeitkemper changed the title ForceSample() does not cause samples received event to fire ForceSample() does not cause sample received event to fire Apr 2, 2018
@PaulHeitkemper PaulHeitkemper changed the title ForceSample() does not cause sample received event to fire ForceSample() does not cause SampleReceived event to fire Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants