Sticky Current Development


Charles
 

Yes this was my initiale design. And it was not working....


Le lun. 24 avr. 2023, 21:53, mmessschuh via groups.io <mmessschuh=googlemail.com@groups.io> a écrit :
u mean if the focouser pins are high-level they cant boot? so it is a "problem" of the pin settings of esp8266, OK i just wondering about it.


mmessschuh@...
 

u mean if the focouser pins are high-level they cant boot? so it is a "problem" of the pin settings of esp8266, OK i just wondering about it.


Charles
 

Yes there is :)
If the pin for the focuser are low-level input the esp82666 cannot boot

Charles


Le lun. 24 avr. 2023, 21:29, mmessschuh via groups.io <mmessschuh=googlemail.com@groups.io> a écrit :
i have a question for the SHC. is there a special reason why all switches have high-level input, except the two focuser(they have low-level input)?


mmessschuh@...
 

i have a question for the SHC. is there a special reason why all switches have high-level input, except the two focuser(they have low-level input)?


Charles
 

Hi,

I modified the organisation on the Hardware repository, it was indeed for me difficult to organize the documentation on the Wiki and Git Repro
Probably it is better if the documentation (The html page are on the Git repro and not on io.group) I see that francois you do it that wax for your work and I think it is easier to maintain TeenAstro this way.
Currently it is a mess to keep the link on the wiki synced with the Git repro

https://github.com/charleslemaire0/TeenAstroHardware

If somebody has interest to write a page readme please feel free to push it

Charles


Charles
 

The goal is to have a modern and flexible interface for coordinate transformations:
this include mount alignment error
mount flexure
refraction
horizontal to sky transformations
field rotator

the beauty of the graph is that if at the moment we do not support flexure we just add a new node in the graph and the function that consume this code is untouched.

the mount miss Alignment is a part of the pipeline.
When we have an equatorial mount we have in this pipeline a  rotation that describe the Equatorial geometry. For an altaz this rotation is 0. for an equatorial mount it is 90-Lat in the north hemisphere

Maybe we could have a video conference next week to discuss this.
The first step is to implement a sample that do the transformation from the field rotator to the sky RA_DEC_ROT
Charles

Charles


John Archbold
 

Is the goal to handle erros relating to the mount operation?
  1. Alignment errors
  2. Mount flexure
  3. Tracking errors
I think the approach in EQMOD was to do a 'platesolve', create the transform matrix, and then continue.
So, by creating this transformation graph, this is possible automatically.


Charles
 

Hi Archie and Francois,

here is the transformation graph for the Geometry lib:
  PoseGraph graph;
  graph.add_transform("SkyOrigin", "SkyRA", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("SkyRA", "SkyHA", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("SkyHA", "SkyHADEC", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("SkyHADEC", "SkyAZALT", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("SkyAZALT", "SkyAZALT_R", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("SkyAZALT_R", "MOUNT", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("MOUNT", "AXIS1", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("AXIS1", "AXIS2", { Identity<3>(), {0, 0, 0} });
  graph.add_transform("AXIS2", "AXIS3", { Identity<3>(), {0, 0, 0} });

We can split Mount into many rotations and introduce Mount errors between the Axis

Charles 


John Archbold
 


Charles
 

Thanks Fred
My goal is to continue to support any version. So yes of course the upcoming release will work for any board with and without encoders

in the 2.5.1 the encoders are on each the SUB-D 9 port
There is a  pin for the reticule and one for the limit sensor

Thanks  for pointing that the link doesn't work. I fix it now.

Charles


Fred13115
 

It's every day Christmas with you Charles :))

Another question came up to my mind this night : the last version works  aswell with and without encoders, right ?

So the new main unit pcb must show new plugs for encoders, and one has to select "yes" or "no" in the web server wether one has or hasn't encoders ?

I've tried to have a look to it but, in the wiki page, the link to the pcb doesn't work : "The 'charleslemaire0/TeenAstro' repository doesn't contain the 'Released data/PCB/TeenAstroMini_2.5.1.zip' path in 'master'.  "

Enjoy the day.
Fred


Charles
 

Hi Fred,
Currently you can update over the air in two manner:

One way is over your web browser
The new one is from the développement environment. Arduino ide/visual micro etc...

Le dim. 5 févr. 2023, 08:26, Ti nicO <lordzurp@...> a écrit :

Not from the IDE ;)

 

De : TeenAstro@groups.io <TeenAstro@groups.io> De la part de Fred13115
Envoyé : samedi 4 février 2023 22:39
À : TeenAstro@groups.io
Objet : Re: [TeenAstro] Current Development

 

On Sat, Feb 4, 2023 at 07:38 AM, Charles wrote:

2.Arduino OTA is a method for flashing the microcontroller over the air.
When I am developping I don't want to open the box to flash the ESP8266. Now I can compile and flash the SHC without any cable. It was indeed easy.

This feature is an old one, isn't it ?


Ti nicO
 

Not from the IDE ;)

 

De : TeenAstro@groups.io <TeenAstro@groups.io> De la part de Fred13115
Envoyé : samedi 4 février 2023 22:39
À : TeenAstro@groups.io
Objet : Re: [TeenAstro] Current Development

 

On Sat, Feb 4, 2023 at 07:38 AM, Charles wrote:

2.Arduino OTA is a method for flashing the microcontroller over the air.
When I am developping I don't want to open the box to flash the ESP8266. Now I can compile and flash the SHC without any cable. It was indeed easy.

This feature is an old one, isn't it ?


Fred13115
 

On Sat, Feb 4, 2023 at 07:38 AM, Charles wrote:
2.Arduino OTA is a method for flashing the microcontroller over the air.
When I am developping I don't want to open the box to flash the ESP8266. Now I can compile and flash the SHC without any cable. It was indeed easy.
This feature is an old one, isn't it ?


Charles
 

1 The encoders can be anywhere. important is that when you release the telecop the encoder rotates as the telescop is moving => the worm gear is a bad place.
TeenAstro uses instrumental coordinates in degree:
-you have instrumental coordinates that are derived from the stepper position
- instrumental coordinates that derived from the number of read pulse from the encoder
you can see both coordinates when you go in the limits menu and select display coordinates
When the encoder is correcly configure then both coordinates are exactly the same. Hence the encoder has its own gear and its own reverse parameter.
2.Arduino OTA is a method for flashing the microcontroller over the air.
When I am developping I don't want to open the box to flash the ESP8266. Now I can compile and flash the SHC without any cable. It was indeed easy.

Ti Nico has translated the object Names in French and German. So you can see the translated nebula names.
I improved also the Memory management on the SHC, It was necesssary has we have more and more functions


 


Fred13115
 

Hello Charles

What an impressive job !

Two newbie's questions if you please.

1- TA doesn't care about the gear ratio between the encoder's axis and the mount's axis, does it ? Does-it mean one can place the encoder anywhere in the mechanical train ? Or did you assume the encoder is placed on the mount's axis ? or on the motor axis ?

2- What means "The SHC supports now Arduino OTA." ?

Fred


Charles
 

Hi,

I have created a new branch for the new TeenAstro firmware version 1.4.x:
- This version support Teensy 3.2 AND Tennsy 4.0
Encoder support is now complete:

you can now use TeenAstro without stepper motor, use it with Skysafari and  enjoy the catalogs in SHC.
The distance to the target is displayed in Arc Minutes
when you have reached the target press the SHIFT button
then TeenAstro ask if you want to synchronize to the target just  press Right if yes, if not select no and Press Right
TeenAstro now support two setup!
That mean's that you can use TeenAstro with your german Equatorial or your dobson in pushTO
To change the current mount you just have to select the mount in the SHC (TeenAstro need to reboot)
in the webserver you can even give each setup a name and the name is visible in the SHC:


The SHC supports now Arduino OTA. 


Charles
 

Hi,

I have added a PushTO function in the main unit, it works only if you have encoders
I have now to update the SHC to support that new feature

Charles


Charles
 

Yes you will need 2 more resistors


Le jeu. 12 janv. 2023, 15:15, <astrosmartphone2b@...> a écrit :
Hi everyone, I started in teenastro on the mini 2.4 version, I have all the components apart from the teensy 3.2, my question is do the components I have suddenly go on this version 2.5 apart from the teensy which will be version 4.0 😁


John Archbold
 
Edited

Hi All,

I have morphed the Teensy from dragonlost on EASYEDA into an ESP32-S3 based device.
I will transfer to other EDA system if requested.

It supports both the ESP32-S3-DEVKITC-1 (approx 10 euro)
(https://www.digikey.com.au/en/products/detail/espressif-systems/ESP32-S3-DEVKITC-1-N8/15199021)
and the WROOM-S3(approx 3 euro)
(https://www.digikey.com.au/en/products/detail/espressif-systems/ESP32-S3-WROOM-1U-N8R2/16162651)

You can access the design here and any comments are welcome.
(https://oshwlab.com/search?wd=teenastro&page=1)
At the end of January I will order some PCBs from JLPCB.
I am testing a prototype at the moment, using my EQ6.

I am currently checking to see if I can get the software to compile side by side (using VSCODE and platformio) so that it remains the same as Charles software.
(https://github.com/ozarchie/TeenAstro)

All comments and suggestions are welcome. I have continued the GPL3 licence.