Live Machine connection Fails on new Haas Firmware 2.06

[philLVQ6X]

Firmware updated as of Tuesday to 2.06 and machine connector get stuck with finding buffer. Buffer setting as well IP/Port all match machine controller as we Live connection is enabled. Machine can be found via CMD ping. It will display this error and ask to use diffent Macros/buffer locations upon changing issue still populates.

[seth.madore]

I'm checking in with the dev team responsible for this area to see if they have any insight into the issue, I'll let you know when I know more.

[seth.madore]

I'm assuming you've downloaded the latest post and machine connector already?

[philLVQ6X]

Yes sir,

FYI Phil B over at JITCADCAM here. Havent seen this problem before.

[seth.madore]

Phil? Never heard of him 🤣😁

That dev team is UK based, so it might not be until tomorrow when we get an answer

[philLVQ6X]

"Clicks Accept Solution" LOL haha I figured this will be a Richard thing. 

[seth.madore · Accepted solution]

Is this set to one or two?

Set it to two and see if that works, please 

[philLVQ6X]

Ill give it a go. No good information on that field as I tried to set it to 1.1 and it errored me out due to not a whole integer.

[philLVQ6X]

Made the change same issue

[seth.madore]

I'm assuming you reposted the code and loaded it back on to your machine?

[Richard.stubley]

Hey, has this worked on this machine before?

Are you pressing cycle start on the machine before Fusion.

Can I please see the NC code. 

Can you confirm the header is getting written in the first 10 macros from the buffer start address. A pic would be usedull. 

Also a pic of your machine file with all the connection settings. 

Sorry for all the questions but saves loads of time.

[philLVQ6X]

[philLVQ6X]

When both posting and running to hit live connection as well starting live connection prior to running program both fail. We get stuck in a loop on Line 38/39 waiting for Fusion connection.

[Richard.stubley · Accepted solution]

The 2nd Macro Variable in the header 10201 in your case we would expect to be kept at a 4. 

This is Measurement results to store. In your previous image this was 4, but the value of 15 is being written and is also in the NC file. 
So has this been changed as a post property or has the post been changed to write out another value other than whats in that post property.

Please give that a go and let me know. 
Either just quickly change 

#10201 = 15
to

#10201 = 4

Or change the property and re post. 

[philLVQ6X]

Do you want the connector version to be 1 or 2?

[Richard.stubley]

Try 1 first. That should work.

[Richard.stubley]

Please let us know if it works or not we are all waiting in suspense 🙂

[philLVQ6X]

We are all good now it was a couple of things. 1. Needs to be 2 not 1, The 15 set to 4. and our network switch was giving a bad IP addresss causing connetion issues as well.