{"action":"created","issue":{"url":"https://api.github.com/repos/cleanflight/cleanflight-configurator/issues/262","labels_url":"https://api.github.com/repos/cleanflight/cleanflight-configurator/issues/262/labels{/name}","comments_url":"https://api.github.com/repos/cleanflight/cleanflight-configurator/issues/262/comments","events_url":"https://api.github.com/repos/cleanflight/cleanflight-configurator/issues/262/events","html_url":"https://github.com/cleanflight/cleanflight-configurator/issues/262","id":113204843,"number":262,"title":"Chrome Update - Configuration and Receiver Tab issues","user":{"login":"pilotgeek","id":15274516,"avatar_url":"https://avatars.githubusercontent.com/u/15274516?v=3","gravatar_id":"","url":"https://api.github.com/users/pilotgeek","html_url":"https://github.com/pilotgeek","followers_url":"https://api.github.com/users/pilotgeek/followers","following_url":"https://api.github.com/users/pilotgeek/following{/other_user}","gists_url":"https://api.github.com/users/pilotgeek/gists{/gist_id}","starred_url":"https://api.github.com/users/pilotgeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pilotgeek/subscriptions","organizations_url":"https://api.github.com/users/pilotgeek/orgs","repos_url":"https://api.github.com/users/pilotgeek/repos","events_url":"https://api.github.com/users/pilotgeek/events{/privacy}","received_events_url":"https://api.github.com/users/pilotgeek/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-25T03:55:18Z","updated_at":"2015-10-28T22:24:47Z","closed_at":"2015-10-28T22:24:47Z","body":"I'm noticing some strange behavior after the latest chrome release.  (Chrome Update - The stable channel has been updated to 46.0.2490.80 for Windows, Mac, and Linux. This release contains a critical update to Adobe Flash Player (19.0.0.226).)\r\n\r\nIn CF, the configuration tab doesn't reboot when you click save and reboot.  Instead it saves and stalls on rebooting.  If I navigate to a different tab, it says waiting for data with the 'thinking' lines.  If I unplug to re-boot, the save looks like it worked when I connect next.\r\n\r\nThe more serious issue is that when using the Naze 1.10.0 firmware, the Throttle, Yaw, Pitch, and Roll controls don't show as functioning on the receiver tab.  If I erase the board and flash back to Naze 1.9.0 everything works except pitch using the same setup that was connected with 1.10.  Ive tested this extensively with multiple rx's on clean brand new models in the tx.  (Spectrum Rx's (610, 6210, 7610) on a DX9.  I've continuity tested the wires with a multimeter and swapped signal wires into the Rx to double check it's not a connection issue or a Tx output issue.  When I swap signal wires, the control resumes to the 'wrong' channel and the pitch (on 1.9.0) remains static.  On 1.10.0, the Aux channels work, but the control surface channels don't.  If I swap an Aux1with throttle, then the throttle stick moves Aux1 on the receiver tab, but the throttle shows no movement.\r\n\r\nShort vid of whats going on:\r\nhttps://youtu.be/hlkhvaQFAro \r\n\r\nCan someone please confirm if this is a bug related to the Chrome update on last Thursday (10/22/15)  or if I have a unique situation here.\r\n\r\nThanks\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/cleanflight/cleanflight-configurator/issues/comments/152016220","html_url":"https://github.com/cleanflight/cleanflight-configurator/issues/262#issuecomment-152016220","issue_url":"https://api.github.com/repos/cleanflight/cleanflight-configurator/issues/262","id":152016220,"user":{"login":"pilotgeek","id":15274516,"avatar_url":"https://avatars.githubusercontent.com/u/15274516?v=3","gravatar_id":"","url":"https://api.github.com/users/pilotgeek","html_url":"https://github.com/pilotgeek","followers_url":"https://api.github.com/users/pilotgeek/followers","following_url":"https://api.github.com/users/pilotgeek/following{/other_user}","gists_url":"https://api.github.com/users/pilotgeek/gists{/gist_id}","starred_url":"https://api.github.com/users/pilotgeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pilotgeek/subscriptions","organizations_url":"https://api.github.com/users/pilotgeek/orgs","repos_url":"https://api.github.com/users/pilotgeek/repos","events_url":"https://api.github.com/users/pilotgeek/events{/privacy}","received_events_url":"https://api.github.com/users/pilotgeek/received_events","type":"User","site_admin":false},"created_at":"2015-10-28T22:24:47Z","updated_at":"2015-10-28T22:24:47Z","body":"Turns out this may have been largely due to a hardware issue.  One of the pads on the Rev5 board disconnected from the board.  Even though my wire continuity tests showed a positive connection, the actual pad on the board disconnected for some reason.  Several others have reported the AETR controls not working on 1.10.0 and .65.  so, there might still be a bug, but for now it's resolved for me by installing a new Naze32.\r\n\r\nI've since replaced the board and flashed to 1.11 on .65 with the latest version of chrome and everything works except the reboot issue.  Looks like the re-boot issue will be solved with an upcoming release sometime soon.  \r\n\r\nI'm going to close the issue as I'm in the air again and everything seems to be working for now."}}