no, 2.5 is on static ip, 3.1 (for now) DHCP
the two raspberries also have different hostnames.
I doubted the W610 was messing up and sending messages to the āwrongā server, as such.
But on the other hand, there is no control on the serial bus side, where only one Master is allowed (the W610 playing master here).
Iād suspect the W610 of being simple minded (it is the simplest USR gateway); so letās assume it works by passing a TCP poll out to serial, and when some response comes back it gets sent to the TCP server.
If itās not very good at queuing ā¦
Server A sends TCP poll
W610 transmits to serial
Server B sends TCP poll ā¦ should we queue that, or send it now?
Serial response message arrives.
W610 sends to ā¦ Original requester A? Latest requester B? Both?
Scope for trouble here.
But itāll only go wrong when two different polls turn up close together, so itāll work sometimes, which fits your observation.
Iāll bet it only goes wrong with identical poll messages, and the W610 is using the modbus command FC/ID echo embedded in the serial response to determine which TCP poll it ābelongsā to.
yeah that sounds about right. iāll activate the modbus binding only one 1 machine if that really solves the problem. the modbus items arenāt crucial for automationā¦
thanks!
@Thomas_Gfeller Kannst du kurz sagen, wie die Verbindung zwischen dem originalen Modbus Adapter von D&W (4 Adern) und dem āseriellen Steckerā gemacht wird? (der dann in den W610 gesteckt wird)
Benƶtige ich Ć¼berhaupt die 4 Adern? Oder nur GND + TX + RX? (also kann ich auf der DuW Seite Pin 4 alias 5VDC weglassen?)
Ich bin irgendwo in dieser uralt seriellen Stecker Hƶlle gefangen und sehe den Wald vor lauter BƤumen nicht.
3 Adern, TX, RX und GND mĆ¼ssten reichen.
first, thank you for your detailed description!
I have connected the original d&w Modbus-Adapter to a RS232-RS485 converter, and this converter to a Weinzierl 886 interface (Modbus to KNX).
After some settings I can now read the d&w Modbus registers, but I cannot write them. I know that some registers are R/O, but also the ones marked as R/W do not accept values for some reason.
Did you have to enable anything like a āwrite modeā in the d&w settings, or would you have any other clue on that?
Thanks!
Stefan
Hi Stefan
You can only write registers which are in the thing file configured for writing like the following one:
// Betriebsart
Bridge poller p5002 [ start=5002, length=2, refresh=60000, type="holding" ]
{Thing data r5002 [ readStart="5002", readValueType="int32", writeStart="5002", writeValueType="int32", writeType="holding", writeMultipleEvenWithSingleRegisterOrCoil=true ]}
as far as I remember not all registers are technical writeable (see documentation for details). But the above p5002 (Betriebsart) definetly is.
I have a stratos system which has a room terminal. There under operation parameters (Betriebsparameter) I have the following settings. They might be necessary:
26/28 Schnittstelle seriell: RS232
27/28 Baudrate: Serial Interface 19200 Baud
28/28 Modbus Adresse: 1
BR
Thomas
Hi Thomas,
long time no see. I finally managed to find the time to crimp the MICA plug (tip for everyone else: it is quite possible to crimp this with a small screwdriver, but you have to use ribbon cable, nothing else will work, because the contacts are not strong enough to penetrate through ānormalā cable insulation. Ribbon cable insulation seems to be softer.)
I have a quite unexpected problem though: I would like to connect the W610 using Ethernet and not WLAN. Did you or anyone else succeed doing this? 1:1 connection to the PC works fine, but if I put it in my network, it seems to insist on opening its own DHCP Server and wrecks havoc on my LAN. On the other hand, it wonāt work as a DHCP client.
Best, Matthias
Solution: The trick is to use the WAN setting instead of the LAN setting