Problem with JPG STILLS refresh

Good morning at all!!

I have a problem. I have an url ( sitename.it/wap/img/022/filename.jpg ), and i have to display it into an ignition page using IP Camera Viewer.

I set the JPEG STILLS mode. I can display the image without problems but the image never refresh.

The url refresh every 30 minutes the single way to view the new image for me is to close and re-open the entire project… some cache problem?

To take that jpg and put it every 30 minutes in a database and take the image from that db is my unique solutions or i don’t see some “stupid” way to refresh that image?

thanks a lot guys

Max

the correct link is: adigebacc-dati.it/wap/img/02 … trezze.jpg

…how can i do to update that image in ignition too?

The IP Camera component is just an open feed to the the camera. There is no caching involved. I will try the link you provided in a test project. I will let you know if I come up with anything.

EDIT: Also, how is it refreshed every 30 minutes? Is that the refresh rate configured on the component in the designer, or is that how often the camera itself is refreshing?

the refresh time of the camera is set every 30 minutes.

In ignition ip camera view i set it on a time <<30 minutes (5 minutes, for example) …but after a lot of hours nothing happened… :cry: :neutral_face: :/ :prayer:

Ok, I have it up and running in a project here so I can keep an eye on it throughout the day.

perfect, thanks a lot! :thumb_right: :

Ok, I have attached a screen shot of how I have the component configured in Ignition. I have been watching the video and it appears to be updating. The updates are being pushed to the component, I don’t have to open and close the client for the updates to come through. What version of Ignition are you using?


oh, damn…

i’m using ignition Version 7.5.6 (b1317).
any ideas?
the settings are the the same:


Here is 11.22, the images are taken at 11.20

You can see the refreshed image from the website at 11.15, but ignition (open at 11.10, with a very high refresh rate, visible on the corner of the image) don’t works well… the JPG has changed but ignition continue to reload the same image for hours and hours :scratch:

What can i do?


This is really strange. I was connected to the same camera for most of the day yesterday and watched as it went from day to night. I took some screen shots throughout the day to compare to one another to make sure the image was updating, and it did update. Do you have any kind of antivirus that might be quarantining the images?

Another thing that I am curious about is the refresh rate and retry delay in the Ignition designer. Can you try setting them both to 500 and see if that works?

Ok, I talked to the developers about the image not updating. They are going to put some additional logging into Ignition to help narrow this down/solve the issue. The additional logging will be in Ignition 7.5.7 when it is released.

One of the things the developer suggested is maybe change the refresh rate of the camera. Meaning, have it take a new still more frequently than every 30 minutes. I have been watching the camera again today. I received updated images every 30 minutes at these times, local time for you:

18:15.44
18:45.44
19:15.44

no… i try in 2 different servers in 2 different networks but it doesn’t works :frowning: the image is always the same…

You can try to put the logger “Vision.Components.IPCamViewer” onto Trace to see if it gives you any hints. I’m curious to see if the cam viewer is still refreshing, but simply reading the same image over and over (hitting a cache somewhere…)

Hi,

I’ve the same pb with 7.6.2 on Windows 7 and Java 7.
In the logger, I can see that the component is refreshing the image, but the image stay on the first one.
Any idea ?

TRACE [IPCamViewer-IPCamViewer-FrameProducer] Sleeping for 5000 before next JPEG TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connecting to http://192.168.1.61:8890/Livejpeg?live=1.2... TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connected. response=200 TRACE [IPCamViewer-IPCamViewer-FrameProducer] End of JPEG reached. bytes.length=16223 TRACE [IPCamViewer-IPCamViewer-FrameProducer] Sleeping for 5000 before next JPEG TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connecting to http://192.168.1.61:8890/Livejpeg?live=1.2... TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connected. response=200 TRACE [IPCamViewer-IPCamViewer-FrameProducer] End of JPEG reached. bytes.length=16223 TRACE [IPCamViewer-IPCamViewer-FrameProducer] Sleeping for 5000 before next JPEG TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connecting to http://192.168.1.61:8890/Livejpeg?live=1.2... TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connected. response=200 TRACE [IPCamViewer-IPCamViewer-FrameProducer] End of JPEG reached. bytes.length=16223 TRACE [IPCamViewer-IPCamViewer-FrameProducer] Sleeping for 5000 before next JPEG TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connecting to http://192.168.1.61:8890/Livejpeg?live=1.2... TRACE [IPCamViewer-IPCamViewer-FrameProducer] Connected. response=200 TRACE [IPCamViewer-IPCamViewer-FrameProducer] End of JPEG reached. bytes.length=16223 TRACE [IPCamViewer-IPCamViewer-FrameProducer] Sleeping for 5000 before next JPEG

I think the problem isn’t in the component. I think the component is happily retrieving a new image every 5 seconds - the problem is that there is some HTTP cache between the component and the camera that has cached the frame and is spitting back the same image every time. You can even see that the byte length of the frames is always exactly the same.