Schematics
-
I'd like to know where can the schematics file of omega and extension be download?
I see other similar topic but I was unable to open them: a white empty page was displayed when I followed the link from google.
thanks in advance
ing. Christian Fontana
-
@Christian-Fontana Hi, that is something I and others have asked (see: https://community.onion.io/topic/7/omega-hardware-documentation)
Unfortunately, the Omega people have a lot of work on and providing this is on their to-do list.
I have offered help in preparing such material but still awaiting the source materials (see: https://community.onion.io/topic/312/is-there-a-version-changelog/5)
-
@Christian-Fontana We have already generated some of the schematics, and we are just waiting for our hardware team to check them over to ensure there's no errors. We should be releasing some of them in a week or so.
-
@Kit-Bishop and @Boken-Lin : thanks for your answers. I'm waiting for news.
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
As mentioned in another thread where you repeatedly asked the same thing:
We're working on high priority features revolving around the cloud and app store. Please have patience, we will be open sourcing the designs when we have the time.
-
@Lazar-Demin as said elsewhere, I do understand that opensourcing the complete design as promised in the kickstarter campaign does not have top priority, but marketing/cloud does.
Still, I don't entirely buy the given excuses for not just posting the schematics. If you have produced the onion, which you obviously have, there's also an error free schematic drawing already existing, which you could post as-is. No need to "generate" or "have hardware guys check it". It would be a matter of a few minute's work to create a github repo for the onion hardware and push the schematics as a first step - and then update it over the next few months to finally make it a complete hardware documentation.
Why is this so important? Because I'm looking at the Omega as a building block to replace RPis in an existing product of mine, needing a few hundreds, maybe thousands of units p.a.. Why do I need the hardware being OS for that? It's a matter of risk management - what if Onion decides to discontinue the Omega for some reason, maybe 3 or 5 years from now? When the design is completely open, that's a risk I can take - because OS would offer a way out.
The point is that your once prominent (in the Kickstarte campaign) commitment to complete Opensource has a bit faded. I need a clear sign (such as publised schematics!) in order to not becoming afraid that more traditionally oriented forces within Onion try to steer away from open source. Sorry for the lack of confidence, but I've seen that happen too many times to "just believe and wait"...
-
This post is deleted!
-
@Lukas-Zeller you make valid points and I understand your concerns, I just want to reassure you that we are committed to being an open source company.
As such, we've created a GitHub repo to document all of the Onion hardware: https://github.com/OnionIoT/Onion-Hardware
For now, it only contains the schematics for the Expansion Dock, but we will be adding to it in the coming weeks.Our hardware team in China is currently on vacation due to the Lunar New year so the going has been slow lately. Additionally, they all use a variety of tools, some being pretty ancient, so there was work required in generating the schematics.
Thank you for your patience from all of us here at Onion
-
This post is deleted!
-
@Lazar-Demin thx a lot - looks promising! I'll now patiently wait for the end of chinese lunar new year and hopefully the schematics of the omega itself will be added to the git repo soon...
In the meantime I had a look at the expansion dock schematics - I thoroughly hope the reset button on the actual expansion dock is not wired like that
(if VDD25 is what the name suggest, a power supply, then this wiring would not only keep the omega reset forever, but also short-circuit the power supply)
-
This post is deleted!
-
https://community.onion.io/topic/379/when-will-onion-open-source/7#
@Lazar-Demin said:
... we will be open sourcing the designs when we have the time....
Thanks,
The Onion Team
-
@Lukas-Zeller lol no, it's just a wonky diagram. What's actually happening is that the RESET_BTN net is usually connected to ground, but when the button is depressed, it will be connected to VDD25 (which is 2.5 V).
Also, we've added two more schematics to the repo, hoping to add more later this week, stay tuned, we will deliver!
-
This post is deleted!
-
@Lazar-Demin thx for the additional schematics (the reset button is much more convincing on the mini dock schematic...).
Still, all three are only little more than pinout descriptions - I'm really waiting for the actual Omega schematic! Or at least for the Ethernet expansion dock, for starters.
@Yejin-Chen I don't believe they want to fool customers on purpose, it's just a way too low prio for them - which I regret.
-
Two more schematics are up on the GitHub repo: the Ethernet and Servo Expansions this time.
Thank you everyone for your continued patience, I hope that with the work we've been putting out recently, you guys can see that we're focused and committed to delivering on all of our promises. We are not in the business of fooling our customers.
Happy hacking!
-
While still waiting for the omega schematics, I was hinted at a project called VoCore. The hardware is similar - MIPS 24k SoC made for routers, same amount of RAM and flash, radio, ethernet etc.
And they HAVE published full schematics and layout (as PDF and Mentor Graphics PADS files)!
To be fair, in many other aspects the VoCore project does not come even near the Omega's level, for example the software (just has a thin wiki with a few hints how to build stock OpenWRT), the shop, extensions etc. Onion is certainly providing much more.
But still - for those who want to get at least an idea of the circuitry needed around such a router SoC, http://vocore.io/wiki/index/id:11 might be worth a visit.
And for @onion - I still don't really understand why this is taking so long. You do have the CAD/CAM files - so what's so awfully time consuming? Just print the schematics to PDF from your CAD, and throw them into the HW git repo. I simply can't imagine circumstances that would make this more than a 5 min task - other than reluctance to publish at all.
