Although I tend to agree with the policy you mentioned:
Ask "What does this have to do with Arduino?" and if the answer to that question is not significant enough, then the question is probably off topic. httphttps://meta.arduino.meta.stackexchange.com/a/52/11
That policy is still quite subjective (how would you quantify "is not significant enough"?) and allows for different interpretations for a given question.
In the specific question aforementioned, I would keep it on-topic for the following reasons:
- some answers may be Arduino-specific (or in this case, RFDuino-specific), e.g. there could be some specific way to provide current to the board and keep low-power consumption
- the answer may require specific Arduino knowledge, as any datasheet only generally specifies min or max values; but nothing values real-life experience on the board to determine actual power needs
- people who can potentially answer this question (i.e. people who already used an RFDuino and have faced the same decision in the past) are more likely to be found on Arduino.SE than EE.SE; as a matter of fact, that's my personal situation, although I do have an account on EE.SE, I almost never go there.
Although I tend to agree with the policy you mentioned:
Ask "What does this have to do with Arduino?" and if the answer to that question is not significant enough, then the question is probably off topic. http://meta.arduino.stackexchange.com/a/52/11
That policy is still quite subjective (how would you quantify "is not significant enough"?) and allows for different interpretations for a given question.
In the specific question aforementioned, I would keep it on-topic for the following reasons:
- some answers may be Arduino-specific (or in this case, RFDuino-specific), e.g. there could be some specific way to provide current to the board and keep low-power consumption
- the answer may require specific Arduino knowledge, as any datasheet only generally specifies min or max values; but nothing values real-life experience on the board to determine actual power needs
- people who can potentially answer this question (i.e. people who already used an RFDuino and have faced the same decision in the past) are more likely to be found on Arduino.SE than EE.SE; as a matter of fact, that's my personal situation, although I do have an account on EE.SE, I almost never go there.
Although I tend to agree with the policy you mentioned:
Ask "What does this have to do with Arduino?" and if the answer to that question is not significant enough, then the question is probably off topic. https://arduino.meta.stackexchange.com/a/52/11
That policy is still quite subjective (how would you quantify "is not significant enough"?) and allows for different interpretations for a given question.
In the specific question aforementioned, I would keep it on-topic for the following reasons:
- some answers may be Arduino-specific (or in this case, RFDuino-specific), e.g. there could be some specific way to provide current to the board and keep low-power consumption
- the answer may require specific Arduino knowledge, as any datasheet only generally specifies min or max values; but nothing values real-life experience on the board to determine actual power needs
- people who can potentially answer this question (i.e. people who already used an RFDuino and have faced the same decision in the past) are more likely to be found on Arduino.SE than EE.SE; as a matter of fact, that's my personal situation, although I do have an account on EE.SE, I almost never go there.
Although I tend to agree with the policy you mentioned:
Ask "What does this have to do with Arduino?" and if the answer to that question is not significant enough, then the question is probably off topic. http://meta.arduino.stackexchange.com/a/52/11
That policy is still quite subjective (how would you quantify "is not significant enough"?) and allows for different interpretations for a given question.
In the specific question aforementioned, I would keep it on-topic for the following reasons:
- some answers may be Arduino-specific (or in this case, RFDuino-specific), e.g. there could be some specific way to provide current to the board and keep low-power consumption
- the answer may require specific Arduino knowledge, as any datasheet only generally specifies min or max values; but nothing values real-life experience on the board to determine actual power needs
- people who can potentially answer this question (i.e. people who already used an RFDuino and have faced the same decision in the past) are more likely to be found on Arduino.SE than EE.SE; as a matter of fact, that's my personal situation, although I do have an account on EE.SE, I almost never go there.