Date
1 - 12 of 12
Manual
Stephan
Dear All,
I would like to contribute a little and would offer to start something like an end-user manual for Teen Astro. It might make sense to start it as a Wiki here and some of you can fill the gaps where I have no knowledge. Ideally we could compile a PDF document from the Wiki at any point.
@Charles, could you open a section in the Wiki and have me enter the data?
Brgds, Stephan
I would like to contribute a little and would offer to start something like an end-user manual for Teen Astro. It might make sense to start it as a Wiki here and some of you can fill the gaps where I have no knowledge. Ideally we could compile a PDF document from the Wiki at any point.
@Charles, could you open a section in the Wiki and have me enter the data?
Brgds, Stephan
Hi Stephan,
You have know rights!
May be a google doc is also good, because many people can edit at the same time
for the document you can work with Fred. May be it is better if you are align and now what you want to do.
I suggest that we can have a TeenAstro meeting each month or each 2 month to stay synced :)
Charles
Dear All,
I would like to contribute a little and would offer to start something like an end-user manual for Teen Astro. It might make sense to start it as a Wiki here and some of you can fill the gaps where I have no knowledge. Ideally we could compile a PDF document from the Wiki at any point.
@Charles, could you open a section in the Wiki and have me enter the data?
Brgds, Stephan
Hello TeenAstro
If Stephan or anyone else believe it's usefull, I'll send the .odt files I have written for improvement. Please feel free to ask.
If you've written something and don't have rights to upload it on the wiki, I can make it for you.
One concern is the lack of tutorial for newbies to make TA talking with KStar, Stellarium, SkyCharts, and others.
For the moment, TA appears to be quickly changing ; for this reason, I believe we should wait for Charles to tell us wich features may not change anymore, and wich are still in progress.
CS
Fred
If Stephan or anyone else believe it's usefull, I'll send the .odt files I have written for improvement. Please feel free to ask.
If you've written something and don't have rights to upload it on the wiki, I can make it for you.
One concern is the lack of tutorial for newbies to make TA talking with KStar, Stellarium, SkyCharts, and others.
For the moment, TA appears to be quickly changing ; for this reason, I believe we should wait for Charles to tell us wich features may not change anymore, and wich are still in progress.
CS
Fred
Hi
I would be happy if we could have something like this:
http://www.astro-electronic.de/anleit_e.pdf
Charles
I would be happy if we could have something like this:
http://www.astro-electronic.de/anleit_e.pdf
Charles
Hi Charles, Fred and all,
I use teenastro and Asiair.
I can bring my contribution if Fred want about it on the the tutorial about it…and if you need help the layout of the tutorial on the model like Charles would want.
I agree with you, I see that TAstro change very fast…so let’s wait and see for now.
I have made update from one of my teenastro but I wait for about the next that work into my observatory. 😄🤭
Jmarc
Le 5 mars 2023 à 11:24, Charles <charleslemaire37@...> a écrit :
Hi
I would be happy if we could have something like this:
http://www.astro-electronic.de/anleit_e.pdf
Charles
Sebastian Schmidt
Dear All, Stephan,
since i came in contact with teenastro i always had moments were i thought that it would be nice to have a more compact/complete manual from the very first start of building to a working product with all (current)
options explained. I also took a look at onestep and compared with it, teenastro is indeed alot easyier, but beside the momentary overwhelming speed of development i always found this and that wich was not selfexplaining.
I know it s more ore less a oneman show and i would not know how much work the this coding stuff etc. is. Thats a blackbox for my knowledge, and a fantastic job from Charles and also others.
I think, when one do such a project, sometimes its hard to get a objektive look from the outside of it. For example, the symbols in the shc wich belongs to the GPS are not all explained at the wiki, just two of them but the ones with a "!" in it,
i have no glue what it means. Or if you use Skytrack , its only working with IP based connection to TA. Or do you also wonder if both teensys need a quarz soldered underneath?I did. All this little things have to be collected over the net and mailing lists.
On top the whole projekt is moving fast right now. So i would be nice to have a little roadmap and maybe also consider all existing users with their TA´s.
My freetime is also not that big but iam willing to contribute some text or ideas for a good outlined manual. My question is, wich way can we go to have a room of developing this? Google docs are nice, but a discorde to discuss is also a good option?
Sebastian
Am 04.03.2023 um 16:41 schrieb Stephan via groups.io:
since i came in contact with teenastro i always had moments were i thought that it would be nice to have a more compact/complete manual from the very first start of building to a working product with all (current)
options explained. I also took a look at onestep and compared with it, teenastro is indeed alot easyier, but beside the momentary overwhelming speed of development i always found this and that wich was not selfexplaining.
I know it s more ore less a oneman show and i would not know how much work the this coding stuff etc. is. Thats a blackbox for my knowledge, and a fantastic job from Charles and also others.
I think, when one do such a project, sometimes its hard to get a objektive look from the outside of it. For example, the symbols in the shc wich belongs to the GPS are not all explained at the wiki, just two of them but the ones with a "!" in it,
i have no glue what it means. Or if you use Skytrack , its only working with IP based connection to TA. Or do you also wonder if both teensys need a quarz soldered underneath?I did. All this little things have to be collected over the net and mailing lists.
On top the whole projekt is moving fast right now. So i would be nice to have a little roadmap and maybe also consider all existing users with their TA´s.
My freetime is also not that big but iam willing to contribute some text or ideas for a good outlined manual. My question is, wich way can we go to have a room of developing this? Google docs are nice, but a discorde to discuss is also a good option?
Sebastian
Am 04.03.2023 um 16:41 schrieb Stephan via groups.io:
Dear All,
I would like to contribute a little and would offer to start something like an end-user manual for Teen Astro. It might make sense to start it as a Wiki here and some of you can fill the gaps where I have no knowledge. Ideally we could compile a PDF document from the Wiki at any point.
@Charles, could you open a section in the Wiki and have me enter the data?
Brgds, Stephan
Well, you're right Sebastian.
On one hand, Charles doesn't have the time to send me each new icons he creates.
On the second hand, I didn't find the way to get them from the Code by myself.
And on third hand (!)) sometimes I believe they're clear, but they're not.
T! means : the GNSS time is different from the TA time
L! means : the GNSS location is different from the TA location
I don't know why the GNSS values don't overwrite the TA ones. That would be interesting to know.
About the cristal or not the cristal on the Focuser's TeenSy : I've uploaded on june, the 24 last year, this file on this page ; I believe you've found the answer by yourself before this date.
About contributing : the first way is to ask questions on the forum, even on documents that may not be clear enough.
A second way may be to write a document about the answer one find, by oneself or on the forum, at a question one had.
When enough Questions/Answers, we'll organise them through chapters on the User's Manual.
About voice chating on Discord : we already have this forum to talk together, and, for some of us, spoken english is less fluent than written one. Moreover, I believe voice/video chating is more carbon consumer than written one.
Fred
On one hand, Charles doesn't have the time to send me each new icons he creates.
On the second hand, I didn't find the way to get them from the Code by myself.
And on third hand (!)) sometimes I believe they're clear, but they're not.
T! means : the GNSS time is different from the TA time
L! means : the GNSS location is different from the TA location
I don't know why the GNSS values don't overwrite the TA ones. That would be interesting to know.
About the cristal or not the cristal on the Focuser's TeenSy : I've uploaded on june, the 24 last year, this file on this page ; I believe you've found the answer by yourself before this date.
About contributing : the first way is to ask questions on the forum, even on documents that may not be clear enough.
A second way may be to write a document about the answer one find, by oneself or on the forum, at a question one had.
When enough Questions/Answers, we'll organise them through chapters on the User's Manual.
About voice chating on Discord : we already have this forum to talk together, and, for some of us, spoken english is less fluent than written one. Moreover, I believe voice/video chating is more carbon consumer than written one.
Fred
Stephan
Hi all, I have pasted a text I had prepared into a Wiki page called:
It is not linked from the sidebar, so it will hopefully not confuse people. Some features are not clear to me, that's where I have out question marks, feel free to fill the gaps and correct my mistakes. I will start to add some of the TA icons and I plan to add a section with some hardware details.
Brgds, Stephan
It is not linked from the sidebar, so it will hopefully not confuse people. Some features are not clear to me, that's where I have out question marks, feel free to fill the gaps and correct my mistakes. I will start to add some of the TA icons and I plan to add a section with some hardware details.
Brgds, Stephan
Sebastian Schmidt
Hi,
how can I contribute/write her?
Sebastian
Am 05.03.2023 um 20:26 schrieb Fred13115:
how can I contribute/write her?
Sebastian
Am 05.03.2023 um 20:26 schrieb Fred13115:
Hello Stefan
Some answers in italics ; if you approve, change it to normal police.
If more details are required, or if it's not clear, or not grammatically correct, please feel free to tell.
Brgds
Fred
Sebastian Schmidt
Hi,
oh ok, right know i have nothing writen down. I just thought i could add something into the postet text. On some points ia just have remarks
So i have no prob to write something down for dedicated aspects. Just wanna be shure not to do some doubles.
Sebastian
Am 06.03.2023 um 14:14 schrieb Fred13115:
oh ok, right know i have nothing writen down. I just thought i could add something into the postet text. On some points ia just have remarks
So i have no prob to write something down for dedicated aspects. Just wanna be shure not to do some doubles.
Sebastian
Am 06.03.2023 um 14:14 schrieb Fred13115:
Hello Sebastian
Could send your document here on this topic, and Stefan or I will include it on the wiki ?
Fred