Giulio Dalla Vecchia

Hi Miro, could you explain better (with an example) what do you intend when you say "transition to History"? Thanks a lot in advance! Giulio

Hi Miro, Is simply putting the Python script to sleep for a certain period before checking the expectations from the target enough to achieve what Matteo wants?

Hi all, I'm working on building the QUTest blinky example for a real target (STM32H7 board) using CMake. However, I believe there might be an issue with the CMakeLists.txt file. When compiling with QUTest, you're not supposed to set any kernel (QV, QK, QXK). If you don't explicitly define QPC_CFG_KERNEL, the variable defaults to 'QV', which leads to the qv.c file being compiled, inevitably causing errors. Does anyone else see this issue?

Hi everyone, Thanks for the replies. I was not referring on the blocking sockets. If I need to run two library, that is already able to get the most out using the non-blocking socket, is it better to isolate the TCP/IP stack using a dedicated AO creating some events for opening/closing/sending/receiving or is it better to manage the libraries in a dedicated othogonal region of the main AO that manage also the TCP/IP stack?

Hi all, Thanks for the replies. I was not referring on the blocking sockets. If I need to run two library, that is already able to get the most out using the non-blocking socket, is it better to isolate the TCP/IP stack using a dedicated AO creating some events for opening/closing/sending/receiving or is it better to manage the libraries in a dedicated othogonal region of the main AO that manage also the TCP/IP stack?

Hi Miro, I was not referring on the blocking sockets. If I need to run two library, that is already able to get the most out using the non-blocking socket, is it better to isolate the TCP/IP stack using a dedicated AO creating some events for opening/closing/sending/receiving or is it better to manage the libraries in a dedicated othogonal region of the main AO that manage also the TCP/IP stack?

Hi Miro, I was not referring on the blocking sockets. If I need to run two library, that is already able to get the most out using the non-blocking socket, is it better to isolate the TCP/IP stack using a dedicated AO creating some events for opening/closing/sending/receiving or is it better to manage the libraries in a dedicated othogonal region of the main AO that manage also the TCP/IP stack?

Hi all, I'm studying the LWIP QP example, where the TCP/IP is running on a dedicated AO. I'm thinking what is the best solution if I need to use other protocols that need to use the TCP/IP stack. For example, if I need to use Modbus on TCP/IP, or I need to connect to a cloud to download/publish some information, I need to call the TCP/IP stack APIs. I think I have two possibility: Create an AO Network Manager to handle the TCP/IP stack. Create some events that can manage the requests to open/close...