Question on usage, apologies if it's been covered. I'm not familiar with Prologix ethernet adapters, only the AR488.
Does it do DHCP or do you set the IP-adress over UART?
Once the IP is known, how do you actually "connect" to it using for example TeraTerm for testing or Python for automation.
Not looking for a tutorial, just basic pointers.
I have not added much on usage on the git page, it is on my todo list, I have just been vague with "prologix syntax"
So out of the box it is configured for DHCP, right now fixed IP requires a recompile, but before the adapters ships I should be able to have a new push that lets you read and set IP address over serial so it will be easier.
Next step is quite easy, it is a TCP server/socket at port 1234, aka telnet port.
So simple example to connect and read would be:
via example netcat, telnet, TerraTerm etc, netcat used as example:
NC <IP> 1234
The way the adapter works then is the same as AR488.
e.g a command prefixed ++ and ends with LF/CR is config command for the adapter, while all others are sent straight for the bus.
So say you want to do a simple *IDN? of the instrument:
NC <IP> 1234
++addr <gpib_addr>
*IDN?
++read
Here we set the address, send command and query the bus.
This can also be more automated with the ++auto command, setting it to ++auto 1, then it does query automatically based in ? in command sent.
Then there is also ++EOI that is default 1, but then we are also getting a bit deeper into GPIB bus structure, let me know if you need any pointers there.
I will see if I can add quick guide on the github or maybe I can refer to a modified AR488 manual for now. Just let me know if you need more for now.
I will prioritize to get a config interface implemented over the usb-c serial when ethernet is used first, docs can always be updated when they are in transit

I also hope to check out the pyvisa fork that has preliminary support for Prologix as I think that is an easy way to get folks going, but need some time to look into, main priority is to get the adapters out first.
Luckily any FW changes is very easily programmed over the USB-C interface for all OSes so any FW update should be very easy for everyone.
@Zucca V1 is verified, I am not sure if you have seen the DT that gives a high level overview over testing? The prototypes that are the final design have been working excellent over many months of heavy use, but I am sure some bugs will surface when they get sent out, but I think those will be firmware more than anything. Link to DT:
https://github.com/Kofen/PoE_Ethernet_GPIB_Adapter/blob/main/docs/dt.md