The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
Moderator note
This topic has been split off and closed. If both Fabien and Arron would like the thread removed, a moderator will comply with the request.
Original post
Fabien,
I'm not really sure $75 for a any number of small sensors is even remotely reasonable. I think individual $10-15 sensors are going to be better options for most users, both on price an ease of use. The IDC cable provides a much better user experience than just wires, after all I could do that with a breadboard for much cheaper.
Edited by Chris Walker, 01 October 2012 - 03:39 AM. added moderator note
I'm not really sure $75 for a any number of small sensors is even remotely reasonable. I think individual $10-15 sensors are going to be better options for most users, both on price an ease of use. The IDC cable provides a much better user experience than just wires, after all I could do that with a breadboard for much cheaper.
I understand that you're still bitter about my questioning the value of your ProtoModule many months ago, that you took it personally and resent me for it, and that since then, you have taken great care of discrediting my contributions to the community any occasion you get. I know what to expect from you and that's ok.
However, if you had done the cost analysis instead of spreading misinformation, you'd know that:
Selling the seven features offered by the DAQ as individual modules would cost well over $75
I2C sensors, without the overhead of the supporting Go hardware, can cost anywhere between $10 to $20 by themselves depending on brand / function
IDC cables cost at least $2 each
Now, show me an alternative to the DAQ that allows connecting *any* kind of I2C sensors to a Netduino Go!
I understand that you're still bitter about my questioning the value of your ProtoModule many months ago, that you took it personally and resent me for it, and that since then, you have taken great care of discrediting my contributions to the community any occasion you get. I know what to expect from you and that's ok.
Fabien, if any of that were true, I wouldn't send people to your shop at Nwazet, something which I do fairly regularly.
However, if you had done the cost analysis instead of spreading misinformation, you'd know that:<br style="color: rgb(28, 40, 55); font-size: 13px; line-height: 19px; background-color: rgb(250, 251, 252); ">
Selling the seven features offered by the DAQ as individual modules would cost well over $75
I2C sensors, without the overhead of the supporting Go hardware, can cost anywhere between $10 to $20 by themselves depending on brand / function
IDC cables cost at least $2 each
Granted (maybe), but you still missed my point about ease of use. The DAQ has it's place, I see it as being more applicable to prototyping and industrial applications, as you do.
... .Net Micro Framework in the context of rapid system prototyping, light industrial control systems ...
<br style="background-color: rgb(250, 251, 252); ">Now, show me an alternative to the DAQ that allows connecting *any* kind of I2C sensors to a Netduino Go!
Fabien, generally I'd offer this advice privately, but you've made that harder and you've already aired this in public. When you represent your company posting stuff like this in full view of 100% of your target market is a bad idea. You make yourself look bad and by extension your company. Was I out of line posting my response to your DAQ advertisement; Yes. Were you out of line in hijacking the thread with your DAQ ad; Yes. Lets take this opportunity to step back and review what we've posted (here and elsewhere), lets both rethink some of it, learn from all of it and MOVE ON.
I've yet to lobby a single personal attack at you, and I'm not going to start now. I will ask that keep things respectful both here and elsewhere I know you have complaints about how certain things are going, or have gone, but the forums are not the place to air them. I also don't have any problem with you promoting your newest module, the DAQ, but there comes a point when you go from promoting it to spamming please keep that in mind.
If you'd like to continue this conversation in part or in whole or start a new one you know how to find me but just in the case that any of my information was lost here you go.
Skype: unkwntech
Phone: 858-598-3814
Email: arron@arronchapman.com
Fabien, while I personally disagree with you on many things, I do recognize the value you can add to the community.
I also don't have any problem with you promoting your newest module, the DAQ, but there comes a point when you go from promoting it to spamming please keep that in mind
I very much appreciate the work that Mark put into his prototype temp / humidity sensor module and the video he made showing it. You certainly don't attack him for "spamming' and hijacking" your thread. But when I post something related to sensing temperature and humidity, I'm a thread spammer and a hijacker?
Fabien Royer, on 30 September 2012 - 02:22 PM, said:
<br style="background-color: rgb(250, 251, 252); ">Now, show me an alternative to the DAQ that allows connecting *any* kind of I2C sensors to a Netduino Go! <br style="color: rgb(28, 40, 55); font-size: 12.727272033691406px; line-height: 19.09090805053711px; background-color: rgb(250, 251, 252); ">Done
Once again, this is misinformation: the Shield Base doesn't have I2C implemented even though the hardware exposes the SDA and SCL pins.
I've yet to lobby a single personal attack at you, and I'm not going to start now. I will ask that keep things respectful both here and elsewhere I know you have complaints about how certain things are going, or have gone, but the forums are not the place to air them.
You can't be serious. What was that Twitter post if not a personal, public attack?
You certainly don't attack him for "spamming' and hijacking" your thread. But when I post something related to sensing temperature and humidity, I'm a thread spammer and a hijacker?
We've run into some issues with some of the senors we've evaluated and would like to get a better feel for what the community would like to see from a Temperature Sensor Module.
The "we" in that post included Mark, and his work here is a direct result of us working together to get this modules out the door.
I very much appreciate the work that Mark put into his prototype temp / humidity sensor module and the video he made showing it.
It pleases me greatly to see you posting positive messages, as I said in the Twitter bit you screenshotted, I would have much rather to have seen this in your inital post, but better late then never as they say.
Once again, this is misinformation: the Shield Base doesn't have I2C implemented even though the hardware exposes the SDA and SCL pins.
That is correct to the extent that it isn't implemented today, however progress is being made to that goal. The first step was Go!Bus 1.5, next up is implementing the remaining protocols, which we are already seeing. I think you know as well as I do that this is a long process that is hard and will take some time to get done, more so when other projects (necessarily) are going on in parallel. Since you've implemented I2C via some sort of proxy (I don't know how this works since I don't have a DAQ, and won't cause I cant afford it) I hope that you'll give guidance to Chris and Secret Labs so as to help them make quick work of finishing the ShieldBase. Something which would greatly benefit the entire community. And would gain you a significant amount of respect from people like me, who have uses for the ShieldBase that the DAQ is unable to fulfill.
You can't be serious. What was that Twitter post if not a personal, public attack?
As I said in the twitter message Fabien, it was honest. An advertisement for the DAQ isn't *needed* everywhere that it *could* be used. Again, I understand the need to market it, and the desire to make sure people know about it. While I don't have numbers to back this up, it feels like most of your recent posts have been about the DAQ, which is great, but I think that overall you'll sell more by showing us that you know how to build products, and that you are a good guy (good will can get you far in business).
My style is clearly different from yours, but my method to sell modules is simple;
Build good modules, and do everything I can to help the community grow. I accomplish the latter part primarily by helping users, via posting in threads, and never seeming to leave chat. Given the sales of the ProtoModule and the current target audience for it, this method is working well and I'm pleased with the results so far. A bit later this year I'm doing some updates (software) to the ProtoModule which I expect to widen the target audience for the ProtoModule, and we'll see then if my methodology works for people who don't want to build modules.
Since you've implemented I2C via some sort of proxy (I don't know how this works since I don't have a DAQ, and won't cause I cant afford it) I hope that you'll give guidance to Chris and Secret Labs so as to help them make quick work of finishing the ShieldBase. Something which would greatly benefit the entire community. And would gain you a significant amount of respect from people like me, who have uses for the ShieldBase that the DAQ is unable to fulfill.
The DAQ schematics and the source are open for anyone to review and re-use provided that attribution is given: https://bitbucket.or...r/nwazet.go/src
What more do you need? How is this not of benefit to the community?
And would gain you a significant amount of respect from people like me, who have uses for the ShieldBase that the DAQ is unable to fulfill.
Like what?
I think that overall you'll sell more by showing us that you know how to build products
You're joking right? Do I need to provide links to the Go! modules that we have designed and shared with the community or would that be considered too much spam?
it feels like most of your recent posts have been about the DAQ, which is great, but I think that overall you'll sell more by showing us that you know how to build products, and that you are a good guy (good will can get you far in business).
I'm the 'bad guy' now? WTF is that even supposed to mean?
Build good modules and do everything I can to help the community grow. I accomplish the latter part primarily by helping users, via posting in threads, and never seeming to leave chat.
That's exactly what Nwazet does and we share everything that we produce with the community. We're trying to make an honest living from our work. What more do you want from us?
The DAQ schematics and the source are open for anyone to review and re-use provided that attribution is given: https://bitbucket.or...r/nwazet.go/src
What more do you need? How is this not of benefit to the community?
I never said it didn't and I don't mean to diminish the value that you've provided.
Like what?
The ability to use all of the shields we already have, for example.
I'm the 'bad guy' now? WTF is that even supposed to mean?
I didn't say that. I say what I mean, don't imply further meaning from it.
Fabien, this is the last I will have of this conversation here, it simply doesn't belong here. If you want to continue it please take it elsewhere. Continuing here does NO ONE any good.
Moderator note
This type of conversation is probably best carried on offline. We want the forums to be a family-friendly place free of bad feelings or conversations of such a personal nature.
I have split this thread and am going to close it, at least for a while. I'm not big on censorship, but sometimes it's good to let feelings cool.
I really appreciate all the effort that both of you puts into your projects, products, and the community. Your words evoke that passion. Let's see what we can all build together.
Chris
P.S. This topic has been split off and closed. If both Fabien and Arron would like the thread removed, a moderator will comply with the request.
This topic is locked
