[[UM S5] Camera feed stopping]

1 hour ago, MiguelV said:

Hi,

 

We are working on a fix for this issue and we will include it in our next version 5.6. Unfortunately I cannot give you an exact timeline for 5.6, so please bear with us.

 

Hi Miguel, so you are confirming the issue ?

 

Did the information I give you helped ? I might have other suggestions to improve that part.

 

O.

[[UM S5] Camera feed stopping]

On 1/24/2020 at 3:12 AM, jkcz said:

I had the same issue a while back, I decided to revert to an older firmware version which had worked fine but some say if you reset Cura Connect it fixes the issue. Just beware that it will delete all your print history/stats/logs.

 

Do you have a link to an older firmware? It looks like Ultimaker removed all their old firmwares to be accessible. (which is NOT cool!). Being able to try to debug the issue from the community would be much more efficient.

@Ultimaker: As a System Administrator I tell you: Obfuscation is debunked security strategy.

 

O.

 

[[UM S5] Camera feed stopping]

Hi,

As I have seen in some posts here, we are having problems with the camera feed stopping using latest firmwares.

We are using the latest (5.4.27).

 

The UM needs to be restarted for the feed to come back but it can't be done while printing.

 

Some information that may help:

• It happens when a client (Cura or other) is streaming the feed for some hours
• We use the streaming feed endpoint (http://um.ip/?action=stream) to create "fast-forwarding" videos of the print
• Using VLC with that endpoint

When the stream stops working, here what we get from the endpoint:

> GET /?action=stream HTTP/1.1
> User-Agent: curl/7.38.0
> Host: um.ip:8080
> Accept: */*
> 
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Connection: close
< Server: MJPG-Streamer/0.2
< Cache-Control: no-store, no-cache, must-revalidate, pre-check=0, post-check=0, max-age=0
< Pragma: no-cache
< Expires: Mon, 3 Jan 2000 12:34:56 GMT
< Content-Type: multipart/x-mixed-replace;boundary=boundarydonotcross

--boundarydonotcross

It stucks after that with the connection remaining opened.

It looks like a buffering/memory problem and after some research, maybe that may be a fix:

https://github.com/jacksonliam/mjpg-streamer/commit/501f6362c5afddcfb41055f97ae484252c85c912

 

O.

[Ultimaker S5 - Remotely start a new job after a finished job]

Since I was to use 3 colors: black for the backplane, orange and blue for the letters,

 

I used black and orange for the first printing with the black being "negative" so that the blue letters would fit to glue them into the "sockets" after they are printed. All layers were imported from three PNGs.

 

Is it a best practice ? I'm pretty sure it will need some trimming ?

 

Thanks,

O.

 

 

[Ultimaker S5 - Remotely start a new job after a finished job]

19 minutes ago, gr5 said:

No because it will then do another auto level and make a mess of the existing part.

 

Instead slice 2 (or more) parts in cura at the same time.

 

That's something I was wondering, the auto level (tips touching) is done before every print ?

 

[Ultimaker S5 - Remotely start a new job after a finished job]

Web UI state

[Ultimaker S5 - Remotely start a new job after a finished job]

Hi,

I just bought a Ultimaker S5 and using Cura 3.6.0.

After a job has finished, it is blocking other jobs that could be printed elsewhere on the glass plate.

According to the API request "/api/v1/print_job/state", it is in "wait_cleanup" state.

 

Is there a way to clear that state to send another job remotely without having to confirm the job on the Touch Screen ?

 

Thanks,

 

O.