Currently the nodes don't support ByteStrings. You would need to change things in the code to be able to display them I think. What is your use case for ByteStrings?

I think something is wrong with the orientation of the corrdinate systems. They Best way for having everything well arranged is to use one of the existing working robots. Delete all the meshes out, move the pivots to the new axis positions and move the meshes in. Now use "Calc Kinematic Parameters". Also Elbow Setting needs to be as set to the correct value. By this you have the guarantee that the kinematic is ok. Or there is a Prefab "EmtpyRobotKinematic" which you can use for this.

I don't think that there is a way for doing this. It is also a little bit "against" the simulation logic. Markes can't be read from external devices in real systems. You could use S7 interface maybe instead.

Perfect - congratulations - in the end it looks like you did the interface pretty quickly.

Hi,

If you're unfamiliar with Unity and C#, I highly recommend learning the basics first. Implementing an interface without this foundational knowledge would be very tough.

Regarding the suggestion to "use any of the existing interfaces as a blueprint and delete everything that is PLC/interface-specific"—what I meant is that you should reuse the C# code (the one script) of an existing interface and remove everything that's specific to that particular interface inside this script. However, doing this requires a good understanding of C# so that you can navigate and comprehend the code.

The parts you remove need to be replaced by C# code tailored to your custom interface (in your case, EGM, where you seem to have some examples on Github). 

That said, simply copying and pasting code won't work in my opinion. You need a decent level of C# knowledge to properly implement and modify a custom interface.

Best regards

Thomas

Future Plans: We might add an empty blueprint to an interface in a future release but this will take some time. This would allow you to simply enter the specific communication part

For the moment, you should use any of the existing interfaces as a blueprint and delete everything what is PLC / interface specific.