Date   

Re: The MaxPCB version 3

Butchf
 

That's a good price and most of the work is done.  would you buy them and become a source for the PCB's? if so I'll buy one.

Don


Re: Failed to init device yet again

Khalid Baheyeldin
 

As Martin Bonfiore says:
I am not sure of the logistic difficulties or whether you would consider it but have you thought of mailing the problem STM32 to someone in the group who has lots of experience and success in getting Onsteps to work?  I am sure curious (as I suspect others on the forum) about what is going on.  So...maybe someone would volunteer to receive it (maybe ideally in your home country) and test it...if this is something you are interested in and have the resources.  Just a thought.....
I can attempt troubleshooting a couple of non-working STM32 to see what the issue is, provided costs of shipping to and from Canada are covered, which may be prohibitive (~ US$14 or so each way). Although I use Linux only, if I can make them work, Dave Schwartz lives nearby and can further test on Windows to make sure there there are no Windows-specific issues.

Not sure any of that is practical, but willing to spend some time on this.


Re: Failed to init device yet again

Martin Bonfiore
 

I am not sure of the logistic difficulties or whether you would consider it but have you thought of mailing the problem STM32 to someone in the group who has lots of experience and success in getting Onsteps to work?  I am sure curious (as I suspect others on the forum) about what is going on.  So...maybe someone would volunteer to receive it (maybe ideally in your home country) and test it...if this is something you are interested in and have the resources.  Just a thought.....


Re: Converting Black HEQ5

Khalid Baheyeldin
 

I don't know why an STM32 would not "play nice" with Astroberry/Pi, while the MiniPCB2 would.
There should be no difference apart from the max slewing speed (when no microsteps slewing or pulse is used).

Can you elaborate?


The MaxPCB version 3

Howard Dutton
 
Edited

I've had this unreleased update of the MaxPCB2 working for a while now.  The MaxPCB3 adds the ability to flash the WeMos D1 Mini through the Teensy and support for only SPI stepper drivers (TMC2130 and TMC5160) in all four sockets.  This limits it to just those TMC drivers but in doing so also does away with soldering all those pin-headers under the focuser/rotator stepper drivers for easier assembly.  And naturally it's a lot nicer to be able to set the current on all stepper drivers (focuser/rotator included) in software.  This design has been on my bench for months and has worked perfectly well.

Recently though I looked into JCL PCB assembly services and using some surface mount components to make assembly easier and make costs lower (in quantity anyway.)  Here's what that looks like...



The PCB cost for me is $49.03 delivered from EasyEDA/JCL for Qty 5 with all SMT devices installed (DHL for shipping so it could be a bit less.)  Most other parts (through hole) are EasyEDA/LCSC and cost for those is $24.12 delivered (for Qty 5 builds and USPS shipping.)  Order this stuff in Qty 10 or 20 and the costs go way down.

So < $15 each + the other parts needed below.

Other stuff needed:
  • Teensy3.5 or 3.6
  • DS3231 RTC
  • WeMos D1 Mini
  • Set of four TMC2130's
  • Voltage regulators (OKI78SR5 and optionally OKI78SR12, or eBay work-alikes)
  • Speaker
  • 2x RJ22 jacks for the focusers/rotator (LCSC doesn't have suitable RJ22's)
  • The usual DIY'ers 0.1" pin headers, socket headers, and shunts
  • The aluminum box this was designed for


Re: Converting Black HEQ5

Jason
 

Here is version 2.0.  1.0 was a STM32 build but it didn't play nice with astroberry/pi so for 2.0 I switched to minipcb2. Still in alpha stages but operating.
Pulley's are 60t and 16t.  The 60t 20t combo seamed to cause stalling when the scope was perpendicular with the horizon, this is more likely a balance issue at the time.  The 60t pulley needs to have the bore drilled out to 9mm.  I did this with a drill bit and a drill press.  Not exactly perfect as the pulley wobble some during operation but that can be fixed later.  

The belt sizes used are 180mm for DEC and 172mm for RA.  All are GT2 belts and pulleys.

 

Onstep is mounted to the side of the mount in an aluminum enclosure.  Secured with command velcro strips.



Here you can see the pi4 mounting via zip ties under the scope.


And the Onstep mounted down low here.  A quick note make sure to tin the ends of the stepper drives if you plan on using the screw in terminals.  I didn't at first and they could easily come out during operation causing some serious wtf moments for a couple to test runs.



Future plans.  Move up to a PCBMax for added stepper drivers like focus and rotator for a filter wheel.  I've decided that having the electronics in mount is not as important and having as much controls as possible in a single package.  Also to build a housing for the integration of pi/onstep/power distribution like the eagle from primaluc labs. Which will also be mounted on top of the scope and limit the amount of wiring need.  Hopefully only one wire to the ground for power and two to the mount steppers.  But that's the up date for now.  I did get some captures of M20 but I haven't processed them yet and for some reason ekos/indi wont go beyond 30 second exposures.  I'm sure it's something I'm not setting right on the camera or in ekos/indi.  Got a lot to learn on that front.


Re: CGE Pro New Conversion to first light

Curly
 

Shhh George, I’ve borrowed some of the pans to boil and seal the parts too!!

Curly 

On Tue, 4 Aug 2020 at 23:27, <stm32bluepill@...> wrote:
You can use the tube, but the wife'll kill you!

Another link:
USB NEO-7M NEO-8M 


Re: New FYSETC S6 replacement build

Dave Schwartz
 

Not a problem, John.

I am sorry (but encouraged) that you had the same problem with the TMC_SPI setting for the driver status. That means the issue is not unique to me and is repeatable... that's always the first step to solving an issue.

Howard, any thoughts of how we can proceed to debug this issue? Would this be amenable to the verbose debugging option?


On August 5, 2020 12:04:08 a.m. EDT, John Petterson <j.petterson@...> wrote:

Sorry Dave.  I did not understand the linkage of that answer - now I do.  My fault for not reading it carefully. 

I tried setting that parameter and I had the same experience you did.  No way to move the motors although the autostart on the tracking did work.

John


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: New FYSETC S6 replacement build

John Petterson
 

Sorry Dave.  I did not understand the linkage of that answer - now I do.  My fault for not reading it carefully. 

I tried setting that parameter and I had the same experience you did.  No way to move the motors although the autostart on the tracking did work.

John


Re: Failed to init device yet again

Mike Ahner
 

On Tue, Aug 4, 2020 at 02:28 PM, Egge wrote:
COM-Port was COM7
Hi Eggie, I know I'm a little late and I imagine you've tested many things. But I wonder if you are certain to have the correct COM port? Windows can be troublesome around comm ports, it's just a thought. If you open the device manager and expand the Ports (COM & LTP) option, you can watch the COM ports appear and disappear as you power on/off the STM32.

Meanwhile,  suppose you'll soon have an answer with a new STM32.

Good luck!


Re: New FYSETC S6 replacement build

Dave Schwartz
 

You were asking about setting DRIVER_STATUS to TMC_SPI. I responded that it hadn't worked for me. Howard asked about the MISO wiring on the S6.

??? I can't reply to a question in the same thread in which it was asked ???

On 2020-08-04 9:31 p.m., John Petterson wrote:
Dave,  Wrong thread???

John


Re: Configuring Wemos Mini problem

Khalid Baheyeldin
 

On Tue, Aug 4, 2020 at 09:35 PM, Jas wrote:
Howard and Dave,
I had NOT placed it back on the board.  I will do so.  I don't think that specific instruction is there in the Wiki.  But now I know.

Do you think going to the OnStep Ver 4 may solve the problem of the Wifi Addon not finding the Teensy?
No need to go to version 4.x.
OnStep 3.16 is the stable version.

Just power off OnStep, and replace the module carefully, so all pins are in the correct place.
Then reboot.


Re: Configuring Wemos Mini problem

Jas
 

Khalid,
I was using Ver 2.6.2 because I thought that I read somewhere in the Wiki that was the version too use.  I have updated the ESP8266 Boards Manager to 2.7.2.  

Howard and Dave,
I had NOT placed it back on the board.  I will do so.  I don't think that specific instruction is there in the Wiki.  But now I know.

Do you think going to the OnStep Ver 4 may solve the problem of the Wifi Addon not finding the Teensy?

Thank you for all the advise.

Jas


Re: New FYSETC S6 replacement build

John Petterson
 

Dave,  Wrong thread???

John


Re: New FYSETC S6 replacement build

Dave Schwartz
 

It appears to be wired correctly.

Using Altium Designer viewer I can see that PA6 (pin 31 of the STM32F466 in its LQFP100 packaging) is connected to the bottom left of the 12-pin header block under each driver. The net is even named MISO. In the SPI driver configuration of the jumpers on that block (connecting the bottom and center pins, column-wise), that will connect it to the SDO pin of the driver. Pretty sure that's the correct pin on the driver because PA7 (pin 32 on the LQFP100, net name MOSI) is connected to SDI on the driver sockets and it sure looks like OnStep's SPI instructions to the driver are working because the tracking, slewing and power control seem to be working well.

On 2020-08-04 6:47 p.m., Howard Dutton wrote:
I've used FYSETC 2130's (v.1.1) they are just TMC2130's.  Wonder if the SPI MISO is right on the S6?


Re: New FYSETC S6 replacement build

John Petterson
 

Slew rate 3  and microsteps slew off causes immediate stall, setting to 0.75x  sometimes causes stall after 1st motor stops, setting to 0.5x lets it work.

I am starting to suspect these motors are a big part of the problem.  I have a pair of 200 step motors (56 oz. in. 1.7A) that I simply plugged in to see how they work.  Without changing the step rate, these run at normal slew speed at 3 degrees (meaning 6 degrees/second, twice the RPM of the others) as well as at 1.5x that speed.  I am certainly going to use these on my AZ8 as I do not need the additional tracking accuracy the 400 step motors would provide for a mount that I plan to use for visual only.

Now I need to check the motors that are on the GM8 today to see how they will work with this controller.  And perhaps look for a different set of 400 step motors.

John


Re: New FYSETC S6 replacement build

Howard Dutton
 
Edited

On Tue, Aug 4, 2020 at 03:20 PM, Dave Schwartz wrote:
You can try. For me, with FYSTEC TMC2130 V1.2's this results in an immediate 'Motor/driver fault' detection and it cannot be convinced to move the axes. Maybe its just me.
I've used FYSETC 2130's (v.1.1) they are just TMC2130's.  Wonder if the SPI MISO is right on the S6?



Re: CGE Pro New Conversion to first light

George Cushing
 

You can use the tube, but the wife'll kill you!

Another link:
USB NEO-7M NEO-8M 


Re: New FYSETC S6 replacement build

Dave Schwartz
 

You can try. For me, with FYSTEC TMC2130 V1.2's this results in an immediate 'Motor/driver fault' detection and it cannot be convinced to move the axes. Maybe its just me.

On 2020-08-04 6:09 p.m., John Petterson wrote:
I noticed the AXISn_DRIVER_STATUS definition has a value TMC_SPI. Do I need to set that for these two axis?

John


Re: Configuring Wemos Mini problem

Dave Schwartz
 

Have you put the WeMos back into your MiniPCB and powered the whole thing as a unit? The WiFi software doesn't reset the SSID to ONSTEP until it can connect to the controller software (at which time the LED also stops flashing and becomes constant).

On 2020-08-04 5:06 p.m., Jas wrote:
I have been trying to upload the wifi sketch on to the Wemos Mini.  I removed it from the MiniPCB2, connected it to the PC (Com 5) and ran the upload.  Everything appears to go well but on checking for the Onstep SSID, I do not find it.  Instead I find a different SSID: ESP-455D1E.  I have done the "Erase Flash  "All contents" and still get this.  Initially I got a different SSID: "Farylink_455D1E" , but that was before the Erase...  Also, I have not changed any of the parameters in the sketches.  The IP address shown on connecting to this wifi is 192.168.4.2 and the MAC address is: 32:40:8d:75:b2:72 which is different from the MAC address reported below.

This is what I get on uploading the sketch:

Executable segment sizes:
IROM   : 329692          - code in flash         (default or ICACHE_FLASH_ATTR)
IRAM   : 27628   / 32768 - code in IRAM (ICACHE_RAM_ATTR, ISRs...)
DATA   : 1480  )         - initialized variables (global, static) in RAM/HEAP
RODATA : 6240  ) / 81920 - constants             (global, static) in RAM/HEAP
BSS    : 26248 )         - zeroed variables      (global, static) in RAM/HEAP
Sketch uses 365040 bytes (34%) of program storage space. Maximum is 1044464 bytes.
Global variables use 33968 bytes (41%) of dynamic memory, leaving 47952 bytes for local variables. Maximum is 81920 bytes.
esptool.py v2.8
Serial port COM5
Connecting....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: 48:3f:da:45:5d:1e
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Erasing flash (this may take a while)...
Chip erase completed successfully in 7.9s
Compressed 369200 bytes to 252229...
Wrote 369200 bytes (252229 compressed) at 0x00000000 in 5.7 seconds (effective 521.8 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...


What am I doing wrong?
Thank you for the help.
Jas