|
new FYSETC S6 build
I just took my soldering iron to a DS3231 RTC module and lifted the SDA pin of the AT24C32 EEPROM with a little common screw-driver. Plugged it in and enabled the option. It works fine too, remembers
|
I just took my soldering iron to a DS3231 RTC module and lifted the SDA pin of the AT24C32 EEPROM with a little common screw-driver. Plugged it in and enabled the option. It works fine too, remembers
|
By
Howard Dutton
· #23093
·
Edited
|
|
new FYSETC S6 build
The S6 Wiki now has Pin information that covers most of what you need to get one of these up and running.
|
The S6 Wiki now has Pin information that covers most of what you need to get one of these up and running.
|
By
Howard Dutton
· #23092
·
|
|
new FYSETC S6 build
The BME280 works fine for me, no issues so far. Many reboots.
|
The BME280 works fine for me, no issues so far. Many reboots.
|
By
Howard Dutton
· #23090
·
|
|
new FYSETC S6 build
Software serial isn't really "Ok" with OnStep but I suspect the disruption would mostly be on transmit where one has to create the exact timings in software (interrupts disabled.) There is nothing tra
|
Software serial isn't really "Ok" with OnStep but I suspect the disruption would mostly be on transmit where one has to create the exact timings in software (interrupts disabled.) There is nothing tra
|
By
Howard Dutton
· #23089
·
|
|
new FYSETC S6 build
I added support in the HAL for the RX2/TX2 port for GPS (only.) In Config.h then use the following... #define SerialGPS SoftwareSerial2
|
I added support in the HAL for the RX2/TX2 port for GPS (only.) In Config.h then use the following... #define SerialGPS SoftwareSerial2
|
By
Howard Dutton
· #23088
·
Edited
|
|
new FYSETC S6 build
You can't have the PPS signal from a DS3231 or DS3234 without OnStep attached and talking to it to set that up. GPS usually has PPS without talking to it.
|
You can't have the PPS signal from a DS3231 or DS3234 without OnStep attached and talking to it to set that up. GPS usually has PPS without talking to it.
|
By
Howard Dutton
· #23087
·
|
|
new FYSETC S6 build
Serial is the USB Serial1 is next to X- marked UART (where my WeMos is plugged into.) And there's Serial3 on the EXP1 connector.
|
Serial is the USB Serial1 is next to X- marked UART (where my WeMos is plugged into.) And there's Serial3 on the EXP1 connector.
|
By
Howard Dutton
· #23082
·
|
|
new FYSETC S6 build
... and my clock runs about 0.25% fast also. That's in the ballpark of what you see with ceramic resonator accuracy.
|
... and my clock runs about 0.25% fast also. That's in the ballpark of what you see with ceramic resonator accuracy.
|
By
Howard Dutton
· #23081
·
|
|
new FYSETC S6 build
Same result here, that is a shame. All those pins and only two TTL serial ports. I can create a HardwareSerial Serial2, but it doesn't work. Library based SoftwareSerial fails to compile.
|
Same result here, that is a shame. All those pins and only two TTL serial ports. I can create a HardwareSerial Serial2, but it doesn't work. Library based SoftwareSerial fails to compile.
|
By
Howard Dutton
· #23079
·
|
|
new FYSETC S6 build
Checked the PEC sense also. Again it was where it was supposed to be and had the desired effect. Just poking around with a grounded lead on sense inputs set for INPUT_PULLUP and active LOW. The Wiki i
|
Checked the PEC sense also. Again it was where it was supposed to be and had the desired effect. Just poking around with a grounded lead on sense inputs set for INPUT_PULLUP and active LOW. The Wiki i
|
By
Howard Dutton
· #23076
·
|
|
new FYSETC S6 build
I can report that: Limit sense - works as expected. Axis 1 Home Sw - works as expected. Axis 2 Home Sw - works as expected.
|
I can report that: Limit sense - works as expected. Axis 1 Home Sw - works as expected. Axis 2 Home Sw - works as expected.
|
By
Howard Dutton
· #23075
·
|
|
new FYSETC S6 build
No luck here getting the S6 to flash the WeMos D1 Mini. The Arduino IDE can't access the S6 serial port unless the S6 is selected. This is on Windows 8.1, Linux might very well work probably due to th
|
No luck here getting the S6 to flash the WeMos D1 Mini. The Arduino IDE can't access the S6 serial port unless the S6 is selected. This is on Windows 8.1, Linux might very well work probably due to th
|
By
Howard Dutton
· #23074
·
|
|
new FYSETC S6 build
There are four "serial ports" available in our design AFAIK. The one on USB (strictly virtual.) Serial. SerialA (command channel.) The one on the UART1 (RX1/TX1) header. Serial1. SerialB. The one on t
|
There are four "serial ports" available in our design AFAIK. The one on USB (strictly virtual.) Serial. SerialA (command channel.) The one on the UART1 (RX1/TX1) header. Serial1. SerialB. The one on t
|
By
Howard Dutton
· #23069
·
Edited
|
|
new FYSETC S6 build
Perhaps I'll add time-stamping to the debug logs too... On Linux, one could easily pipe the serial data into a file as a running log of each nights operations.
|
Perhaps I'll add time-stamping to the debug logs too... On Linux, one could easily pipe the serial data into a file as a running log of each nights operations.
|
By
Howard Dutton
· #23067
·
|
|
Problem connecting to wemos d1 mini pro with android devices
Try this code (for Access Point only, wondering about the order of operations setting up the WiFi stack.) If it doesn't work remove the disconnect statements and try again. Then rearrange the order of
|
Try this code (for Access Point only, wondering about the order of operations setting up the WiFi stack.) If it doesn't work remove the disconnect statements and try again. Then rearrange the order of
|
By
Howard Dutton
· #23065
·
Edited
|
|
new FYSETC S6 build
One could, for example, roll an Arduino Nano etc. with OELD display that shows the last couple of error log messages. Or, on a Teensy you can do 3x serial interfaces on a single USB port so #3 can get
|
One could, for example, roll an Arduino Nano etc. with OELD display that shows the last couple of error log messages. Or, on a Teensy you can do 3x serial interfaces on a single USB port so #3 can get
|
By
Howard Dutton
· #23063
·
|
|
new FYSETC S6 build
It would corrupt the communication exchanges on that channel. DEBUG output can also be attached to any Serial interface, it doesn't need to be associated with a command channel.
|
It would corrupt the communication exchanges on that channel. DEBUG output can also be attached to any Serial interface, it doesn't need to be associated with a command channel.
|
By
Howard Dutton
· #23062
·
|
|
new FYSETC S6 build
That's right. It's in src/lib/TLS.h You'd have to intercept the read() and send it to DL(). Just make sure the GPS emits NMEA sentences, the baud rate is right, and it's wired in right (levels etc.) t
|
That's right. It's in src/lib/TLS.h You'd have to intercept the read() and send it to DL(). Just make sure the GPS emits NMEA sentences, the baud rate is right, and it's wired in right (levels etc.) t
|
By
Howard Dutton
· #23061
·
|
|
new FYSETC S6 build
Naturally you don't want DEBUG enabled on a command channel you are actually connecting to with anything (like the ASCOM driver.) This is for you, not control software.
|
Naturally you don't want DEBUG enabled on a command channel you are actually connecting to with anything (like the ASCOM driver.) This is for you, not control software.
|
By
Howard Dutton
· #23059
·
|
|
new FYSETC S6 build
This DEBUG mode and its options is really a new thing. Mostly the it logs errors. No errors nothing is shown but that will possibly change (for VERBOSE anyway.) With ON or VERBOSE you see NV and parki
|
This DEBUG mode and its options is really a new thing. Mostly the it logs errors. No errors nothing is shown but that will possibly change (for VERBOSE anyway.) With ON or VERBOSE you see NV and parki
|
By
Howard Dutton
· #23058
·
|
