Hi Bruno,
the Monarco HAT has hardware PWM and therefore does not need to create PWM in software using a PWM block. Documentation to the PWM on Monarco HAT can be found on page 16 in Monarco technical specification https://www.monarco.io/docs/Monarco-HAT-Hardware-Reference-Manual.pdf.
All you need to do is set the PWM frequency (in your case to 50 Hz) and calculate the actual duty cycle for one channel according to the equation:

Duty_cycle = pulse_width/period_length

Take a look at example 0121-05_Monarco_HAT_PWM_output to find out how to set the frequency and duty cycle for PWM1 (for example).

Hope, this will be helpfull.
Cheers
Jan.

@pancirm Dobrý den,
máte pravdu. Děkujeme za upozornění. Zjistíme, kde je chyba, a dáme Vám co nejdřívě vědět.

S pozdravem,
Jan Reitinger

@scoobsalamander
Hi, you can divide the initialization into two commands:

char stringTemp[80];
stringTemp = "";

if you want to be sure that the array is empty. The warning will disappear.

Cheers,
Jan

@mtomek Hi Michal,
I found the meaning of the errors directly in the REXduino_slave.ino code. The first number indicates the type of error and can have values:

• 49 - ERROR_COMMAND
• 50 - ERROR_PINMODE
• 51 - ERROR_SERIAL
• 52 - ERROR_ONEWIRE
• 53 - ERROR_I2C
  The second number indicates error specification. For example for ERROR_ONEWIRE:
• 49 - ERROR_ONEWIRE_NOMOREDEVICES
• 50 - ERROR_ONEWIRE_BUSYBUS
• 51 - ERROR_ONEWIRE_BADCRC
• 52 - ERROR_ONEWIRE_DEPLETED
• 53 - ERROR_ONEWIRE_NOTEMPDEVICE
  I agree that the errors could be mentioned more explicitly somewhere.

So in your case, the code 52 51 means bad crc error. So, for example, some noise may have appeared during data transmission.

I don't have any experience with the UniPi hub, because I'm using Monarco HAT. But as I understand to the UniPi 1-wire knowledge base, you should use the first hub port to connect the hub to your Raspberry Pi GPIO. Default GPIO pin for 1-Wire is GPIO 4. After connecting, you can read the data in REXYGEN using OwsDrv module. Please pay special attention to the note in the knowledge base:

Unfortunately, I have no idea if the UniPi hub provides ESD protection. You should check this directly from the manufacturer. If the hub doesn't have protection, I definitely wouldn't connect it directly to the Raspberry GPIO. The resistance of such a solution to the induction of unexpected voltages is negligible and it's possible that your Raspberry would get burned. In the absence of ESD protection, I would rather invest in Monarco HAT, where ESD protection is present and Monarco communicates 1-Wire over the I2C bus (documentation here), so 1-Wire is not connected directly to the processor.

Cheers,
Jan

@mtomek Hi Michal,
REXduino slave error, code 51 49 means that the master is sending too much data... in other words that the slave is unable to process data and respond to all the requests.

Keep in mind that reading data from 1-wire sensors takes a relatively long time (the slave is currently set as #define ONEWIRE_TEMPCONV_DELAY 800 ms). It can very easily happen that the slave will not be able to read data from twelve 1-wire sensors and send values ​​over the serial to your Raspberry Pi with the period with which the master is running.

My advice is to try setting a larger value for the running period on the master side. You can do it in REXYGEN in the EXEC block (see documentation here https://www.rexygen.com/doc/ENGLISH/MANUALS/BRef/EXEC.html).

But my private opinion is that you are very close to the maximum possibilities of REXduino. In your place, I would consider the options I suggested to you above.

Best regards,
Jan

@fabio Není zač.

Dobrý den,
jak kontrolujete, že výstup UP bloku PWM má hodnotu pouze OFF? Pokud kontrolu provádíte pouze sledováním výstupu ve watch režimu, změnu pravděpodobně ani neuvidíte. Aktualizace hodnot ve watch režimu Rexygen Studia probíhá s daleko větší periodou a tento způsob sledování je pouze orientační. Zkusil jsem namodelovat task se stejnými parametry, jako vy a v Trendu (vizte obrázek) je vidět, že PWM spíná i pro vstup u = 0.06. Pro jistotu posílám zabalený i svůj projekt.

PWM_test.zip

Opravdu potřebujete nastavené i hodnoty dtime, btime a offtime? Tyto parametry jsou určeny pro použití v případě, že je to nezbytné kvůli spínanému hardware. Pokud ve specifikaci vyloženě tyto hodnoty nemáte uvedeny, nechal bych je nastavené na 0.

S pozdravem,
Reitinger

Hi guys,
@mikeyh you're welcome. @apollo is right with persistent parameters. If you don't just do short-term tests, don't forget to turn persistent parameters on.

@mikeyh Hi Mike,
one possibility is to use a SHLD block with Triggered sampling mode (documentation here). When you send a pulse to the block input SETH, the current value of input u is stored at output y. The overall connection can then look something like this:

Cheers,
Jan

@mtomek Hi Michal,
you are welcome. I'm glad everything is working as it should. Good luck with your project.

Regards,
Jan

@mtomek Hello Michal,
the error: Unable to load authentication database from "/rex/rexcore/auth.rex": File open error means that you don't have any authentications set on your device (or more precisely you are using the default authentications which is admin without password). Documentation can be found here. This settings is optional and the REXYGEN can run without it.

First of all, please update your REXYGEN to the last public version according this manual. We are aware of incompatibility issues between REXYGEN 2.50.9 and newer versions of REXduino caused by updating communication protocols.

Please let me know if the update helped,
Jan