Basically you can use the module, communication via BT / BTE can be like as using the Arduino. And yes, of course, it takes some effort to rewrite the code, but in my opinion it is worth it.
I have also checked the SQM and Dewcontroller also on the module, and it would be possible. All Temp sensors via OneWire will need only one I / O port. So Focuser and Dewcontroller can share the Temp sensors, also an advantage. In my trial version, i planned to save the BUZZER and the LED for IN and OUT and to control two OLEDs via I2C, possibly only one larger color display.
The majority of the code can be taken over 1:1, the rest is "handmade"
At the same time eqdirect by WiFi would be possible.
The only difficulty is the communication of the software, because there is only one BT connection and everything about it exchanges the data, but that too will hopefully be solved.
The connection via USB will continue to exist.
By that i first realized how much work and time Robert has put into these projects, and can only say thank you for the fact that he helped us a lot.
And now i start to implement my designs on the paper in the Fritzing, for the beginning only the focuser with BT. next step expansion around the sqm.
Cheers Toni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
You might look at a larger TFT using SPI?
If using two I2C displays you would have to make sure each is on a different address.
Controlling it via ascom will be an issue. I cant think of a way around this at present.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the sketch version (Focuserv258_DRV8825_HW203_OLED_RE_F) i have already run on the arduino nano with me to adapt to the EPSWROOM32.
Code changes took about 90 minutes. eeprom must be completely replaced by the nvs and the code for the rotaryencoder is still missing, this will take a while.
the rest can already be completely compiled and requires 11% of the available memory :D
If all goes well and the hardware test also then I will extend the code to WiFi and BT and can then optionally be used for the connection.
cheers Toni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
nvs.h replaced by prefenrenzes.h - replace EEPROM thinks
standalone new code for testing rotaryencoder
pretest comunication select (BT, WiFi, WiFi mode) at start with rotaryencoder
It's not so easy as i thought, especially since the espwroom32 is still relatively new, and the Arduino IDE support is accordingly - and that ends up in a mostly longer search for solutions ;)
The only thing I can say so far that it will be possible anyway with the appropriate effort to transfer the focuser on the module, At the moment I assume that I'll need about 1 to 2 weeks to implement the gasamten code - including the extension for BT / WiFI, and the corresponding hardware tests. then I can gladly provide all the necessary data for reproduction.
Robert if there is interest that someone wants to have the code, should i just send the customized code in the discussions as an attachment?
Cheers Toni
Last edit: Rev.Antun 2017-11-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes that is probably the best way.
The real test is about reponse - how long does it take focuser to respond to a command once issued.
I found lag time very serious issue with Wifi
I tested using serial monitor interface, send command by hand and then time response
I found sometimes it got to 2-3 seconds lag time
When trying under dark sky autofocus software the lag time was serious issue
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
Basically you can use the module, communication via BT / BTE can be like as using the Arduino. And yes, of course, it takes some effort to rewrite the code, but in my opinion it is worth it.
I have also checked the SQM and Dewcontroller also on the module, and it would be possible. All Temp sensors via OneWire will need only one I / O port. So Focuser and Dewcontroller can share the Temp sensors, also an advantage. In my trial version, i planned to save the BUZZER and the LED for IN and OUT and to control two OLEDs via I2C, possibly only one larger color display.
The majority of the code can be taken over 1:1, the rest is "handmade"
At the same time eqdirect by WiFi would be possible.
The only difficulty is the communication of the software, because there is only one BT connection and everything about it exchanges the data, but that too will hopefully be solved.
The connection via USB will continue to exist.
By that i first realized how much work and time Robert has put into these projects, and can only say thank you for the fact that he helped us a lot.
And now i start to implement my designs on the paper in the Fritzing, for the beginning only the focuser with BT. next step expansion around the sqm.
Cheers Toni
Hi
You might look at a larger TFT using SPI?
If using two I2C displays you would have to make sure each is on a different address.
Controlling it via ascom will be an issue. I cant think of a way around this at present.
Regards
Robert
Hi Robert!
I have 2 I2C 0.96" displays with different addresses. The ASCOM problem - that's too bad :(
Of course, I can go another way, for all my own esp32 module and use the BT connection - then the ASCOM problem would be solved.
Anyway, within the next two weeks, the Focuser will run on the Modul with BT. Just connect to the ESP32 module via the Arduino socket ;)
Cheers Toni
Hi!
If each (ASCOM) driver have their own com (eg BT) interface, then there is no problem - right?
If so, then I have solved the problem. I use an serial port expander, need additional code on sketch but that's will be work :D
Last edit: Rev.Antun 2017-11-14
yes
Hi!
I have the sketch version (Focuserv258_DRV8825_HW203_OLED_RE_F) i have already run on the arduino nano with me to adapt to the EPSWROOM32.
Code changes took about 90 minutes. eeprom must be completely replaced by the nvs and the code for the rotaryencoder is still missing, this will take a while.
the rest can already be completely compiled and requires 11% of the available memory :D
If all goes well and the hardware test also then I will extend the code to WiFi and BT and can then optionally be used for the connection.
cheers Toni
Hi!
Status update:
It's not so easy as i thought, especially since the espwroom32 is still relatively new, and the Arduino IDE support is accordingly - and that ends up in a mostly longer search for solutions ;)
The only thing I can say so far that it will be possible anyway with the appropriate effort to transfer the focuser on the module, At the moment I assume that I'll need about 1 to 2 weeks to implement the gasamten code - including the extension for BT / WiFI, and the corresponding hardware tests. then I can gladly provide all the necessary data for reproduction.
Robert if there is interest that someone wants to have the code, should i just send the customized code in the discussions as an attachment?
Cheers Toni
Last edit: Rev.Antun 2017-11-20
Yes that is probably the best way.
The real test is about reponse - how long does it take focuser to respond to a command once issued.
I found lag time very serious issue with Wifi
I tested using serial monitor interface, send command by hand and then time response
I found sometimes it got to 2-3 seconds lag time
When trying under dark sky autofocus software the lag time was serious issue
Regards
Robert