(31-Mar-2016, 08:31 PM)Oscar Wrote: i can confirm pass through works

This makes me happy and NolaFPV your welcome   

Arggggg, Sorry to have say this but the buzzer pads are still not very good, Brand new board, first solder to buzzer pads and instantly fell off. LOL, Anyone know where I can pick up another Buzzer + trace.


Other than that, the board works fine.

The buzzer ground is the signal so if you just drop the + trace, lucky you, you can just grab any 5v source from anywhere else on the board.

(01-Apr-2016, 05:28 AM)BigglesFPV Wrote: Arggggg, Sorry to have say this but the buzzer pads are still not very good, Brand new board, first solder to buzzer pads and instantly fell off. LOL, Anyone know where I can pick up another Buzzer + trace.


Other than that, the board works fine.

yes my buzzer pads fell off too on my first board, replacement worked fine though.
the trick is to solder like lightening fast... i would recommend reporting it and sending FPVMOdel a picture

(01-Apr-2016, 09:13 AM)Oscar Wrote: yes my buzzer pads fell off too on my first board, replacement worked fine though.
the trick is to solder like lightening fast... i would recommend reporting it and sending FPVMOdel a picture

Sent Ally at FPVmodel a pic and a problem description

Someone can confirm that the telemetry working with x4r/d4r? (battery voltage is the most important to me)

(01-Apr-2016, 08:15 AM)Eddie Chong Wrote: The buzzer ground is the signal so if you just drop the + trace, lucky you, you can just grab any 5v source from anywhere else on the board.

Thanks Eddie.

Oscar, which print on motor input is correct? front or back? Also, are you going to do a write up on your blog with pictures and wiring diagrams? Thanks

(02-Apr-2016, 10:27 PM)Miguel Arr Wrote: Oscar, which print on motor input is correct? front or back? Also, are you going to do a write up on your blog with pictures and wiring diagrams? Thanks

I reported the mis-lable problem to FPVModel, they said they would check but never got back to me...
I would probably trust the label on the top (the face where the USB connector is) because there is LED label and it's not on the back

Finally installed the new V2 board and besides the buzzer pads falling off a new issue arose. When checked motor rotation in cleanflight, Motor 1 fires up when slider moved, Motor 2 fires up when slider moved, But..wait for it.. When you slide motor 3 tab up, both it and motor 4 busrt into life, same on Motor tab 4, motor 3 starts up.

Swapped boards to second V2 board and same problem, Put older V1 board in and worked perfectly. Hmmmm, Something not quite right with the V2 boards I received.

(03-Apr-2016, 12:58 AM)BigglesFPV Wrote: Finally installed the new V2 board and besides the buzzer pads falling off a new issue arose. When checked motor rotation in cleanflight, Motor 1 fires up when slider moved, Motor 2 fires up when slider moved, But..wait for it.. When you slide motor 3 tab up, both it and motor 4 busrt into life, same on Motor tab 4, motor 3 starts up.

Swapped boards to second V2 board and same problem, Put older V1 board in and worked perfectly.  Hmmmm, Something not quite right with the V2 boards I received.

check those pins are not shorted? I will test mine tomorrow and report back.

(03-Apr-2016, 01:15 AM)Oscar Wrote: check those pins are not shorted? I will test mine tomorrow and report back.

No visual signs through magnifying glass, solder joints nice and clean. Yeah, please let me know. We need to find out if it is a batch issues or a across the board issue. (no pun intended). My V1 boards have always worked fine.

I too am having all sorts of issues my V1 doesn't have. Worst is trying to read setup in BLheli. Was getting a can't connect  to ESC#1- und_power bal bla. Disconnected 5v going to FC and just powered through USB Plugged in Bat and BAAM! ESCs all there. I'm still quite a noob but I've set V2 up just like V1 Only adding Vbat... hmm that makes me wonder, perhaps I'll disconnect that.

Oh! I've got a second V2 I ordered sometime after the first. The first one I ordered the day they came back in stock the second a couple weeks later. Noticed when I ordered that one there was already an updated batch.

Update:
Swapped out with the other V2 I had. No issues with BLHeli passthrough now. Another issue was horrible wobbles with stock PIDs that got worse when lowering or raising P. Funny thing is they weren't showing up as osolations in blackbox either. That seems to have gone away but won't know for sure till tomorrow.

(29-Mar-2016, 04:07 PM)Twistyml Wrote: I would also like to know what these RSSI ports are for and is it possible to program the ESC's through this board?

The RSSI port is used to measure the radio signal. Some firmware allows you to have your copter automatically go into "Safe Mode" when the RSSI drops below a certain threshold (on the assumption you've lost control of it). Safe mode can be used for RTH (Return to Home) if you have GPS support, or to have the copter hover and slowly decrease the throttle (in an attempt to safely land it).

Well after all the fun I had figuring out my screws/motor windings problem I've got into tuning mode. The damn thing got stuck in a reboot cycle after putting it back to a 500 looptime (changed it during the troubleshooting). Now it won't connect to the configurator. It powers up, LEDs light up, the port it's on shows up and connects. Plug the other V2 in and it's just fine. So I've tryed to reflash but won't connect to bootloader on first click but will on second click and flashes. How ever it still won't connect to configurator. I've now swapped back to the other V2 and the quad is back and ready to tune when the rain goes away. Funny thing, now that it's out I can flash it on the first try every time... but still won't connect to configurator.

Update:
HA! the stories not over. This other V2 I've put back in as now reminded me of another issue I originally had but never mentioned. when I plug in the USB it acts like a battery has been plugged in. Low voltage alarm goes off. I've set it to 1 so I don't have to hear it. The voltage scaling is at default 110 which was correct for the other V2. Without the battery it's reading 1.5V and with it'll read anywhere from 1.5 to 10V. When unplugging it'll shoot up to as high as 10V then settle back down to 1.5V. Looks I'm going to have to set this up just like my V1 with a voltage divider straight into the Frsky smart port.

Another update:
Arg! BLHeli passthrough still won't read set up with this board. No error just comes back with the list of ESC and --- next to them. In Betaflight motor tab calibrating doesn't get past the initial plug in battery faze. Lowering master slider does nothing. Actually motor tab sliders won't control the motors at all.
Good news is that I've yet to lose my buzzer pads with all the soldering and desoldering. (insert thumbs up emoji)

Last update:
After walking away for a few hours I remembered that when I had forgotten to reconnect the 5V feeding the FC BLHeli worked. This time isn't nay different. Motors tab calibrated ESC fine and BLHeli read setup. Turned vbat back on and it works too.