Bad radio?

Post Reply
portney
Posts: 5
Joined: Fri Jan 08, 2016 9:10 pm
Location: Blacksburg, Virginia, USA

Bad radio?

Post by portney »

New to the forum, and new to scratch built quads. I am working on a 250, and have managed to set things up with a multiwii se v2.5 flight controller board, have successfully uploaded a script, and have been able to 'see' what's going on via the conf display.

my problem is that i am unable to arm the board. i have read through the posts dealing with 'board won't arm' and one of the suggestions was to hook in the ftdi to check what values the board is 'seeing'. i think that my board is seeing values very close to 1500 (1484, for instance) no matter what the stick positions are, and therefore the board will not arm, no matter how much i try to adjust the signal limits in the transmitter...

the receiver(FS R9B) is, i think, correctly bound to the transmitter (FS TH9X), as i have a solid red light in the receiver.

also, i have tried several different sketch settings, including setting the board to #define MultiWii_32U4_SE, as well as the one suggested by Painless360, the #define CRIUS_SE_v2_0...

To be honest, i can say i have learned a lot, and i think that i am getting close, but at this point, i am really stumped...

:? :? :?

Kbev5709
Posts: 451
Joined: Mon Aug 17, 2015 5:56 pm

Re: Bad radio?

Post by Kbev5709 »

portney wrote: i think that my board is seeing values very close to 1500 (1484, for instance) no matter what the stick positions are, and therefore the board will not arm, no matter how much i try to adjust the signal limits in the transmitter...
:? :? :?

If your stick movements are not being reflected in the conf, but the TX and RX are bound, your TX is most likely not set up properly. If moving your FC makes the sensors work as reflected in the conf or GUI but moving the sticks does nothing, the first thing I would check is if my TX is set up on FM-PCM or FM-PPM. You do this in system settings menu in the "mode sele" submenu. You want it set up on FM-PPM. That RX is just like my RX and I know it is a PPM. A PCM RX can be bound to the TX as well so they give you the option of using a more expensive and higher end PCM RX.
That radio is just like my Turnigy 9x. There are two more menu's that you need to work with. Endpoints and subtrims. First and formost, center up your trim switches next to and below your gimbals. They emit a longer beep when you reach the center. Now, go into your subtrim menu and center up (it lets you change the settings) your sticks so they all come in as close as possible to 1500. Then go into the endpoints menu and adjust low end points to 1000 and high endpoints to 2000. Go back and check that the mid point hasn't changed. If it did, readjust and go recheck the endpoints. Going back and rechecking after a change is just what you have to do to get it right. Do this until you get your subtrim at 1500 and endpoints at 1000 and 2000 (or as close to those as possible.) These are actually the very first steps everyone needs to do before their fc will arm.
Then, make sure that in your config.h sketch that you have #define ALLOW_ARM_DISARM_VIA_TX_YAW enabled. Make sure your minspeed and mincommand are correct, and then you should be able to arm by taking the throttle stick down and right, and disarm down and left. If you don't know what your mincommand and minthrottle should be try 950 for mincommand and 1000 for minthrottle. Those settings work for mine. If you have one of the listed special ESC settings ESCs, use what it says to use in the config.h.
I really think you should look up your TX on some YouTube videos and you can probably get answers to any questions you might have about that TX's setup. If not that one then use a Turnigy 9x video. It's basically the same TX.
Also,you need to use the configurator or Win GUI when you are setting your endpoints and subtrims. Use the throttle, pitch, roll, yaw bars to get things right.
The TX has to be set to the FM-PPM setting to transmit on all eight rx inputs. If the TX is set up wrong it will bind with the RX but still not talk with it, so the very first step is making sure it is set to FM PPM.

portney
Posts: 5
Joined: Fri Jan 08, 2016 9:10 pm
Location: Blacksburg, Virginia, USA

Re: Bad radio?

Post by portney »

Thank you for the very detailed reply, and very helpful suggestions. i can tell you are not an 'armchair expert', and so i would like to have you work with me to solve this puzzle (as well as anyone else who might have some insight to the problem).

I am in PPM mode. I have noodled around on the web, and youtube, quite a bit, but much of the info on the Turnigy/Flysky Tx/Rx (I believe they are entirely equivalent) is unhelpful, a lot of it dealing with the 3way mode switch. That might be helpful at some point, but first things first. i just need to get the board to communicate with the transmitter!

i can't figure out how to do a screenshot, but here is what the configurator looks like when i am connected. the artificial horizon and compass work well.
i can't figure out how to do a screenshot, but here is what the configurator looks like when i am connected. the artificial horizon and compass work well.


this is what the board, connected to the receiver and the ftdi looks like
this is what the board, connected to the receiver and the ftdi looks like


Am I doing this correctly??

I have centered the trim tabs on the Tx

When I go into subtrim menu on the Tx, I can adjust the settings for a wide range, but nothing moves on the conf screen. As you can see, i am at 1486 on the thr, pit, and yaw, and 1484 on roll. they do not budge. Should they, when I move the sticks??

I have set the E.POINT for thr at various levels, from the default 100 to values lower and higher, as high as 120, with no perceptible change. BTW, I used this setup guide for the board (I'm on my 2nd board fried the first :cry: ) oh well, i can't upload a .pdf file - you can see it if you google 'HURC MultiWii SE'

Finally, the arm via yaw function is set in the script: #define ALLOW_ARM_DISARM_VIA_TX_YAW

Again, thanks for your help

Kbev5709
Posts: 451
Joined: Mon Aug 17, 2015 5:56 pm

Re: Bad radio?

Post by Kbev5709 »

Did you remove the bind plug after getting the RX to bind? I'm not seeing it in your photo so I assume you did. I can't tell from your pic where all the wires plug into your RX. From what I can see, it looks like your ground is plugged into one of your signal pins but i really can't tell for sure. I'm probably wrong on that but I really can't tell from that photo. What you want to do is supply power and ground from the FC to the battery terminals on the RX. I'm sure you can also power it from any of the + and - pins on the RX. As long as you can get it to light up red and bound you have the power going in ok.

Also more importantly, you want to plug the FTDI adapter into your UART pins on the FC board in order to program. I think the pins you are plugged into now on the board are FTDI out. Try using only the +, the -, RX and TX on the adapter board and the FC board. Reverse RX so it goes to TX and TX so it goes to RX (from one device to the other.) Do not hook up either the 3.3v or the DTR pins. The reason I am suggesting this is because what you have plugged in is known as an FTDI to UART adapter. They plug into a serial port which is what your UART pins are. I believe you will see your stick moves on the GUI after correcting this minor error. Hopefully all of the pins on your FC are labeled. The other four pins north of the FTDI pins on your FC board is the UART.
Last edited by Kbev5709 on Sat Jan 09, 2016 6:10 pm, edited 9 times in total.

Kbev5709
Posts: 451
Joined: Mon Aug 17, 2015 5:56 pm

Re: Bad radio?

Post by Kbev5709 »

portney wrote:I am in PPM mode. I have noodled around on the web, and youtube, quite a bit, but much of the info on the Turnigy/Flysky Tx/Rx (I believe they are entirely equivalent) is unhelpful, a lot of it dealing with the 3way mode switch. That might be helpful at some point, but first things first. i just need to get the board to communicate with the transmitter!

Yep. You will be needing to set up that 3 way switch to get your different flight modes. Acro is kind of hard to fly in if you are a complete beginner. You might want to start off in angle or horizon. To do that there will be more stick moves to learn.

portney
Posts: 5
Joined: Fri Jan 08, 2016 9:10 pm
Location: Blacksburg, Virginia, USA

Re: Bad radio?

Post by portney »

very interesting, in that every vid i have watched involving the FTDI has shown the device being used as a bridge between the 6 "FTDI" pins on the board and the computer via old version usb connector.

so when I connect tbe FTDI as you suggest, i get a compiler error!

Arduino: 1.6.7 (Windows 8.1), Board: "Arduino Pro or Pro Mini, ATmega328 (5V, 16 MHz)"

C:\Program Files (x86)\Arduino\arduino-builder -dump-prefs -logger=machine -hardware "C:\Program Files (x86)\Arduino\hardware" -tools "C:\Program Files (x86)\Arduino\tools-builder" -tools "C:\Program Files (x86)\Arduino\hardware\tools\avr" -built-in-libraries "C:\Program Files (x86)\Arduino\libraries" -libraries "C:\Users\David\Documents\Arduino\libraries" -fqbn=arduino:avr:pro:cpu=16MHzatmega328 -ide-version=10607 -build-path "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp" -warnings=none -prefs=build.warn_data_percentage=75 -verbose "C:\Users\David\Desktop\MultiWii_2_4\MultiWii\MultiWii.ino"
C:\Program Files (x86)\Arduino\arduino-builder -compile -logger=machine -hardware "C:\Program Files (x86)\Arduino\hardware" -tools "C:\Program Files (x86)\Arduino\tools-builder" -tools "C:\Program Files (x86)\Arduino\hardware\tools\avr" -built-in-libraries "C:\Program Files (x86)\Arduino\libraries" -libraries "C:\Users\David\Documents\Arduino\libraries" -fqbn=arduino:avr:pro:cpu=16MHzatmega328 -ide-version=10607 -build-path "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp" -warnings=none -prefs=build.warn_data_percentage=75 -verbose "C:\Users\David\Desktop\MultiWii_2_4\MultiWii\MultiWii.ino"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.ino.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Alarms.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\EEPROM.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\GPS.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\IMU.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\LCD.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.ino.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Output.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Protocol.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\RX.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Sensors.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Serial.cpp" -o "nul"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.ino.cpp" -o "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\preproc\ctags_target_for_gcc_minus_e.cpp"
"C:\Program Files (x86)\Arduino\tools-builder\ctags\5.8-arduino5/ctags" -u --language-force=c++ -f - --c++-kinds=svpf --fields=KSTtzns --line-directives "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\preproc\ctags_target_for_gcc_minus_e.cpp"
Using previously compiled file: C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Alarms.cpp.o
Using previously compiled file: C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\EEPROM.cpp.o
Using previously compiled file: C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\GPS.cpp.o
Using previously compiled file: C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\IMU.cpp.o
Using previously compiled file: C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\LCD.cpp.o
Using previously compiled file: C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.cpp.o
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -MMD -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.ino.cpp" -o "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\MultiWii.ino.cpp.o"
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -MMD -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10607 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino" "-IC:\Program Files (x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs" "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Output.cpp" -o "C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Output.cpp.o"
C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Output.cpp: In function 'void initOutput()':

Output.cpp:688: error: 'MINCOMMAND' was not declared in this scope

writeAllMotors(MINCOMMAND);

^

C:\Users\David\AppData\Local\Temp\buildc44a809ba71843eda3f67f5c83c29855.tmp\sketch\Output.cpp: In function 'void mixTable()':

Output.cpp:1575: error: 'MINCOMMAND' was not declared in this scope

motor[i] = MINCOMMAND;

^

exit status 1
'MINCOMMAND' was not declared in this scope

Kbev5709
Posts: 451
Joined: Mon Aug 17, 2015 5:56 pm

Re: Bad radio?

Post by Kbev5709 »

Yow! Do you have all of your arduino libraries unzipped???? At least it tried to communicate. It saw your board. Why were you trying to upload another sketch? You should be checking to see if the sticks are showing up in the conf when it's hooked up the way I suggested.

portney
Posts: 5
Joined: Fri Jan 08, 2016 9:10 pm
Location: Blacksburg, Virginia, USA

Re: Bad radio?

Post by portney »

I guess I got ahead of myself yes i checked to see whether the multiwiiconf display showed any action with the tx inputs - still no go. i was trying to go back to the settings that painless 360 used in the youtube vid, as i had been experimenting with some others

i guess i need to hook up the ftdi to the ftdi pins on the board for uploading a sketch, and switch them for viewing the multiwiiconf display? i am not understanding this very well, but i do feel that i am learning, slowly, and perhaps making some progress.

at anyrate, when i had the ftdi plugged in to the 6 pins, i was able to compile and upload my sketches!

Kbev5709
Posts: 451
Joined: Mon Aug 17, 2015 5:56 pm

Re: Bad radio?

Post by Kbev5709 »

Ok, i'm just as lost as you. I am obviously barking up the wrong tree here, so by all means, use what method works to upload.
I actually used Painless360's vids myself to get everything up and running when i first started. I think I'm going to have to bow out here because I am not an expert on the 328P boards, with all of my knowledge based on the Mega atmega2560 boards. They use a direct usb plug in to program. The only thing I need to use my FTDI adapter for is setting up baud speed and other settings on my bluetooth using AT commands. When I hook up my FTDI to my serial 0 (my UART) I can see everything working in the conf. When I tried to upload a sketch, it wouldn't finish the upload. I tried.

portney
Posts: 5
Joined: Fri Jan 08, 2016 9:10 pm
Location: Blacksburg, Virginia, USA

Re: Bad radio?

Post by portney »

thanks for trying :( :( :(

i am going to go thru your other posts, as i note that you seem to have been involved in more than one case like mine

:D :D :D

Kbev5709
Posts: 451
Joined: Mon Aug 17, 2015 5:56 pm

Re: Bad radio?

Post by Kbev5709 »

portney wrote:i am going to go thru your other posts, as i note that you seem to have been involved in more than one case like mine
:D :D :D

I only get in on a few 328p related things. If I think I can help I try to. Most of my posts are probably related to GPS and mega boards though.

Post Reply