If you’re a commercial entity who has real concerns, jump on the phone and talk with the team. While Gus says he and the team are as transparent as they can be here, I suspect timing is one key thing he will never be able to be fully open with the full forum on. In a conversation, or perhaps under an NDA, I am sure he can help confirm timing that can help your planning, either by giving you the timing or taking your timing into account and telling you if TinyCLR OS is going to be something you can/should wait for
Fantastic Jay, thats good to know!
I just tried it out, and glad to see the old.ghielectronics.com back up and running and the links working.
Also test that the old Google links work.
It was suprising just how many times I go back to the old info, or found a link that took me there.
Its a value resource, so glad you got it back up!!
Thanks!
2 Likes
Yes I’ve had private conversations regarding the timeline of TinyCLR with them and they’ve been pretty transparent about timelines. It’s understandable that they don’t want to commit to a deadline publicly - that would be foolish.
Every software project I’ve worked on is “well… it’s done when it’s done!”
If people want hard deadlines I can give them my gut feeling based on experience, but you just never know what kind of obstacles you will encounter. Sometimes you may hit a roadblock that requires re-factoring very large amounts of code, and that slows things down badly. Other times, something you thought would be very tricky, turns out to be pretty simple; or someone has an epiphany that just works.
When you are on a large, complex project like TinyCLR, how do you know when it’s going to be done? You don’t. Just like an artist can’t commit to a deadline… if it has never been done before (or done THIS way), there’s no measuring stick to go off of.
Once it is OUT, them I’m sure they’ll commit to a standard release schedule of updates, etc. Layered tracking of issues, and feature requests, with locked in, set in stone “this is going in to the next version, that’s going in to the version after, and so on.”
The nice thing about GHI is they are light and agile, compared to a massive monolithic entity like MS, etc. You ever work with MS on a private hotfix for Server OS or Exchange? My god that’s an ordeal. By the time they get through reproduction in a lab, coding, regression testing, shiproom quality control, 6 or 8 months may pass. And that’s just for a bugfix…
it looks like you have not much experience with GHI
in the past we had to wait months, sometimes years for fixes and sometimes we are still waiting for fixes…
edit: and don’t forget GHI’s stable release cycle, was it once a year ?
Really sounds like you have an ax to grind Kevin.
Every post I’ve seen you make is negative of either GHI or critical / insulting to users on this board.
Not just in this thread, but everywhere on here.
2 Likes
i am so sorry that you miss understand the correction of false statements
what you wrote is wrong and i have in the past and will in the future correct such wrong statements
serious ? the next false statement
last but not least, i am happy that GHI’s biggest argument (Microsoft) does no longer exist and only GHI is responsible for the quality of their builds and speed of their releases (and of course bug fixes…)
I dont know about you but I have a great help and good experience with GHI even for stupid and amateur questions.
So for electronics product if reach stability in production there no need to change things so this is a reason why there’s less fix-es and you need to find way how/know with your hardware and you can not compare .net in pc with .net in mcu for fixes.
Also you have alternative instead using .NET (mbed,keil,python,arduino) for STM32F4 mcu
So you need to deal and split software and hardware for optimisation.
For example i use tinny85 with arduino or arduino mini as noded sensors reader or relay trigger and .net as master controller buy using rs232 or rs485 and i have no problem even with unfinished TinyClr since 0.5.0 because work well in all my projects
@valon_hoti_gmail_com absolutely, GHI’s support is one of the greatest
but that’s alone is not enough
at the end the finished product counts (with all the functions, bugs and missing features)
TinyCLR is promising but unfortunately not stable enough for production use and required features are not available (but that’s ok as TinyCLR is early alpha)
what you should not forget about your “alternative instead using .NET”…
as soon as a product is finished, why should one waste money to go back to TinyCLR only because TinyCLR is now production ready ?
Yes yes and yes. We take pride of our quality and work ethics. It is very sad that we on some occasions we came short and we are working very hard on fixing all previous mistakes.
2 Likes
@Gus_Issa well, you already did the first steps, you have realized and admitted some mistakes, i think that’s one of the hardest parts of your v1 into v2 transformation
I have netduino, arduino, tessel, raspberry pi 2-3, padi, esp8266, esp32, nucleo 401ret, brainpad, I bought almost all the gadgeteer modules + raptors + hydra + spiders, fezcream, fezhat, fezutility, and also I got atsaml21 dev kit… I code in C, C++, Java, kotlin, python, vb, delphi, C#, R, etc… from my perspective, it’s all about how you can deliver ‘value’ to your customers, so company decide what is the best strategy to make their products and services better, unique and different than the competitors. Microsoft is now open for all platform and all languages coz they want everyone can enjoy Azure regardless what are they using… for example, they put a lot of effort to provide IoT SDK to all embedded platforms, they slim down the win 10 to fit in SBC like raspi, joule, dragon board, etc. so how about GHI? I have created a lot of events in my country and introduce gadgeteer concept, netmf, tinyclr… then I collects my audience oppinions… what are they said? 1. expensive, but I understand its because the taxes and delivery cost. so, we can reduce the cost by porting tinyclr to the available dev boards in my country 2. the develoment of tinyclr is slow, of course they need to form and acquire a brilliant team for this or open the code for community contributions 3. community support, I know it’s about language barrier so I created local community 4. more sample code, drivers, projects… so I push the code on github and create some tutorials on youtube.
I have some notes from my experiences when using GHI products:
- nothing wrong with gadgeteer, its just costly… I can perform live demo in front of my customers/audiences from the scratch smoothly. when you start your project use plain netmf or tinyclr.
- if you want to runs faster, just take on C/asm
- drivers and libraries for CAN, usb client/host, glide, sqlite, cryptography are bonuses from GHI, if you want it, take the netmf version and port to tinyclr by yourself
- every platform has it’s own purpose, so, don’t write a blog using asm
- GHI is on the right direction, I love what I see on the back of brainpad case. you can code with python, c++, mbed,…
- the reason why I use C# for embedded is about productivity and time to market, because I have put a lot of investment in this language
so, we need more supports and contributions from people like you…
2 Likes
those were/are arguments to buy the more expensive GHI products… if my company would have to port it other already finished solutions are much cheaper
What company is that?
Returning to the discussion theme, I must say that from my point of view as a teacher who uses Reaper - Boards with many different modules in his lessons under NETMF my expectation would be that by switching to TinyCLR the first thing to do would be to make the Gadgeteer - Boards and modules running out of the box with TinyCLR.
It’s nice to see that a lot of different boards are able to run TinyCLR. But for me and my lessons that has very low relevance.
We baught those Gadgeteer - Kits
- because the ease of making connestions to the modules instead of wiring dozends of cables.
- the possibility to do programming on different skill - levels starting from very easy.
- the suggested long-term availability of the hardware. There are many much cheaper kits which do similar things (e.g. demo-boards) but they often disappear after some months). Unfortunately it was the same with GHI…
- in times where IOT is a important thing Gadgeteer gave an easy approach to handle with networking.
- as we do C# on PCs Visual Studio offered a possibility to do hardware programming without the need to learn a new language and IDE.
You see: at lot of reasons to make a decision to Gadgeteer / GHI.
So my expectation was: If they switch to TinyCLR (I understand the reasons for this), GHI tries everything to focus on the interest of their existing customers and make TinyCLR run as fast as possible to run on Gadgeteer hardware instead of kicking all Gadgeteer hardware stuff out.
To do a port from NETMF to TinyCLR for all the modules we have is a thing where I have a lack of time.
I did it for the N18 - display but it took too much time to scratch together all the information I needed and the hints I got have been only little helpful.
During the port I found out, that with TinCLR the language especially accesing the hardware has become much more complicated. You can see this already if you want to access a single Bit - Portpin. For this you have to programm really long codelines. For many of my pupils this is too complicated.
All in all:
I’m not sure if it is time for us to say goodbye to GHI.
We’ll watch the development for a while, but if there is no progress into the direction I tried to explain, then we have to go.
As i see different people use GHI/non GHI products for their different purpose
- Some for work
- Some for hobby
- Some for their customers
- Some as part of their work with combination (mixed way as me)
And everyone want just buy and sell to customer and want support from GHI for their bussiness
But wait we need to clarify some things
What is what for all things we are talking there
What is requested support
What is requested engineering
What is free and
What is payed
Since nothing is free or have time to loose.
GHI offer lot gamma of products and their products have support too,also this is OK
But do not wait for GHI to do job for you (make a specific driver and other things for non their products)
This a reason of community forum and all people that are attended can (or not - doesn’t matter) provide different help (volunters and share drivers or different source)
Sorry, but I don’t understabd fully, what you want to tell me. (Maybe because I’m German)
GHI was in large parts focused on education and is still (see Brainpad)
They produced kits (we baught many of them) and shortly before the break with NETMF there was (after years) an environment of soft- and hardware in combination with an active community that made it possible to work with this in education.
Then there was this break not only of software but also with the hardware.
We spent quite a lot of time to prepare lessons for the Gadgeteer stuff and maybe you can imagine, that we are somewhat disappointed.
But there was hope that we could at least use our Gadgeteer parts for a while with TinyCLR.
Right now I must see, that it will take a long time (maybe too long for us) until we can really use our equipment which we baught just some months before GHI stopped producing it.
You may know that in schools parts break faster than in industry. Where to get spare parts?
Community? I don’t really see a community so far in comparison to the situaltion before.
I believe that most of the Gadgeteer people moved somewhere else.
The problem is not the money. The problem is our limited time, the lack of an easy to use hardware.and the lack of support.
Sell and forget is not suitable for educational purposes.
I’m not sure @Valon’s response was to you or a more general commentary. Anyway, here’s what I think you need to consider.
Your investment in Gadgeteer hasn’t left you with nowhere to go - all the parts are still usable, including the software pieces you need. So not a lost investment, in my view. Sure, the versions of software you need are all old and stagnant, and any issues are unlikely to be addressed, but things that work today will continue to do so. Unfortunately, at commercial scale, there are no manufacturers who will build modules to replace existing ones, or who will build new modules or new mainboards - you could undertake to build short runs of them yourself, but you won’t get the commercial scale benefits that GHI had. You could approach someone here in the community to take on a short run module remanufacture on your behalf, there’s a few people I am aware of who have looked at this already.
Over time, I’d expect an amount of community contribution adding TinyCLR OS drivers for the remaining Gadgeteer modules that aren’t already covered in some of the work that’s already done mainly via @mifmasterz. This may then allow you to get the benefit of more modern investment in C#/TinyCLR OS and modern VS versions.
But also I’d suggest GHI haven’t “sold and forgot” you. The issue was really with support from Microsoft, not GHI - they prolonged offering what they did much past when Microsoft stopped investing. GHI had to make a hard financial decision, and unfortunately you were one of the affected people. (I have probably $1000 in Gadgeteer parts myself too, so I’m far from immune). I don’t think you can blame GHI for wanting to stay in business (I want them to!), no matter how harsh that decision seems to you.
I’m not telling you that you don’t have problems, but I am saying there’s not much you can’t work around if you think it’s still worth investing. It won’t be a simple “buy a new module as we go” but if you talk about what you might want you’ll probably find someone willing to help
1 Like
I’m just chiming in to say I haven’t quite caved yet and moved on. I’m a diehard fan and am holding on to what little hope I have. I’ve got 50 or so devices in the field relying on good old 4.3. Aim to do twice that next year. While I can thankfully still get the G120, half the stuff I sell relied on a physical LEMUR board, for that whole design I’ve got to start again now. I’m scared of sticking around though. I invested in the windows phone ecosystem for to long as well and got burned there. I’m not turning out to be a good chooser of tool chains. 
1 Like
the schematic is available so 90% of the risk should disappear right there… and the G30 is nowhere near as challenging to create a layout for than the G120 or above…
This is a great forum to share knowledge but we always recommend that we talk directly with commercial customers to work on helping them better. We are the manufacture and we are the engineers behind all of our products. There is no risk if we together work on a good plan for your own products.
1 Like