-
Hi everyone, I'm Matteo Many thanks to everyone. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 10 replies
-
Why?
Why?
Where you talking with people from Probat HQ or others? What did they try?
What did you change between the working state and the non-working state?
Which cable? The one of the roaster?
I cannot follow you here. Which IP and Google page? Which "control panel" do you get "projected" on your laptop? Maybe you can connect to the roaster via the browser on your laptop? Which URL address are you using for this in your Web browser? Could you please paste it here?
Your report lacks a lot information. From the screenshot I can see that you are on Windows using Artisan v2.10.2. Could you attach a picture of your roasters control panel showing its IP address?
|
Beta Was this translation helpful? Give feedback.
-
Any reason why you have set the Host IP address in the Artisan WebSocket tab to What happens if you fix that typo in the Artisan WebSocket tab and uses the correct IP address of the roasting machine? Anyhow, it would be worse asking Probat if that machine also has a DNS name that could be used instead of the IP. The advantage would be that even if the IP address assigned to the Probat roaster by your router changes over time it would always be available under the same IP name and thus the configuration in Artisan would not need to be changed. I am aware that at least the Probatone series II machines did have an IP name. Not sure about the Series III. |
Beta Was this translation helpful? Give feedback.
-
Sorry just a small mistake trying different things. The correct one was used several times. |
Beta Was this translation helpful? Give feedback.
-
Am I Right to say that: |
Beta Was this translation helpful? Give feedback.
-
Could you try a small thing: downgrade to Artisan v2.10.0 and retry. Rational: in Artisan v2.10.2 we upgrade the WebSocket communication which is used to communicate with newer Probat machines to a different library. That library seems to be using compression of the data by default, which is also standard. The previous lib used did not support compression at all. Maybe this difference can explain your connection issue. I am now adding a flag to deactivate compression for WebSocket communication and some additional logging. Thus if v2.10.0 still does not connect for you we can look at the log data to see what exactly is going wrong. Sorry for your troubles with Artisan! |
Beta Was this translation helpful? Give feedback.
-
Hi Makomo, I do confirm. Version 2.10.5 is giving the readings. |
Beta Was this translation helpful? Give feedback.
-
Hi MAKOMO how are you? Unfortunately I had to change laptop as it crashes too many times. We just installed a router with sim card. I'm facing the same problem of communication with artisan. It looks I'm not able to download the v2.10.0. I'll send you some shots. to be notice: now the p12 III ethernet cable is not able to communicate with the new laptop even if plugged. Current situation. I am able to use only the ethernet connection with the old laptop Regards |
Beta Was this translation helpful? Give feedback.
Could you try a small thing: downgrade to Artisan v2.10.0 and retry.
Rational: in Artisan v2.10.2 we upgrade the WebSocket communication which is used to communicate with newer Probat machines to a different library. That library seems to be using compression of the data by default, which is also standard. The previous lib used did not support compression at all. Maybe this difference can explain your connection issue.
I am now adding a flag to deactivate compression for WebSocket communication and some additional logging. Thus if v2.10.0 still does not connect for you we can look at the log data to see what exactly is going wrong.
Sorry for your troubles with Artisan!
Marko