{"action":"created","issue":{"url":"https://api.github.com/repos/ivmech/ivport-v2/issues/3","repository_url":"https://api.github.com/repos/ivmech/ivport-v2","labels_url":"https://api.github.com/repos/ivmech/ivport-v2/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/ivmech/ivport-v2/issues/3/comments","events_url":"https://api.github.com/repos/ivmech/ivport-v2/issues/3/events","html_url":"https://github.com/ivmech/ivport-v2/issues/3","id":180113203,"node_id":"MDU6SXNzdWUxODAxMTMyMDM=","number":3,"title":"Hardware/ setup issue with ivport-V2 board","user":{"login":"Longans","id":22527613,"node_id":"MDQ6VXNlcjIyNTI3NjEz","avatar_url":"https://avatars2.githubusercontent.com/u/22527613?v=4","gravatar_id":"","url":"https://api.github.com/users/Longans","html_url":"https://github.com/Longans","followers_url":"https://api.github.com/users/Longans/followers","following_url":"https://api.github.com/users/Longans/following{/other_user}","gists_url":"https://api.github.com/users/Longans/gists{/gist_id}","starred_url":"https://api.github.com/users/Longans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Longans/subscriptions","organizations_url":"https://api.github.com/users/Longans/orgs","repos_url":"https://api.github.com/users/Longans/repos","events_url":"https://api.github.com/users/Longans/events{/privacy}","received_events_url":"https://api.github.com/users/Longans/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2016-09-29T17:32:03Z","updated_at":"2018-09-17T14:31:57Z","closed_at":null,"author_association":"NONE","body":"Please see anfegori91's post at https://github.com/ivmech/ivport/issues/21#issuecomment-250534439\nIt's got a nice picture of the issue. Re-posting here since our questions are about the V2.\n\nLooks like my board has the R5-R6 shorted together. Are they electrically connected on that one side anyway?\n\nI'm also confused with some of the jumpers, and the manual hasn't been much help. No idea what X and Y are, and if the GPIO (next to 3V3) needs to be jumper-ed as well.\n\nI did try it out. the Pi can't see the camera with the mux unit in place. I have the two A jumpers shorted and have tried with and without the GPIO pins 7,11, and 12 set for each camera. Never got a connected camera.\n\nCamera and all cables still work after taking the mux board out of the path.\n"},"comment":{"url":"https://api.github.com/repos/ivmech/ivport-v2/issues/comments/422040809","html_url":"https://github.com/ivmech/ivport-v2/issues/3#issuecomment-422040809","issue_url":"https://api.github.com/repos/ivmech/ivport-v2/issues/3","id":422040809,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMjA0MDgwOQ==","user":{"login":"pranav1796","id":9511335,"node_id":"MDQ6VXNlcjk1MTEzMzU=","avatar_url":"https://avatars0.githubusercontent.com/u/9511335?v=4","gravatar_id":"","url":"https://api.github.com/users/pranav1796","html_url":"https://github.com/pranav1796","followers_url":"https://api.github.com/users/pranav1796/followers","following_url":"https://api.github.com/users/pranav1796/following{/other_user}","gists_url":"https://api.github.com/users/pranav1796/gists{/gist_id}","starred_url":"https://api.github.com/users/pranav1796/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pranav1796/subscriptions","organizations_url":"https://api.github.com/users/pranav1796/orgs","repos_url":"https://api.github.com/users/pranav1796/repos","events_url":"https://api.github.com/users/pranav1796/events{/privacy}","received_events_url":"https://api.github.com/users/pranav1796/received_events","type":"User","site_admin":false},"created_at":"2018-09-17T14:31:57Z","updated_at":"2018-09-17T14:31:57Z","author_association":"NONE","body":"> I've tested the board with four identical v2 cameras following the \"getting started\" guide and only CAM1 and CAM2 could be switched calling the `camera_change()` function. All connections were tested. Also, I've tried by changing the jumper to B and C with same results. Note: when creating the iv object, the iv_jumper parameter was changed from `'A'` to`'B'` and `'C'` in my tests, but when getting the iv.f1pin and iv.f2pin values it still shows '11' and '12', so I had to change te code to force the pin change. @ivmech , why didn't you included `camera_change(3)` and `camera_change(4)` in the suggested example? is there a hardware issue in this board? (I've tried defining my own pin change functions but I can't get past the second camera!!!). @Longans how is your progress?\r\n> \r\n> log after failed attempt to change to camera 3 (a full tested brand new working camera):\r\n> \r\n> ```\r\n> mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board\r\n> mmal: mmal_vc_component_enable: failed to enable component: ENOSPC\r\n> mmal: camera component couldn't be enabled\r\n> mmal: main: Failed to create camera component\r\n> mmal: Failed to run camera app. Please check for firmware updates\r\n> ```\r\n\r\n@anfegori91  I am facing a similar issue. I am able to get two cameras function but can't access cam3 and cam4. Is there any solution for this. "}}
{"actor":{"display_login":"pranav1796"}}