<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Recently Active Topics]]></title><description><![CDATA[A list of topics that have been active within the past 24 hours]]></description><link>https://forum.rexygen.com/recent</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 18:06:14 GMT</lastBuildDate><atom:link href="https://forum.rexygen.com/recent.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 28 May 2026 14:37:19 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[How to run a compiled .rex model from command line for fast repeated cost-function evaluation]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/5">@cechurat</a><br />
Hi,<br />
I apologize for the delayed response. I needed to consult this issue further before getting back to you.</p>
<p dir="auto">Afterwards, I verified the following behavior: after creating the simroot folder and enabling write access to it, running my project in Simulation mode causes crashes. The issue disappears when I set log.file.enabled=1 in rexcore.cfg.</p>
<p dir="auto">This can be used as a temporary workaround, although it slightly slows down execution, especially when the simulation is run repeatedly many times.</p>
<p dir="auto">If there is a better systematic solution, please let me know.</p>
<p dir="auto">Best regards,<br />
Stepan</p>
]]></description><link>https://forum.rexygen.com/topic/624/how-to-run-a-compiled-rex-model-from-command-line-for-fast-repeated-cost-function-evaluation</link><guid isPermaLink="true">https://forum.rexygen.com/topic/624/how-to-run-a-compiled-rex-model-from-command-line-for-fast-repeated-cost-function-evaluation</guid><dc:creator><![CDATA[stepan.ozana]]></dc:creator><pubDate>Thu, 28 May 2026 14:37:19 GMT</pubDate></item><item><title><![CDATA[Refrigeration system P-H Diagram]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/11">@MikeyH</a> Hi Mike,</p>
<p dir="auto">Thanks for the details. Currently, there is no direct support for such data representation.</p>
<p dir="auto">For small-scale, I can imagine using the CNDR function block. You can also check the STEAM function block, but it appears the data you require is missing there.</p>
<p dir="auto">There is also the possibility to use, e.g., Python or a C library if available.</p>
<p dir="auto">Let me know your thoughts on this.</p>
<p dir="auto">Regards,<br />
Tomas</p>
]]></description><link>https://forum.rexygen.com/topic/622/refrigeration-system-p-h-diagram</link><guid isPermaLink="true">https://forum.rexygen.com/topic/622/refrigeration-system-p-h-diagram</guid><dc:creator><![CDATA[cechurat]]></dc:creator><pubDate>Fri, 27 Feb 2026 13:21:27 GMT</pubDate></item><item><title><![CDATA[License error]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/186">@Jan-Reitinger</a> Hi Jan,</p>
<p dir="auto">Thanks for clearign that up.</p>
<p dir="auto">I'm not sure what happened with the slave device, it hasn't been changed at all, a mystery! If I find the issue I'll le you know.</p>
<p dir="auto">Cheers,<br />
Mike</p>
]]></description><link>https://forum.rexygen.com/topic/623/license-error</link><guid isPermaLink="true">https://forum.rexygen.com/topic/623/license-error</guid><dc:creator><![CDATA[MikeyH]]></dc:creator><pubDate>Fri, 27 Feb 2026 02:46:59 GMT</pubDate></item><item><title><![CDATA[Problems Sequential reading channels ADC MCP3424 via I2C]]></title><description><![CDATA[<p dir="auto">Hi everyone,</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/231">@AlexanderH</a> solved his MCP3424 multi-channel reading issue! Here's the key takeaway:</p>
The Problem
<p dir="auto">When reading multiple channels sequentially from MCP3424, <strong>conversion time must be respected</strong>. Each configuration byte starts a new conversion:</p>

<strong>12-bit</strong>: ~5ms (1/240 s)
<strong>18-bit</strong>: ~267ms (1/3.75 s)

<p dir="auto"><strong>Table 4.3 from MCP3424 datasheet</strong> lists all data rates by resolution.</p>
The Solution
<p dir="auto"><strong>One-shot mode + proper timing between configure/read operations:</strong></p>
<p dir="auto"><strong>For 12-bit (2 channels):</strong></p>
// Channel 1 - configure + convert + read
i2c_bufTx[0] = 0x80; // CH1, one-shot, 12-bit, gain x1  
i2c_write_count = 1;
i2c_read_count = 0;
i2c_ret_fun = I2C(i2c_bus_handle, i2c_chip_address, i2c_bufTx, i2c_write_count, i2c_bufRx, i2c_read_count);

Sleep(0.01); // wait for 10 ms before reading the first channel 
             // Data rate: 12bit = 240 SPS, 14bit = 60 SPS, 16bit = 15 SPS, 18bit = 3.75 SPS

i2c_write_count = 0;
i2c_read_count = 3;
i2c_ret_fun = I2C(i2c_bus_handle, i2c_chip_address, i2c_bufTx, i2c_write_count, i2c_bufRx, i2c_read_count);
// i2c_bufRx[2] contains configuration byte
channel1 = ((i2c_bufRx[0]&lt;&lt;8) + i2c_bufRx[1])/2;

i2c_bufTx[0] = 0xA0; // channel 2, one-shot, 12bit, gain 1 (see MCP3424 datasheet)
i2c_write_count = 1;
i2c_read_count = 0;
i2c_ret_fun = I2C(i2c_bus_handle, i2c_chip_address, i2c_bufTx, i2c_write_count, i2c_bufRx, i2c_read_count);
  
Sleep(0.01); // wait for 10 ms before reading the second channel 
             // Data rate: 12bit = 240 SPS, 14bit = 60 SPS, 16bit = 15 SPS, 18bit = 3.75 SPS
  
i2c_write_count = 0;
i2c_read_count = 3;
i2c_ret_fun = I2C(i2c_bus_handle, i2c_chip_address, i2c_bufTx, i2c_write_count, i2c_bufRx, i2c_read_count);
channel2 = ((i2c_bufRx[0]&lt;&lt;8) + i2c_bufRx[1])/2;

Important Notes
<p dir="auto">Sleep time scales with resolution - 10ms works for 12-bit, 270ms needed for 18-bit</p>
<p dir="auto">Original MCP3422 example worked because it read only 1 channel (no channel switching). The message from the previous tick was probably returned as a response.</p>
Example Update
<p dir="auto">REXYGEN example library will be extended with:</p>

read_mcp3424_12bit.c - 2 channels, 12-bit
read_mcp3424_18bit.c - 2 channels, 18-bit

<p dir="auto">Big thanks to Alexander for the thorough debugging, testing different timing scenarios, and sharing his working scripts!</p>
<p dir="auto">Cheers,<br />
Jan</p>
]]></description><link>https://forum.rexygen.com/topic/620/problems-sequential-reading-channels-adc-mcp3424-via-i2c</link><guid isPermaLink="true">https://forum.rexygen.com/topic/620/problems-sequential-reading-channels-adc-mcp3424-via-i2c</guid><dc:creator><![CDATA[Jan Reitinger]]></dc:creator><pubDate>Tue, 10 Feb 2026 08:02:25 GMT</pubDate></item><item><title><![CDATA[Rexygen Runtime installation after 31st January 2026]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/186">@Jan-Reitinger</a> Thank you Jan. I will try it. Martin</p>
]]></description><link>https://forum.rexygen.com/topic/621/rexygen-runtime-installation-after-31st-january-2026</link><guid isPermaLink="true">https://forum.rexygen.com/topic/621/rexygen-runtime-installation-after-31st-january-2026</guid><dc:creator><![CDATA[martinpies]]></dc:creator><pubDate>Tue, 03 Feb 2026 21:31:42 GMT</pubDate></item><item><title><![CDATA[Handling Base64 Output in Python Projects]]></title><description><![CDATA[<p dir="auto">’m working on a Python task that requires generating Base64-encoded data from user input and converting it to a readable PDF.</p>
<p dir="auto">Before I implement my own solution, I’ve been testing conversions with a simple <a href="https://smallpdffree.com/png-to-pdf/">Base64-to-PDF tool</a> to verify that the encoded strings I’m producing are valid.</p>
<p dir="auto">Has anyone here dealt with converting Base64-encoded content into PDFs directly within Python? I’m wondering whether to use built-in libraries like base64 and fpdf, or if there’s a more efficient way to handle larger files.</p>
]]></description><link>https://forum.rexygen.com/topic/619/handling-base64-output-in-python-projects</link><guid isPermaLink="true">https://forum.rexygen.com/topic/619/handling-base64-output-in-python-projects</guid><dc:creator><![CDATA[elvismartin]]></dc:creator><pubDate>Tue, 18 Nov 2025 11:36:58 GMT</pubDate></item><item><title><![CDATA[Vector demultiplexer VTOR+Python processing]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/26">@stepan-ozana</a>,<br />
The main point from our developer's explanation is that the problem occurs because the Python script assigns outputs from inputs only during the initialization phase (init). However, while the CNR block sets its output directly in init (based on its parameter), the VTOR block likely receives its output settings only after the first run of its main function.</p>
<p dir="auto">Generally, blocks should not process inputs from other blocks during init. During init, each block should manage itself: check parameter settings and initialize its own outputs to starting values. Any processing of inputs and outputs involving other blocks should happen in the main runtime phase.</p>
<p dir="auto">In this case, CNR correctly sets its output in init according to its parameter, which is acceptable. VTOR must read its inputs to set outputs, so it does this later in the main function, which is also correct.</p>
<p dir="auto">Thus, the VTOR output being zero initially can happen because it does not update outputs until the main function runs, unlike CNR which sets fixed output at init. This explains the observed behavior with the VTOR1 showing zeros at first while sharing the same Python script with another block</p>
]]></description><link>https://forum.rexygen.com/topic/618/vector-demultiplexer-vtor-python-processing</link><guid isPermaLink="true">https://forum.rexygen.com/topic/618/vector-demultiplexer-vtor-python-processing</guid><dc:creator><![CDATA[Jan Reitinger]]></dc:creator><pubDate>Sun, 16 Nov 2025 18:12:19 GMT</pubDate></item><item><title><![CDATA[REXYGEN - DWM interface for Debian Trixie]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/16">@gninaus</a> Hi Guenther,</p>
<p dir="auto">DWM is not ready for Trixie yet. We are working on it. I will keep you posted when Trixie is supported.</p>
<p dir="auto">Cheers,<br />
Tomas</p>
]]></description><link>https://forum.rexygen.com/topic/617/rexygen-dwm-interface-for-debian-trixie</link><guid isPermaLink="true">https://forum.rexygen.com/topic/617/rexygen-dwm-interface-for-debian-trixie</guid><dc:creator><![CDATA[cechurat]]></dc:creator><pubDate>Fri, 14 Nov 2025 07:42:40 GMT</pubDate></item><item><title><![CDATA[Core Error &quot;Configuration requires higher license than available on the target device&quot;]]></title><description><![CDATA[<p dir="auto">In this specific case, the error message "Configuration requires higher license than available on the target device"﻿ indicates that RexCore did not find the new version of the license. If an older license version is present on the device and is sufficient concerning the scope of the project, this information should appear in the log and the project should run normally. In such a case, please ignore the error message.</p>
<p dir="auto">This error message will be revised in future versions of REXYGEN.</p>
]]></description><link>https://forum.rexygen.com/topic/616/core-error-configuration-requires-higher-license-than-available-on-the-target-device</link><guid isPermaLink="true">https://forum.rexygen.com/topic/616/core-error-configuration-requires-higher-license-than-available-on-the-target-device</guid><dc:creator><![CDATA[Jan Reitinger]]></dc:creator><pubDate>Thu, 13 Nov 2025 08:44:04 GMT</pubDate></item><item><title><![CDATA[error on Modbus driver]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/5">@cechurat</a> Hi Tomas,</p>
<p dir="auto">Yeah I see, thank you.</p>
<p dir="auto">Cheers,<br />
Mike</p>
]]></description><link>https://forum.rexygen.com/topic/615/error-on-modbus-driver</link><guid isPermaLink="true">https://forum.rexygen.com/topic/615/error-on-modbus-driver</guid><dc:creator><![CDATA[MikeyH]]></dc:creator><pubDate>Thu, 06 Nov 2025 21:24:56 GMT</pubDate></item><item><title><![CDATA[Problems reading from PCF8574A]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/231">@AlexanderH</a> Hi,<br />
I'm sorry. For some reason I didn't get an email notifying me that you had replied. I'm glad you finally resolved the issue.</p>
<p dir="auto">Cheers,<br />
Jan</p>
]]></description><link>https://forum.rexygen.com/topic/614/problems-reading-from-pcf8574a</link><guid isPermaLink="true">https://forum.rexygen.com/topic/614/problems-reading-from-pcf8574a</guid><dc:creator><![CDATA[Jan Reitinger]]></dc:creator><pubDate>Mon, 25 Aug 2025 10:15:46 GMT</pubDate></item><item><title><![CDATA[Core error]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/5722">@har</a> Hi har,</p>
<p dir="auto">This error is related to the timing issue of the 'data_collect' task. The task takes longer to complete than the allotted time. Based on the image, I would guess that the Python block will take the most time to execute. In your case, I would inspect the timing of the whole project and also the diagnostics of task (Target -&gt;Diagnostics -&gt; data_collect and select the Task tab as shown bellow).<br />
e8e7f83c-6ba9-44db-9318-cb844cbf6d51-image.png</p>
<p dir="auto">Cheers,<br />
Jan</p>
]]></description><link>https://forum.rexygen.com/topic/613/core-error</link><guid isPermaLink="true">https://forum.rexygen.com/topic/613/core-error</guid><dc:creator><![CDATA[Jan Reitinger]]></dc:creator><pubDate>Fri, 01 Aug 2025 06:53:04 GMT</pubDate></item><item><title><![CDATA[Bluetooth sensor with rexygen]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/5722">@har</a> Hi Har,</p>
<p dir="auto">I'm sorry, but we are not able to debug third-party Python code for you.</p>
<p dir="auto">If you made it work under plain Python, then you can send the data to REXYGEN using the REST API. Have a look at "0302-03 REST API Python Bash etc", which sends data to REXYGEN using Python.</p>
<p dir="auto">Kind regards,<br />
Tomas</p>
]]></description><link>https://forum.rexygen.com/topic/612/bluetooth-sensor-with-rexygen</link><guid isPermaLink="true">https://forum.rexygen.com/topic/612/bluetooth-sensor-with-rexygen</guid><dc:creator><![CDATA[cechurat]]></dc:creator><pubDate>Wed, 09 Jul 2025 12:18:35 GMT</pubDate></item><item><title><![CDATA[MBM error]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/11">@MikeyH</a> Hi Mike,</p>
<p dir="auto">This is related to the communication timeout - inspect data length with respect to baudrate and timeouts.</p>
<p dir="auto">All REXYGEN error codes here in Docs: <a href="https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/BRef_ENGap3.html#x488-487000C">https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/BRef_ENGap3.html#x488-487000C</a></p>
<p dir="auto">Cheers,<br />
Tomas</p>
]]></description><link>https://forum.rexygen.com/topic/610/mbm-error</link><guid isPermaLink="true">https://forum.rexygen.com/topic/610/mbm-error</guid><dc:creator><![CDATA[cechurat]]></dc:creator><pubDate>Wed, 09 Jul 2025 06:33:08 GMT</pubDate></item><item><title><![CDATA[Bluetooth sensor]]></title><description><![CDATA[<p dir="auto">Hi I am trying to connect my bluetooth sensor(Witmotion WT9011DCL 9-axis BLE Magnetometer Gyroscope) to rexygen via bluetooth so I can stream the data from the sensor into rexygen. I am not sure how to get started on this.</p>
]]></description><link>https://forum.rexygen.com/topic/611/bluetooth-sensor</link><guid isPermaLink="true">https://forum.rexygen.com/topic/611/bluetooth-sensor</guid><dc:creator><![CDATA[har]]></dc:creator><pubDate>Fri, 04 Jul 2025 23:20:17 GMT</pubDate></item><item><title><![CDATA[Error 106]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/11">@MikeyH</a> Hi Mike,</p>
<p dir="auto">This error is triggered when something is preventing Studio from writing to the Project location. Do you have all related folders available for read and write?</p>
<p dir="auto">If the issue persists, can you share a minimal project with us? Thanks</p>
<p dir="auto">Cheers, Tomas</p>
]]></description><link>https://forum.rexygen.com/topic/609/error-106</link><guid isPermaLink="true">https://forum.rexygen.com/topic/609/error-106</guid><dc:creator><![CDATA[cechurat]]></dc:creator><pubDate>Wed, 02 Jul 2025 06:33:52 GMT</pubDate></item><item><title><![CDATA[SPI comms for MCP41X]]></title><description><![CDATA[<p dir="auto">Hello All,</p>
<p dir="auto">Is there, or does anyone have an example of using an MCP41X digital 257 position potentiometer with SPI?</p>
<p dir="auto">Cheers,<br />
Mike</p>
]]></description><link>https://forum.rexygen.com/topic/608/spi-comms-for-mcp41x</link><guid isPermaLink="true">https://forum.rexygen.com/topic/608/spi-comms-for-mcp41x</guid><dc:creator><![CDATA[MikeyH]]></dc:creator><pubDate>Sat, 28 Jun 2025 00:06:48 GMT</pubDate></item><item><title><![CDATA[Bytes to bit]]></title><description><![CDATA[<p dir="auto">sorry, I've just worked it out using the Bitwise demultiplexer</p>
<p dir="auto">f8e2817e-be2b-4795-8b4f-ac8a5581218b-image.png</p>
]]></description><link>https://forum.rexygen.com/topic/607/bytes-to-bit</link><guid isPermaLink="true">https://forum.rexygen.com/topic/607/bytes-to-bit</guid><dc:creator><![CDATA[MikeyH]]></dc:creator><pubDate>Fri, 27 Jun 2025 02:36:37 GMT</pubDate></item><item><title><![CDATA[Connection Problem]]></title><description><![CDATA[<p dir="auto">Hi har,<br />
Check if RexCore is running. I see that you are solving the Python code in another thread. It is possible that your code is not only causing the error, but also causing the entire RexCore to crash. Try connecting to the Raspberry via SSH and enter the command:</p>
systemctl status rexcore

<p dir="auto">Cheers,<br />
Jan</p>
]]></description><link>https://forum.rexygen.com/topic/606/connection-problem</link><guid isPermaLink="true">https://forum.rexygen.com/topic/606/connection-problem</guid><dc:creator><![CDATA[Jan Reitinger]]></dc:creator><pubDate>Wed, 11 Jun 2025 10:46:27 GMT</pubDate></item><item><title><![CDATA[Complier issue]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.rexygen.com/uid/5722">@har</a> Hi har,</p>
<p dir="auto">Thanks for the additional info. We are not able to provide free support on this since it's your custom Python script. The error is not related to the Rexygen ecosystem. It seems that the CPU dispatcher is being initialised multiple times.</p>
<p dir="auto">Tomas</p>
]]></description><link>https://forum.rexygen.com/topic/605/complier-issue</link><guid isPermaLink="true">https://forum.rexygen.com/topic/605/complier-issue</guid><dc:creator><![CDATA[cechurat]]></dc:creator><pubDate>Tue, 10 Jun 2025 08:34:30 GMT</pubDate></item></channel></rss>