HELP NEEDED: MAC Addresses

[LarsK1]

Hi everyone,
we're currently implementing many features for 2.0.0. One feature, that is missing is autodiscovery - since Solvis doesn't provide us with data we need to collect it our selves. If you want to help, please post your devices mac address next to the model.

Example:
XX-XX-XX-XX-XX-XX: Solvis Ben 3

[fkhr79]

FC:0F:E7:5D:21:18: LAN, SC3
60:8A:10:CC:84:F2: WLAN, SC3

00:08:DC:19:B6:B0: LAN, Solvis Remote

[fkhr79]

some other user:
00:08:dc:50:06:f7: LAN, Solvis Remote (SC2)

[fkhr79]

Just had a look at the network traffic the solvis software "Konfig_Remote_V1020.exe" produces (this problem massively triggers me). Thought I could find a clue concerning the MAC address range. Unfortunately not. BUT: Now I think I know how the discovery of the Remote Devices (SC2) is done:
The software sends an UDP broadcast from port 48714 to port 48713. The UDP payload contains the message "FIND" (46494E44).
(note: wireshark filter "udp.port == 48713 || udp.port == 48714")

The following answer of Solvis Remote looks like this:

It contains a UDP header and a data-block (111 bytes) starting at byte 42. The data block is structured as follows:

The ip adress we are looking for is contained twice: bytes 26-29 and again in the data block.

Done - for SC2/Solvis Remote at least! 🚀 Just needs to be implemented yet...😉

(In fact there's a little more we could do: set username, password, network... but this goes too far at the moment)

[fkhr79]

I had a look in the IEEE database:

So we have at least a first MAC address range we could use.

Suggestion: We know, that the Solvis device supports Modbus. It should be enabled by the user. So we could arp the local network, filter by the mac address range and try a simple modbus connect. If the device responds we have a candidate!
If no device responds we could remove the filter and try a modbus connect to all the devices with local ip addresses. If the connect is successfull we could try to read the ... let's say version registers. If that is successful we're also done.
Since the SC3 does have a web ui we could use this to filter the ip list of potential devices too.

[fkhr79]

further implementing to be discussed in #161