-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uPNP does not find FDR-X1000V #23
Comments
Checked what happens with my HDR-AS15 with the following patch.
As you can see the camera returns 3 services, all with the same IP and port. If this different from the X1000V?
Ignore the 'forbidden' this is a problem with this specific camera and can be 'solved' by authenticating first (see 'authenication2' branch). |
Hi, Sorry, but I'm not sure how I'm supposed to use that, I'm quite new to this. What url am I supposed to give to _parse_device_definition? |
Hi, if you're interested about how the uPNP works this is quite a good write-up: However just adding the two print statements and running the 'dump_camera_capabilities' script (as above) should give us enough information to see if there's an obvious difference in the XML that the camera returns. |
Hi, I'm sorry I had not the same version of pysony as you, and I didn't understand how the prints changed the sump_camera_capabilities script. I changed everything to fit, and unfortunately it does not return anything. In the discover function, the packets returned by the _listen_for_discover function is the empty list. I don't know much about network configuration, am I supposed to change the msg defined in the discover function? |
Oh, that might mean that we're not waiting long enough for the camera to respond. There should be no need to change outgoing message in the discover function (well we think its right). The basic sequence is:
You could try to increase the timeout to see if the FDR-X1000V just takes a little longer to reply, 10s is probably overkill, but would confirm if this is the issue.
You do have the computer connected to the camera's WiFi at this point, don't you? You suggested that using a 'QX_ADDR=..' works so I guess you do... just checking :-) |
Yes I'm connected to the wifi ;) . Still nothing... I had already tried to wait a little bit longer than one second. I've juste tried again with 10s and even 20s, but it's no better... When I do
I get None, and when I do
I get 141. Is this of any help? For SSDP_ADDR and SSDP_PORT I have the same thing as you. And I don't know if it changes anything, but I'm using Linux, not windows. |
as reported by @toufraita.
'src/example/dump_camera_capabilities.py' script does not find camera, but capabilities do list if QX_ADDR is manual set to correct IP.
This is probably an issue with the big regular expression which attempts to pull the IPs out of the XML file that the camera 'sends'. (note: QX10 has an extra space which we needed to appreciate). Script know to work on QX10, AS15 and HX60V at present.
X1000V is in the same group as AS200, so there code base is likely the same
https://developer.sony.com/develop/cameras/
Try some extra prints to see if there's something obvious, or upload the XML file for inspection....
The text was updated successfully, but these errors were encountered: