Date   

Re: new FYSETC S6 build

Markus Kempf
 

Howard,

just tried it with this little change to the Pins.Ramps14.h file:

#define LEDnegPin            13 \\Aux0 = 11

and it works beautifully and does no harm. It lights up the little blue LED. Would be nice to have this in the config.h as an option (eg. EnablePCBStatusLed = ON changes Aux0 to 13). It could even be in parallel to the regular Aux0 pin (11) with some code changes.

Markus

Am 14/07/2020 um 13:27 schrieb Howard Dutton:

On Tue, Jul 14, 2020 at 04:14 AM, Markus Kempf wrote:
Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED
Not something I want to get into.


Re: OnStep + ESP32 (WemosD2R32) + Motor Shield V3 + Wii Nunchuk

chris
 

Oh NOOOOOOOOOOO. after several Months waiting and several hours trying to understand why the program would not compile I have realized they have sent the incorrect board. they have sent a Wemos D1R2 not a D1R32.  AGGGGGGHHHHHHHHHHHHHHHHHHHGGG.


Re: stand alone operation

Howard Dutton
 

On Tue, Jul 14, 2020 at 04:35 AM, <gsmclean2@...> wrote:
I will go back an look at my scratching of this connection. The location shown in the picture is unclear to me
Without cutting that trace on the Teensy the MiniPCB2 will "power up" with just the USB plugged in (5V and 3.3V become available but the motors will no run.)  I.e. you will see the power LED light.

Either way, trace cut or not, plugging into the coaxial DC connector should power up (again that power LED will light.)


Re: stand alone operation

Gary McLean
 

I will go back an look at my scratching of this connection. The location shown in the picture is unclear to me.
I was thinking the same and have gone back to that connection a number of times. Will head that way again.
Thanks Howard for all of your great work.
Gary
 


Re: new FYSETC S6 build

Howard Dutton
 
Edited

On Tue, Jul 14, 2020 at 04:27 AM, Howard Dutton wrote:
On Tue, Jul 14, 2020 at 04:14 AM, Markus Kempf wrote:
Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED
Not something I want to get into.
The heater outputs are supported in OnStep as auxiliary features, dew heaters, switching EL panels for flats, etc.
Mapping status LED's over that is not the way to go.


Re: new FYSETC S6 build

Howard Dutton
 

On Tue, Jul 14, 2020 at 04:14 AM, Markus Kempf wrote:
Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED
Not something I want to get into.


Re: stand alone operation

Howard Dutton
 
Edited

On Tue, Jul 14, 2020 at 04:23 AM, <gsmclean2@...> wrote:
My MiniPCB2 requires both motor power connection and a usb to computer connection to power up.
Is this normal or have I missed something.
Should power up with just the coaxial DC connection.

Power from the USB into the Teensy should have been physically disconnected as instructed in the MiniPCB2 Wiki.


stand alone operation

Gary McLean
 

My MiniPCB2 requires both motor power connection and a usb to computer connection to power up.
Is this normal or have I missed something.  MiniPCB2 and SHC working. WIFI  working.
Thanks to all
Gary


Re: GPS compile error with MKS Gen L1

Markus Kempf
 

should be a 9600 baud device, but will try 4800 baud to be NMEA compliant.

Markus

Am 14/07/2020 um 13:06 schrieb Howard Dutton:

Is this a 9600 baud device?  Remember there is a setting for that too.


Re: new FYSETC S6 build

Markus Kempf
 

if nothing is connected to the heater or fan terminals, it should not matter if the FET's get switched but the LED will turn on (if I read the schematics right). Therefore it could be possible to use them for the OnStep status leds without having the need to solder a LED and a resistor. Same thing on the MKS GenL, that has also the D13 pin to switch the LED next to the power led to be used as a OnStep status LED. Just ideas if you can find the time...

Markus

Am 13/07/2020 um 11:54 schrieb Howard Dutton:

On Mon, Jul 13, 2020 at 01:05 AM, Markus Kempf wrote:
Btw. is it possible to switch the (BED/E0/E1/E2) LEDs in software? Would be nice if OnStep could use them.
Those are coupled to the heater MOSFET's.  When you use those to switch something, like a dew heater, the corresponding LED should turn on.


Re: GPS compile error with MKS Gen L1

Howard Dutton
 

Is this a 9600 baud device?  Remember there is a setting for that too.


Re: Problem connecting to wemos d1 mini pro with android devices

Howard Dutton
 

On Tue, Jul 14, 2020 at 02:39 AM, <schinos@...> wrote:
I will try what you suggested and report back.
I see you trying a bunch of things to solve a problem that you alone, AFAIK, have encountered.  This works for many users on many devices, the play store says my App is active on 1281 devices presently and I bet > 50% use WiFi.

The idea here is to start at the beginning.  Reset/clear everything.  OnStep and the phone you are trying to connect to.  Additionally, the master branch WiFi has new code that streamlines the connection process that some users trip over so you will be using new code.  Which is a good thing and a bad thing since release-3.16 is tried and true, just connecting can be a bit clumsy (you have to not automatically connect and wait for OnStep to come up beforehand.)


Re: Problem connecting to wemos d1 mini pro with android devices

Howard Dutton
 

On Tue, Jul 14, 2020 at 02:39 AM, <schinos@...> wrote:
I noted on the screenshot you attached that for Programmer you have "AVR ISP" but i have (as a default value) "AVRISP mkII".
A setting that is not used in this case.  Doesn't matter.


Re: Problem connecting to wemos d1 mini pro with android devices

schinos@...
 

Howard thank you for your immediate response!

I would like to clarify a little more on the matter: once i power up the MaxPCB, the blue led of wemos starts blinking and continues for about 30 - 40 seconds before it turns solid blue and stays that way throughout the whole operation until i power it off. I have never experience it to turn off or start blinking without me doing a restart or reset by button. This behavior has not changed even though i have configured the baud rate on both ONSTEP and WIFI to 115200.
I will try what you suggested and report back.
I noted on the screenshot you attached that for Programmer you have "AVR ISP" but i have (as a default value) "AVRISP mkII".
Would that play any role in general or more specifically on this matter?

Thank you again very much for your support, effort and time!

Konstantinos


Re: GPS compile error with MKS Gen L1

Markus Kempf
 

Howard,

thank you very much again for your restless efforts.

I have added

#define SERIAL_B_BAUD_DEFAULT         OFF

#define TIME_LOCATION_SOURCE          GPS

#define MEGA2560_ARDUINO_SERIAL_ON

#define SerialGPS Serial1

and it compiles flawlessly. I get a Last General (Background) Error: Time and Location not set but I expected this because the RC filter is still there and the reception indoors is minimal with this old module. The good news is that PPS is working with the GPS module. Without digging out my oscilloscope it's hard to say why the PPS signal of the DS3231  was good enough for the S6 but not the MKS GenL.

Markus


Am 13/07/2020 um 23:05 schrieb Howard Dutton:

On Mon, Jul 13, 2020 at 01:43 PM, Howard Dutton wrote:
I'm sure I could code around this issue, but I'm not going to since to do it properly would take serious time and effort and this is dated h/w.
Ok... went and thought about this for a moment and I changed my mind, there really is no problem and it should work.

Until recently it could perhaps cause timing jitter/performance issues (Mega2560) but that should no longer be the case with code improvements to GPS I recently added.  We turn on the Serial interface for just long enough to grab the data and turn it off again.  Provided Arduino handles that properly, and it's a good bet it does, this should work.

The compile error you see is a collision of the interrupt vector for my custom serial class vs. the Arduino built in class.  Turn off my built in class and no collision.

So if using Serial1 for GPS turn off SerialB, this is required anyway since you can't have a command channel tied to the GPS serial interface:

#define SERIAL_B_BAUD_DEFAULT         OFF //   9600, n. See (src/HAL/) for your MCU Serial port # etc.                        Option


Re: Wifi Add-on / WeMos D1 Mini

 

 Khalid Baheyeldin 

 

Yes am using  0.9 degree 4.4kg.cm motor with direct drive... not dare to use pulley, because am using over 10-15 kg payload equipment.
Just order two TMC5160 V1.2 USD 12.65 for ech, Go for the best... don't want worry so much for heat.
 
 


Re: Problem connecting to wemos d1 mini pro with android devices

Howard Dutton
 

On Mon, Jul 13, 2020 at 03:36 PM, Howard Dutton wrote:
WiFi Addon:  In its Config.h change no settings at all.  Then flash it into the WeMos D1 Mini.  Use the "LOLIN Wemos D1 and Mini" selection.  Change only the setting so it wipes all flash memory on upload.
Like this:


Re: Onstep and DIY GEM

tnut55
 

Yes, I have plans to add PEC and Home switches.  I think my guiding errors are a magnitude larger than PEC.  I need to sort out mechanical issues in the drives.

It was a bit of luck but I have done lots of guided imaging with dedicated cameras and other mounts, enough to know that getting all this to work together the first night would be challenging.  The Onstep part of the equation made it all easy.


On Mon, Jul 13, 2020 at 4:50 PM, Khalid Baheyeldin
<kbahey@...> wrote:
On Mon, Jul 13, 2020 at 04:30 PM, tnut55 wrote:
Night 2 was more challenging.  My goals were perhaps a little too ambitious.  I wanted to image with a DSLR, something I have never done.  I wanted to use PHD2, GPUSB and try guiding through the Onstep controller.  I've used PHD a couple years back but never PHD2 so that was a re-learn event in itself.  I had some difficulty getting a successful PHD2 calibration until I adjusted the calibration parameters.  As far as the GPUSB and Onstep controller, I had absolutely no issues.  Once I achieved a successful guide calibration, there were never any other issues.
You lucked out. I usually add only one component (or upgraded firmware/feature, ...) per session, and after it works well, I then add another.
Otherwise problems will be impossible to narrow down to a single cause.

As far as guiding, my mount still has a lot of issues that I need to track down and resolve.  I'll need to investigate everything to remove slop in the gear train.  In a nutshell, up to 60 secs, guiding did not appear necessary and given my heavily light polluted sky, I was not getting very good exposures above 1 or 2 minutes anyway.  The images produced were not spectacular and that was not the goal.  The goal was to see if I could get everything working together, check out mount performance and see where to go from here.
You can increase the time for unguided exposures by recording PEC 5 or 6 times and saving it. A PEC sensor is preferred, but you can record PEC every power up, and use autoguiding to do it. Also use refraction tracking. That may get you to 120 or 180 seconds. I have done that in the past.

Once again, thanks Howard for such a brilliant project.
Yes, it is so satisfying when things finally works.

And thanks for sharing your project. I added it to the showcase page.


Re: Problem connecting to wemos d1 mini pro with android devices

Howard Dutton
 

Download the latest master.

Use the ESP8266 libraries 2.4.2 or 2.7.2 in the board manager.

OnStep:  In its Config.h change no baud rate settings but configure for your device.  Then flash it.

WiFi Addon:  In its Config.h change no settings at all.  Then flash it into the WeMos D1 Mini.  Use the "LOLIN Wemos D1 and Mini" selection.  Change only the setting so it wipes all flash memory on upload.

Connect everything together.

Report on the WeMos D1 Mini blue led.  Does it flash and eventually turn solid blue?


Re: PPS on MKS Gen L1 does not work

Howard Dutton
 
Edited

On Mon, Jul 13, 2020 at 01:24 PM, Markus Kempf wrote:
I have connected the DS3231 PPS output to X+ (2) (Vcc/GND only) and nothing gets recognized. It worked nicely with the S6 board, same config.
I don't have a MKS Gen-L anything but I do have several Arduino Mega2560's...

Pulled out one of those.  Wired my DS3231 for +5V/Gnd and PPS to Pin 2 configured as usual (PINMAP MksGenL) and uploaded the latest master.

No issues: