How does the '--random' work

[chr1shung]

Hi all,

I'm new to python and modbus and recently I'm using pymodbus REPL server as a simulator of the real modbus device .
Everything works fine I have another service acting as client and it can read the data from pymodbus correctly.
However I'm wondering what does the --random option do ? I thought it determined whether to randomize the value to-be-read every r reads but I still got the same value if I don't manually update it with another REPL client.

Thanks for the help .

[janiversen]

It depends on which version you are using, in 3.0.0 there are a known bug, which are solved on dev.

[dhoomakethu]

Thats a good idea what @janiversen suggested, I will spend sometime if I can use the datastore simulator in repl server as well.

[dhoomakethu]

but if you beat me to it with your PR, we are happy to accept it.

[janiversen]

@dhoomakethu I am already working on a similar thing: integrating the repl server and simulator into the web server so you can remotely control the server.

[janiversen]

@dhoomakethu but I am focusing on the web server first, so if you integrate the simulator datastore I can use that.

[dhoomakethu]

Ok, I am yet to go through the new simulator datastore, Will spend some this week to understand it and try to add it to the REPL server. With that said, I will also check if I can use the latest and greatest features in pymodbus and update this simulator if possible. https://github.com/riptideio/modbus-simulator

[janiversen]

Please check that your dev contains commit 30f7166
It was added November 2, so very new.

[chr1shung]

and btw, does the docker image still public accessible ?

➜  ~ docker pull riptideio/pymodbus
Using default tag: latest
Error response from daemon: pull access denied for riptideio/pymodbus, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

[janiversen]

There is an error in the documentation. After the documentation update was merged, it turned out that the riptideio organization is inaccessible for this and a couple of other urgent problems so the image could not be stored there.

To help the contributor doing docker I used my private account “janiversen” where it is publicly available, sorry about the confusion.

[chr1shung]

Is it janiversen/pymodbus ?
Tried pull it and get the same error.

[janiversen]

Seems there was an upload error, so it is not available until the contributor who made it repairs it. The pymodbus team do not maintain docker and other packer images.

[janiversen]

see #1178

[chr1shung]

I see, I will build the image by myself.
Thanks for the clarification

[janiversen]

If you want to maintain it, we are happy to include it (again) in our build process, just submit a pull request.