Howdy all,

I've been using the great diagrams that Oscar has provided such as this one here:

http://blog.oscarliang.net/ctt/uploads/2...setup1.jpg

Now I am working with the SPRacingF3 Mini on a build and was wondering if anyone have a sketch or even words on where to hook up the

1.  RX/TX for the OSD

2. Buzzer

3. Vbat measurement should be handled by the main power pins per the docs


I have read the docs for the board and have a good idea, but it would be great to validate that with someone who has already done it!

Thanks,

Bill

(08-Mar-2016, 05:33 PM)kelleysislander Wrote: Howdy all,

I've been using the great diagrams that Oscar has provided such as this one here:

http://blog.oscarliang.net/ctt/uploads/2...setup1.jpg

Now I am working with the SPRacingF3 Mini on a build and was wondering if anyone have a sketch or even words on where to hook up the

1.  RX/TX for the OSD

2. Buzzer

3. Vbat measurement should be handled by the main power pins per the docs


I have read the docs for the board and have a good idea, but it would be great to validate that with someone who has already done it!

Thanks,

Bill

Hi Bill,

Perhaps this may help you.

http://postimg.org/image/szc8v0hcd/

(08-Mar-2016, 11:00 PM)BigglesFPV Wrote: Hi Bill,

Perhaps this may help you.

http://postimg.org/image/szc8v0hcd/

Hi,

Thank you very much for that!@@ 

Yep, I studied that in the docs and it pretty much explains it...

I was looking for a "Fisher-Price" type of a diagram with the big bright colored lines like Oscar's illustrations LOL!@@

Thanks again...

Cheers,

Bill

OK, so using the docs as I interpreted them from the SPRacing Mini Docs, using a Spektrum Satellite, I soldered the pins onto the board as in the pic here: SPRacingF3 Mini with soldered pins

At the top, the red and black pins are the main Voltage in

the green/yellow pins on the right side are the UART1 pins 5 & 6 for the OSD Rx/Tx,

and the bottom red & black pins are the buzzer

the 2 black wires are the bootloader pads to be shorted for DFU mode for flashing the firmware


The docs say that UART3 can be used for the OSD Rx/Tx, but the Spektrum satellite conflicts with the R3 port there, so UART1, pins 5 & 6 is where I soldered the OSD pins

Would someone be a a "second set of eyeballs" and kindly take a look and validate if my interpretation is correct or not???

Once I nail this down I will then post the pic as an aid to others using this board.

Thanks,

Bill

IMO you are ok with what you have done.
Please check with a multimeter if there are short circuits anywhere.

Personally i probably won't use 2 wires to bridge the bootpads. A screwdriver would do the job too and you are not risking having leads flapping around.
I guess the reason for soldering wires is to be able to get into the bootloader when everything is mounted? Perhaps you can use a small push button switch there.

(09-Mar-2016, 06:05 PM)Luc Wrote: IMO you are ok with what you have done.
Please check with a multimeter if there are short circuits anywhere.

Personally i probably won't use 2 wires to bridge the bootpads. A screwdriver would do the job too and you are not risking having leads flapping around.
I guess the reason for soldering wires is to be able to get into the bootloader when everything is mounted? Perhaps you can use a small push button switch there.

Hi Luc,

Thanks for that!@@

Yep, the 2 wires are there ready for flashing, then the plans are to shrink wrap them but leave them there for flashing later w/o disassembly, etc, as you mentioned. 

I do have a micro switch and may install that, but the tradeoff is that it is just something extra needing to be secured.  For as often as I plan on flashing either way will work.

Thanks again...

Cheers,

Bill

Well, I got the FW flashed OK, but now cannot get a COM port with the STM32102 drivers on Win 7 64.

Always getting unknown device in device manager, despite reinstalling, restarting, swapping cables, etc...

Stopped for now..., I may abandon this board after some more troubleshooting on a different PC. The Acro and Full SPRacingF3 boards all connect fineto the same PC, but they use the VCP drivers.

If anyone has any ideas I would greatly appreciate them

Thanks,

Bill

You got cleanflight flashed, but cannot connect properly to your PC? Sounds strange...
Maybe you permanently stuck in bootloader mode? please check, if your soldering on the bootloader pads is ok. Perhaps you have accidently make a permanent joint there.

Yeah, very strange indeed...

The image link above in an earlier post leads to an image big enough that you can zoom in on and see the 2 separate pads...

Thanks for the reply

Cheers,

Bill

Soldering cannot be checked by watching an image, you have to measure it
Other than that i have no idea what the problem could be, sorry

(10-Mar-2016, 03:13 AM)Luc Wrote: Soldering cannot be checked by watching an image, you have to measure it
Other than that i have no idea what the problem could be, sorry

Yeah, I would not know what value to look for in measuring across the bootloader pads, but visually in person under a magnifying glass the pads are separate.

I've handed it to a friend to see if they have any success.  At the least I have the transponder part of it.  Switching back to the original boards which do not require the same drivers.

My device manager is always telling me that the drivers are not installed, but of course I have just installed them and restarted the PC,so perhaps someone else's PC may have a different result...

Thanks for trying to help.  I will report the result here...

CHeers,

Bill

Well, all is well with the board after all...

I handed it to a friend who then tried to connect the board with his PC; he was able to do that, so my PC appears to be the culprit...

The flashing I was able to do worked just fine as he connected it straightaway to CF...

Anyways, I just wanted to report that and say "case closed".

Thank you all for the replies!@@

Cheers,

Bill

I got it to connect to my PC successfully so I'm posting this to share...

I was searching and put in "STM32 no driver found error" and it led to a post that was the inspiration to keeping the device plugged into the USB port of the PC during the installation. Without the driver you get the not found error when you click into the driver properties on the STM32 device's entry in Device Manager; that's where you see the error message whose partial text I searched for.

1. Connect the device to the PC. Instead of that nice little ding sound when you connect a device, you'll get a subdued double ding kind of sound.

2. Install the driver. In my case I found version 1.3.1 from that post. I haven't tried re-instlling with version 1.4.0 that is linked to on the CF Configurator's main screen.

Anyways, about halfway through the installation process I heard that new device connecting dinging sound then saw that Device manager showed STM Electronics... on COM7 under the Com/Lpt port node.

Note: This is in conflict with the SPRacingF3 Mini's docs that advises you to disconnect the board from the PC, then to install the driver. I tried that first, with no success...

(10-Mar-2016, 03:03 AM)kelleysislander Wrote: Yeah, very strange indeed...

The image link above in an earlier post leads to an image big enough that you can zoom in on and see the 2 separate pads...

I know you got it all working in the end, but when I look at your image:

   

I can see a resistor that should be there to the right of the boot pads is missing. Here's what it looks like on my board:

   

Without a circuit diagram to look at, I can't say what the effect of not having that resistor might be...

Oh, and hello everyone, nice forum you have here!