16 replies to this topic

[Antti Lukats]

Hi I did read somewhere on netduino website that GO! firmware and SDK sources will be available on 8th April today is 9th April but I am failing to see the download information, same goes was nWazet website, they also promised 8th April but are also not providing any links or further information. Maybe I just can not find where the downloads are, or is the deadline moved? If so on what DATE can we expect the downloads to be available? Antti

[Nevyn]

I did read somewhere on netduino website that GO! firmware and SDK sources will be available on 8th April
today is 9th April but I am failing to see the download information, same goes was nWazet website, they
also promised 8th April but are also not providing any links or further information.

Antti,

The date published on the Netduino site is incorrect. I asked about this earlier today and I was informed that the sources will be available on 9th April (New York time).

Regards,
Mark

[Chris Walker]

Hi Antti, We're packaging all the files for upload. If you need anything before this evening, just PM me and I'll be happy to send it your way. Chris

[Fabien Royer]

Hi

I did read somewhere on netduino website that GO! firmware and SDK sources will be available on 8th April
today is 9th April but I am failing to see the download information, same goes was nWazet website, they
also promised 8th April but are also not providing any links or further information.

Maybe I just can not find where the downloads are, or is the deadline moved?
If so on what DATE can we expect the downloads to be available?

Antti

Hi there,

All the [nwazet source code and designs have been published on BitBucket on 04/07/2012: https://bitbucket.or...r/nwazet.go/src
We published this fact in this Netduino GO! forum and announced it on Twitter. For what it's worth, [nwazet has nothing to do with the creation of the Netduino GO! SDK.

Cheers,
-Fabien.

[Antti Lukats]

Hi there,

All the [nwazet source code and designs have been published on BitBucket on 04/07/2012: https://bitbucket.or...r/nwazet.go/src
We published this fact in this Netduino GO! forum and announced it on Twitter. For what it's worth, [nwazet has nothing to do with the creation of the Netduino GO! SDK.

Cheers,
-Fabien.

Fabien,
relax!

But the fact remains: nwazet is selling OPEN SOURCE hardware labelled modules without providing the information how to rebuild them, at least some vital parts of the needed information is missing, not yet available. If you put open source hardware logo on your products you must know what it means for the product: ALL MANUFACTURING INFO must be be available and public. For your button module, where is C source? I have not found it.

as of SDK, yes, your website only says IT WILL BE AVAILABLE on 8th, but as today is not 8th but 10th it is wise to update the "8th april" to SOMEDAY in the future

ah, its only because I really do not like to WAIT, I assume all the required docs and sources will be made available one day, I just assumed it would have been day before yesterday, eg 8th of April as was initially promised.

Antti

[Fabien Royer]

But the fact remains: nwazet is selling OPEN SOURCE hardware labelled modules without providing the information how to rebuild them, at least some vital parts of the needed information is missing, not yet available.

Please be specific about what you believe is missing.

Did you actually take the time to explore the repository?

ALL MANUFACTURING INFO must be be available and public.

We are sharing our schematics, BOMs, source code. What else would you need?

For your button module, where is C source? I have not found it.

The Netduino Go! button is made by Secret Labs. Not us. In addition, there's no C code used for that module: it's managed through the Go!Bus GPIO pin using an InterruptPort.

as of SDK, yes, your website only says IT WILL BE AVAILABLE on 8th, but as today is not 8th but 10th it is wise to update the "8th april" to SOMEDAY in the future

Chris Walker of Secret Labs owns the Netduino SDK and drives the schedule for its release. We, my partner and I @ [nwazet, have no control over it.

I really do not like to WAIT

Neither do I

Cheers,
-Fabien.

[Fabian Nunez]

@Antti Dude, relax. Schedules slip all the time, and it's only been a couple of days. It's aggressive attitudes like yours that push companies away from open source. These guys could have made the Go bus proprietary, patented the bus protocol and implemented everything as a closed source set of libraries running on top of .net micro - it's allowed by the license. They chose to open source everything. Cut them some slack.

[Antti Lukats]

@Antti

Dude, relax. Schedules slip all the time, and it's only been a couple of days. It's aggressive attitudes like yours that push companies away from open source. These guys could have made the Go bus proprietary, patented the bus protocol and implemented everything as a closed source set of libraries running on top of .net micro - it's allowed by the license. They chose to open source everything. Cut them some slack.

Well yes. But its just that if you say 8th April, then you either do it on 8th, or say, its slipped, and scheduled for
say 11th April. And all questions answered.

I am not agressive, I am just wondering how hard it can be to say: well not 8th April, but say 15th is scheduled date.
We all do understand schedules slipping.

To Nwazet: yes I did explore the repository. On nwazet button board is microcontroller, right, so where is manufacturing info for this mcu? I did not find it.

Antti
sorry for being so much with Questions, I just really do not like waiting.. sometimes its worth of course.

[CW2]

On nwazet button board is microcontroller, right, so where is manufacturing info for this mcu?

Please note the button module is made by Secret Labs, [nwazet is a reseller (and maker of their own display, relay modules). The button module does not contain a microcontroller, but MC74HC589A shift register (pdf) that provides the module identifier. There is STM003F3 microcontroller on Secret Lab's RGB LED and Potentiometer modules.

[Stefan]

Hi

Well yes. But its just that if you say 8th April, then you either do it on 8th, or say, its slipped, and scheduled for
say 11th April. And all questions answered.

Currently we (Secret Labs and friends) are working hard on getting everything done. Since it's mostly done by volunteers, it's difficult to name an exact date, so lets say it will be here as soon as possible

To Nwazet: yes I did explore the repository. On nwazet button board is microcontroller, right, so where is manufacturing info for this mcu? I did not find it.

I'll help you look. According to the BOM.xlsx (bill of materials) which is in Nwazets repository, a STM32F205RET6 (LQFP64) is used. All documentation about that chip can be found here.

sorry for being so much with Questions, I just really do not like waiting.. sometimes its worth of course.

Questions are no problem, just remember to keep things friendly and you'll see you get your questions answerred
I must say the tone of your first message -looked- a bit aggressive. I'm glad you didn't ment it like that. Could be lost in translation of course!

Anyways, welcome to the Netduino community!

[Antti Lukats]

Hi


Currently we (Secret Labs and friends) are working hard on getting everything done. Since it's mostly done by volunteers, it's difficult to name an exact date, so lets say it will be here as soon as possible

I'll help you look. According to the BOM.xlsx (bill of materials) which is in Nwazets repository, a STM32F205RET6 (LQFP64) is used. All documentation about that chip can be found here.

Questions are no problem, just remember to keep things friendly and you'll see you get your questions answerred
I must say the tone of your first message -looked- a bit aggressive. I'm glad you didn't ment it like that. Could be lost in translation of course!

Anyways, welcome to the Netduino community!

Well maybe I am upset that I can help. If I do not see the code, there is not much I can do

I am not native english speaker and I did not go to KINDERGARTEN, and well it shows. Sorry.

Antti

[ErikN]

Hey everyone - I want to say I spoke to Antti directly and worked out the language difference. I can say with absolute confidence the initial communication was just a misunderstanding but there was some escalation after that point with the frustration. From Antti's point of view there was some sense of being attacked where I can see the remaining members were probably being defensive to what they sensed was an antagonistic contact. Please take my word that this was just a misunderstanding. Antti's use of the English language seems so complete it's easy to overlook that he's not a native speaker and is from a different cultural background. The way the language is learned varies greatly around the world and leads to misunderstandings like this when people don't realize they're speaking with someone with such a different background. I hope everyone involved can stop and reset their perception of each other from this first impression! Antti: While I do not speak for Secret Labs or the talented people involved in the Netduino Go project, I can say with confidence the source will be forthcoming. It's important to understand the resources involved in this project are quite small given the scope. Due to this a lot of things slipped through the cracks. I can say I'm never as good with documentation as I am with getting to the 90% point of a project. This is not an excuse. The open source hardware, in fact open source in general, has a difficult time with the last details of a project. Please don't think this means something strange is going on. Secret Labs has committed quite deeply to the open source hardware and software communities. From what I can tell, without passionate people external to Secret Labs, the Netduino Go would not be where it is today. Because of this immense accomplishment, despite the remaining community member's desire to have the SDK completely finished and released, we are very tolerant. This is a brand new product. This is a new league of device. It will take some time for everything to come together. Please also keep in mind the Netduino Go is not even finished being made yet! The same limited resources that rushed to get this amazing hardware to us are still working on refining the SDK to get the most stable and best performing firmware and libraries out to those of us on the bleeding edge who wanted to get our hands on this project early. They are still working on stabilizing the Shield Base module and preparing the switch over to faster bus access for it. They are working with a small group of extremely dedicated and passionate people who want to start creating go!bus compatible modules right now. It's important they pursue these goals now while the community is at the height of their excitement or they might lose the momentum and struggle later to get people interested again. This is important to us in the community because we need those passionate people to struggle through the rough ground and cut a path for us! We need them to shake out the problems and establish a common, workable way of creating modules. In short, please allow for some delinquency in the schedule. It was very ambitious of them and things slid. Updating a web page to reflect this was clearly an oversight. As Secret Labs people can't possibly monitor the forum so frequently to see that this is an issue and correct it immediately, it will take a little time for this to shake out. If it is acceptable, please just consider the date "pending" but know that it will be as soon as is responsible. In my time here I have grown to understand Secret Labs to be full of wonderful, passionate and very smart people who will help in any way possible. They are committed to delivering high quality boards. If you look at the schematics and see how well the boards are engineered with respect to signal and input tolerances, the components chosen for the manufacture, and with the Netduino Go the commitment to using easily recycled parts to lessen their environmental impact, I hope you will come to see them as I do: a truly great, caring company. My best, -Erik

[Antti Lukats]

Quick updates:

Full source code to the Netduino Go and Shield Base firmware is now posted on the Downloads page.

This code was contributed by community member KodeDaemon, who spent many months of free time and weekends on it. [Thanks Kode!]

We've signed the official .NET MF 4.2 drivers and are now in the process of building and testing the installer. All of the files you need to get up and running with Netduino Go are in the "Early software and instructions thread" pinned in this forum...but we will also have a nice SDK with templates for Netduino Go and official signed .NET MF 4.2 drivers shortly.

The design files for the modules are on the main website and Wiki. If there's any source I've missed, please let me know and I'll get it posted!

Thank you everyone for your patience these last few days while we have been getting everything uploaded. And please let us know how you are liking your new hardware!

Thank you,

Chris

Super!
just a stupid question maybe, why are you not using codeplex anymore for source hosting?
just curious. must be a valid reason?

Antti

PS sorry I must be blind or stupid, on downloads where?
netduino download pages is empty, nothing new there

can you please provice link to the secret download place?

[CW2]

netduino download pages is empty, nothing new there

There is netduino go firmware source link at the bottom of the middle netduino firmware source column.

[Chris Walker]

just a stupid question maybe, why are you not using codeplex anymore for source hosting?
just curious. must be a valid reason?

With Netduino Go, we had to temporarily split the code tree into two branches (netduino go and everything else). Once we get the two combined again (soon) we'll push everything to codeplex as well.

Chris

[Antti Lukats]

There is netduino go firmware source link at the bottom of the middle netduino firmware source column.

IT IS NOW!
It was not at the time I posted!

Antti

[CW2]

IT IS NOW!
It was not at the time I posted!

Oooooppppssss... switching the time machine off now