@MikeyH Hi Mike,
We found out that there were changes to systemd in Bookworm. On the clean image, there is a problem in DNS after installing DWM. We will adjust the DWM installation accordingly so that everything works on Bookworm and older distributions. We'll let you know when we have a solution.

Cheers,
Jan

@mtomek Hello,
I'm really sorry—I somehow overlooked the fact that you were posting in this old thread. The "Warning 1 1" indicates that the buffer for serial communication between the Master and Slave devices is full:

#define WARNING_SERIAL 1
#define WARNING_SERIAL_BUFFER_FULL 1

Have you added any new data communication or changed the communication speed recently? I’d also like to point out that REXduino is a third-party project, and we don’t have direct control over it. I found the explanation for the warning directly in the source code here:
https://github.com/jaroslavs/REXduino/blob/master/REXduino_slave/REXduino_slave.ino

Cheers,
Jan

Hi @stepan-ozana,

The delay you're observing in Windows is likely due to process prioritization and interruption handling, which are less efficient and harder to control compared to a Linux-based system like Debian or Raspberry Pi OS. In Linux, you have better control over how processes are scheduled and managed, allowing the system to run more smoothly and minimizing the BUSY signal duration. Windows, on the other hand, tends to introduce more overhead when executing external processes, even if the script itself does nothing, due to the way it handles process management at the system level.

Additionally, our systems on Raspberry Pi use a real-time kernel, which further improves the timing and responsiveness of processes. That's why we recommend running time-critical processes on Debian-based systems.

Cheers,
Jan

@MikeyH Hi Mike,
The driver for controlling the GPIO pins on the Raspberry Pi 5 is finally available. I apologize for the delay. In the end, we had to develop an entirely new driver. This driver can also be used on older versions of Raspberry Pi, provided they are running Linux 5.10 or newer. The documentation for the driver is still being developed. However, everything should be described in the 0410_GPIO and 0411_PWM examples if you install the latest daily build of REXYGEN: https://download.rexcontrols.cz/partner/daily/

Cheers,
Jan

@Scoobsalamander Hi Kris,
I am sending the promised example from our developers: ethercat_basic_example.zip. A readme file with a brief description is included. Please let us know if anything is unclear.

Cheers,
Jan

@stepan-ozana Thanks for sharing your solution! Unfortunately, I don't have the required toolboxes to run the script on my computer. However, the code is well-documented and well-organized, which should make it easy for anyone with the necessary Matlab toolboxes to use it without any issues.

'modbus' requires one of the following:
  Industrial Communication Toolbox
  MATLAB Coder Support Package for NVIDIA Jetson and NVIDIA DRIVE Platforms

Error in example_ModbusTcpIP_Comm_RpiToPC (line 9)
m = modbus('tcpip', IP_ADDR,MODBUS_PORT)  %establish communication with the server (client)

Cheers,
Jan

@stepan-ozana
That's good news. I believe your confusion arises from different terminology. The Master/Slave terminology is used in the original context, which we are still adhering to for now. However, the Server/Client terminology is more commonly used nowadays. In the earlier terminology, the client was referred to as master and the server as slave.

@stepan-ozana
Thank you for confirmation. I will update the example. Unfortunately, quite large changes occur across Matlab versions, and there are situations where a script from older versions stops working in newer ones.

Cheers,
Jan

@stepan-ozana
Dear Štěpán,
I can confirm that the Matlab script behaves the same way for me as it does for you. Thanks for reporting the bug. Can you please test the following modified script? This modification works for me:

clc;
clear all;

serviceUrl = 'http://192.168.100.2:8008';
username = 'admin';
password = ''; 

% Data to be written
value_double = 17.89;
value_long = 1234;
value_bool = 1;
value_string = "External string";

% URLs of the data points
url_double = "/api/tasks/rest_api_task/CNR_IN:ycn";
url_long =   "/api/tasks/rest_api_task/CNI_IN:icn";
url_bool =   "/api/tasks/rest_api_task/CNB_IN:YCN";
url_string = "/api/tasks/rest_api_task/CNS_IN:scv";

% Basic authentication header
credentials = base64encode([username ':' password]);
authHeader = ['Basic ' credentials];

% Writing data type double
data_double = struct('v', value_double);
writeData(serviceUrl, url_double, data_double, authHeader);

% Writing data type long
data_long = struct('v', value_long);
writeData(serviceUrl, url_long, data_long, authHeader);

% Writing data type Boolean
data_bool = struct('v', value_bool);
writeData(serviceUrl, url_bool, data_bool, authHeader);

% Writing data type string
data_string = struct('v', value_string);
writeData(serviceUrl, url_string, data_string, authHeader);

% Function to encode base64
function encoded = base64encode(str)
    encoder = java.util.Base64.getEncoder();
    encoded = char(encoder.encodeToString(uint8(str)));
end

% Function to write data to the server
function writeData(serviceUrl, url, data, authHeader)
    options = weboptions('RequestMethod', 'post', ...
                         'ContentType', 'json', ...
                         'MediaType', 'application/json', ...
                         'HeaderFields', {'Authorization', authHeader});
    try
        response = webwrite(strcat(serviceUrl, url), data, options);
        disp(['Successfully wrote data to ', url]);
    catch ME
        fprintf('Error writing data to %s:\n%s\n', url, ME.message);
    end
end

Cheers,
Jan

@stepan-ozana

Hi Stepan,

I believe there might be a misunderstanding in the way the connection is being set up. It seems there might be a confusion between the roles of Master and Slave in Modbus TCP communication.

In Modbus communication, the Slave holds the Modbus table, meaning the Master should connect to the Slave. Therefore, the correct approach should be:

1. Upload the REXYGEN Slave to your Raspberry Pi.
2. Try to connect to the Raspberry Pi from Matlab using the following command, where Matlab acts as the Modbus Master:

m = modbus('tcpip', '192.168.111.2', 'Port', 502);

This way, you are ensuring that the Master (Matlab) is correctly connecting to the Slave (Raspberry Pi with REXYGEN).

Please let us know if you encounter any further issues.

Best regards,
Jan

@MikeyH Hi Mike, I think the fix should be ready within 14 days.
Cheers,
Jan