Hi, the PR is not merged yet. I’ll have it fixed in the firmware tonight.
Also, the library is in the openmv github under scripts/libraries. It’s not in the IDE.
1 Like
Oops, saw something related to sockets in commits and assumed that it was the fix 
Will wait for the merge, thank you!
The PR was merged. You can build the latest firmware and test now.
Hi, thank you so much for the fixes.
Yes, it is working now.
Glad to hear! Also, this example stresses all the drivers pretty well so it should be good for us to use as a benchmark to prevent regression.
Hi, I would appreciate if someone can help me. Am I missing something? Firmware version 4.4.2. I got the IP 192.168.3.2:554, but I can’t visualize it. I’m using ffplay.
Hi, we just merged the change into the tip of the latest:
install this:
Niclav: firmware.bin
Thank you for the answer @kwagyeman , I’m using the latest firmware Nicla release.
ffplay.exe -rtsp_transport udp rtsp://192.168.3.2:554
rstp.py
Hi, you have to run an example script on the camera. The libraries just run on the camera.
Hi @kwagyeman, Could you explain that to me please? I have the example script on the camera.
Okay, does that example script connect to the internet and have a DHCP address? And then did you point ffmpeg to that IP address printed?
From the previous post it looks like you are doing the right thing.
Um, I can’t debug this remotely. You need to run wireshark, filter for the IP address of the camera and send me the dump of what happens during transactions.
We fixed the code pretty well though. It should just work now.
Okay, at a minimum you should see packets from FFMEG trying to ping the camera on wireshark. Even if the camera doesn’t respond.
Please remove the port number from the ffmpeg command. However, it appears the issue is that ffmpeg doesn’t send any packets to the camera. When you run the ffmpeg command you should see it send a TCP SYN packet to the camera IP address at a minimum.
Is that communication to the camera? I see TLS stuff and etc. happening.
Question, when I try to open a video for the FFPlay, the route of my CMD is where the file(video) is saved, and it works well.
But, when I’m going to transmit on the camera the route of my CMD is where I have saved the RTSP.py file?
Example on this route “C: \ Users \ Eli \ Github \ OpenMV-Master \ OpenMV-Master \ Scripts \ Libraries” (RTSP.py)
ffplay -rtsp_transport udp rtsp://192.168.0.17
The rtsp file on your computer is not applicable. That gets compiled into the camera firmware. What’s on your computer does nothing.
Please add an IP address filter to your wireshark session for the camera.
You should clearly see FFPLAY send packets to the camera IP address.
1 Like