{"action":"created","issue":{"url":"https://api.github.com/repos/betaflight/betaflight/issues/5314","repository_url":"https://api.github.com/repos/betaflight/betaflight","labels_url":"https://api.github.com/repos/betaflight/betaflight/issues/5314/labels{/name}","comments_url":"https://api.github.com/repos/betaflight/betaflight/issues/5314/comments","events_url":"https://api.github.com/repos/betaflight/betaflight/issues/5314/events","html_url":"https://github.com/betaflight/betaflight/issues/5314","id":300058952,"number":5314,"title":"Frsky R-XSR f.port default output values","user":{"login":"Gozzz","id":18582045,"avatar_url":"https://avatars1.githubusercontent.com/u/18582045?v=4","gravatar_id":"","url":"https://api.github.com/users/Gozzz","html_url":"https://github.com/Gozzz","followers_url":"https://api.github.com/users/Gozzz/followers","following_url":"https://api.github.com/users/Gozzz/following{/other_user}","gists_url":"https://api.github.com/users/Gozzz/gists{/gist_id}","starred_url":"https://api.github.com/users/Gozzz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Gozzz/subscriptions","organizations_url":"https://api.github.com/users/Gozzz/orgs","repos_url":"https://api.github.com/users/Gozzz/repos","events_url":"https://api.github.com/users/Gozzz/events{/privacy}","received_events_url":"https://api.github.com/users/Gozzz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":32,"created_at":"2018-02-25T20:39:40Z","updated_at":"2018-03-03T15:02:44Z","closed_at":null,"author_association":"NONE","body":"<img width=\"466\" alt=\"screen shot 2018-02-25 at 3 03 43 pm\" src=\"https://user-images.githubusercontent.com/18582045/36646054-45e14892-1a40-11e8-9417-f6acdc371f2f.png\">\r\n\r\nI'm using the R-XSR with frsky f.port firmware on a CLR4 (bardwell F4), and a BFF3. Both are showing the same default output when the RX is powered and the TX is not. See the screenshot attached. Once TX is powered the output values are normal. They fly fine and lua/telemetry seems to be working properly, failsafe also seems to work as when the TX is powered off again it drops throttle value below 900us. \r\n\r\nI've emailed Frsky but the BF f.port Wiki suggested providing feedback here.\r\n\r\nDiff from the CLR4-\r\n```# version\r\n# Betaflight / CLRACINGF4 (CLR4) 3.3.0 Feb 18 2018 / 13:34:25 (f07bf40d1) MSP API: 1.37\r\n\r\n# name\r\n\r\n# resources\r\n\r\n# mixer\r\n\r\n# servo\r\n\r\n# servo mix\r\n\r\n\r\n# feature\r\nfeature TELEMETRY\r\nfeature AIRMODE\r\n\r\n# beeper\r\n\r\n# map\r\n\r\n# serial\r\nserial 2 64 115200 57600 0 115200\r\nserial 3 2048 115200 57600 0 115200\r\n\r\n# led\r\n\r\n# color\r\n\r\n# mode_color\r\n\r\n# aux\r\naux 0 0 0 1700 2100 0\r\n\r\n# adjrange\r\n\r\n# rxrange\r\n\r\n# vtx\r\n\r\n# rxfail\r\n\r\n# master\r\nset acc_hardware = NONE\r\nset min_check = 1005\r\nset rssi_channel = 8\r\nset serialrx_provider = FPORT\r\nset blackbox_device = NONE\r\nset dshot_idle_value = 229\r\nset motor_pwm_protocol = DSHOT1200\r\nset pid_process_denom = 1\r\nset osd_warnings = 63\r\nset osd_rssi_alarm = 40\r\nset osd_cap_alarm = 1000\r\nset osd_tim2 = 769\r\nset osd_vbat_pos = 2465\r\nset osd_rssi_pos = 2081\r\nset osd_tim_2_pos = 2486\r\nset osd_throttle_pos = 2454\r\nset osd_current_pos = 2478\r\nset osd_mah_drawn_pos = 2471\r\nset osd_warnings_pos = 2441\r\nset osd_disarmed_pos = 2410\r\nset osd_stat_max_spd = OFF\r\nset osd_stat_bb_no = OFF\r\nset vtx_band = 2\r\nset vtx_channel = 4\r\nset vtx_freq = 5790\r\n\r\n# profile\r\nprofile 0\r\n\r\nset dterm_lowpass_type = PT1\r\nset p_pitch = 47\r\nset i_pitch = 46\r\nset p_roll = 47\r\nset i_roll = 46\r\nset d_roll = 35\r\n\r\n# rateprofile\r\nrateprofile 0\r\n\r\nset roll_rc_rate = 150\r\nset pitch_rc_rate = 150\r\nset yaw_rc_rate = 150\r\nset roll_srate = 79\r\nset pitch_srate = 79\r\nset yaw_srate = 79\r\n\r\n# ```"},"comment":{"url":"https://api.github.com/repos/betaflight/betaflight/issues/comments/370153739","html_url":"https://github.com/betaflight/betaflight/issues/5314#issuecomment-370153739","issue_url":"https://api.github.com/repos/betaflight/betaflight/issues/5314","id":370153739,"user":{"login":"ttjs82","id":2527411,"avatar_url":"https://avatars3.githubusercontent.com/u/2527411?v=4","gravatar_id":"","url":"https://api.github.com/users/ttjs82","html_url":"https://github.com/ttjs82","followers_url":"https://api.github.com/users/ttjs82/followers","following_url":"https://api.github.com/users/ttjs82/following{/other_user}","gists_url":"https://api.github.com/users/ttjs82/gists{/gist_id}","starred_url":"https://api.github.com/users/ttjs82/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ttjs82/subscriptions","organizations_url":"https://api.github.com/users/ttjs82/orgs","repos_url":"https://api.github.com/users/ttjs82/repos","events_url":"https://api.github.com/users/ttjs82/events{/privacy}","received_events_url":"https://api.github.com/users/ttjs82/received_events","type":"User","site_admin":false},"created_at":"2018-03-03T15:02:43Z","updated_at":"2018-03-03T15:02:43Z","author_association":"NONE","body":"Certainly @parnz \r\n\r\nTo start of devices I used was Kakute F4 V2 AIO and the R-XSR receiver. The flight controller doesn't supply power to the receiver while the controller is powered through usb which helps a lot in the update process. Download the FrSky update tool from their website https://www.frsky-rc.com/usb-to-s-port/ \r\n\r\nI had the Rx connected to Uart1 Tx pad initially and the port setting tab on betaflight having the serial rx enabled for the F.Port protocol. What I had to do was disabling the serial rx option and choose smartport from the telemetry output option. The quad was powered through lipo in this phase.\r\n\r\n![image](https://user-images.githubusercontent.com/2527411/36935519-5a235f32-1f01-11e8-9886-b4d45218faba.png)\r\n\r\nAfter saving this option I reconnected to Betaflight and then went to the CLI tab. There I gave the command serialpassthrough 0 57600. Where is the number you get from the UART number you have the receiver connected minus 1. So in my case Uart 1 becomes 0. After this command I unplugged the lipo to power down the receiver (but leave the usb connected). Next I opened the update tool. Make sure the com port setting shows the same com port you had when connecting betaflight.  In the update utility choose the update file you want to update to the receiver. After choosing the file the tool starts to search for the receiver. Now I powered the quad with lipo to turn on the receiver. Then pressing the download button starts the process of updating. If everything goes fine it shows a success message. Then I closed the tool and powered down the quad. Finally go back to betaflight and change the serial rx back on and disable the smartport telemetry option. Also make sure the configuration tabs also has the F.Port chosen. Take notice that disabling the serialrx option also empties all the modes tab options so you have to put back the arm switch settings and such.\r\n\r\nThis process worked for me but the problem can be power cycling the receiver if the flight controller feeds power to it when using usb connection and removing the connection cable to receiver is difficult. The instructions on this page https://github.com/betaflight/betaflight/wiki/Serial-Pass-Through was missing the thing about putting the uart port number to the seriallpassthrough command. Also enabling the smartport setting is something I did differently but I thing the github instruction page doesn't mention anything about that because I think it's written from the point of view where there is SBUS and Smartport connections in use initially and we start from the situation of F.Port.\r\n\r\nGood luck with the update."}}
{"actor":{"display_login":"ttjs82"}}