Documentation is incomplete
-
@Manuel-Godinez said in Documentation is incomplete:
you should have 100% of the documentation. ...... But well, going to have to wait for the eBook
.If you are new you can have also a look in to the wiki ... wiki.onion.io to get an idea of the Operatingsystem etc. I bet with you that the e-Book will not be more as the Manual you have online now, just more complete.
Normally in a open-source hardware- and software community things are never from the beginning 100%. Ppl. work it together out and bring it there where it has to go.
Even Microsoft where never was open-source minded in the past, and always charged license fees, did let clients make the beta-testing and when you wanted a more sophisticated Manual you had to pay extra.
So change your mind and thins get changed
-
@Costas-Costas :)) Good one! Also, the GPIO tool app (Cloud) is currently working on my end. I am running latest firmware b149.
-
@Manuel-Godinez I'm also running b149. So GPIO tool is fine for you locally and via the cloud? It shows Omega 2 pinout or Omega?
-
@Costas-Costas Yes, works fine. I go into the tool, and select first the Omega2 that is running, then since it has a default pin of 0 (zero) I go and either select 1 or 0 and just for the heck of it, pressed the Sync button. Once I do that, I am reading 3v when (1) high and 0 when (0) low using a voltmeter.
-
But is the image for a Omega 2 or an Omega and are you seeing Omega 2 pins or just Omega pins? For example can you see pins 45 and 46 that are new to O2?
Could you please post a screenshot?
Just to add I can control some pins via the cloud but the board selection only shows Omega layout not Omega 2. So pins that are common to both MCU's are OK but not the new pins.
-
@Costas-Costas Yes, I didn't look deep enough so I was just looking at the default pin 0. Seems they have not updated the page with the Omega2 pins, but just to be clear, I am using the dock and the pins layout is also not the Omega2. I was only testing using pin 0 until you mention it. Oh well, Onion has a LOT of updating to do in their hands, I only wish they would release the eBook already, but don't want to rush them or they will miss parts in that one too
-
Thanks for the confirmation @Manuel-Godinez
As an experienced Blynker I don't currently need the GPIO Tool but other users certainly will.
My +2 takes snapshots from a cheapo webcam and emails them to me, all done without port forwarding and with the power of Blynk. Currently snapshots are sent on demand but can be set based on sensors or button pushes etc.
Will post more details at some stage but the setup details for Blynk are at https://wiki.onion.io/Tutorials/blynk-library
It needs an update for +2 pinout but the developers at Blynk have it in their roadmap.
-
Just coming back to the documentation I can't fine the Omega, as opposed to Omega 2 stuff.
Looks like someone has edited the Omega stuff into Omega 2 and not made the appropriate changes for Omega 2.
First thing I looked at was the onboard LED at https://docs.onion.io/omega2-docs/the-omega-led.html#the-omega-led
The path's quoted are incorrect. Don't know if they were right for the Omega as I don't have one.
-
@Costas-Costas said in Documentation is incomplete:
Looks like someone has edited the Omega stuff into Omega 2 and not made the appropriate changes for Omega 2.
Yea, that's what i realized too... so check out on github ... might be better to see the difference ... and or if you find out something you can participate with pull requests to change the Omega2 Manual.
https://github.com/OnionIoT/Onion-Docs
versus
https://github.com/OnionIoT/wikiSometimes it my has something in work on git-hub where is not published yet in wiki/doku.
-
Looks like the GitHub is different to the WiKi.
What's the reason for 2 lots of docs that need to be corrected and kept up to date?
-
@Costas-Costas said in Documentation is incomplete:
What's the reason for 2 lots of docs that need to be corrected and kept up to date?
I bet the documentation will be the e-Book and the wiki will be the resources for omega1.
-
Oh yes with the Ebook that makes 3 lots of docs.
-
@Costas-Costas said in Documentation is incomplete:
Oh yes with the Ebook that makes 3 lots of docs.
No, did you not realize that the structure is all-ready different in the documentation? Just export as a e-document and you have your e-book where you can download ...
-
Also, I think we all would greatly benefit from an ongoing FAQ section. The answers have to be validated and clear. And they should be from the designers of the product. I have spent countless hours trying to figure things out and when I think I have the answer, a new problem arises. Or the figured out problem goes bad again. And I don't know why. Like being disconnected from WiFi for no reason. I finally got it working, but afraid to touch anything!
The documentation is very hard to follow. It makes you skip around and then you can't find where you were. It's very poor to show 1 page of a topic, which doesn't continue. One has to jump back to choose the sub-topic. About the not having to login all the time. Why can't it just be remembered in the OS? Another example, the section doing a command line: oupgrade. The word is in the middle of the sentence in a very light font. You can hardly see it. It should on a line by itself, bold and red. I see many more examples like this. Clear and clean documentation so important!
The first time user, very important person, should be shown step by step how to get the Omega2+ up and working in the most basic way. When appropriate, the steps should be illustrated and explained. For a while, I didn't know if my laptop was actually a wireless client of the Omega. And didn't know the laptop has to be a LAN client of my router. This setup is not usual for a new comer.
This is where a diagram of the connections should be shown.To Onion Management: You do know that hundreds of UNPAID Quality Control Experts are working for you. Without us..... No Omega2+ You need to live up our bargain more.
WE WANT YOU TO SUCCEED !
-
-
Yes the documentation would be better if you didn't have to skip about, poor design in my book (no pun intended).
-
Noticed the almost invisible grey commands hidden within the text. +1 for new line in red.
-
Looks like fast-gpio doesn't work as documented, comes back with:
segmentation error- Could the Onion doc person confirm they are watching this thread or advise how they want to be informed of the errors and omissions?
-
-
@Don-DeGregori , nice point ... i mentioned the FAQ 5 Month ago ....
http://community.onion.io/topic/989/onion-freshdesk-com-support-home-faq
-
- Looks like fast-gpio doesn't work as documented, comes back with:
segmentation errorYes, I ran into something like that before and the problem lies in the syntax, for example the docs says something like: (Example only)
fast-gpio call more -p
The syntax should be something like instead
fastgpio -p call more
AGAIN, this is just an example but you get the idea of what is going on. I just type words as an example and are not actual commands and options.
-
The syntax at https://docs.onion.io/omega2-docs/using-gpios.html is shown as:
fast-gpio read <gpio pin>but
fast-gpio read 5gives the error I stated (technically Segmentation fault) and
fast-gpio 5 readDoesn't error but gives no response.
-
Best way is to do a issue on github as far as there is not changed yet.
From own experiences i got there the best request times for answers.
-
@Costas-Costas The segmentation fault - error is due to missing /dev/mem, not due to something in fast-gpio being wrong. You just have to wait for Onion-devs to fix their kernel.
