Topics created by MikeyH

Hi Mike, great question, makes perfect sense. Can you please provide more details about your project? Namely: Do you need the tasks to execute in specific order? How long does it take to execute the individual tasks? I don't expect it takes more than a few milliseconds, but please confirm. What is the base tick? What is the factor of Modbus driver? Can you share your project source files? Or at least some minimum example? Jaroslav

Hi Jaroslav, Trying what you suggested has mixed results. I remembered something you showed me awhile ago and looked at the log for just the driver read/write. See below for what the log is saying. This was done with no writing and three registers being read, 0x1000, 0x1010 and 0x1020. 0x1010 seems to return the same value as 0x1000. This shouldn't be the case, 0x1000 is correct though. I changed the read order in the configuration settings and 0x1010 started reading correctly, 0x1000 now does not and returns the same value as 0x1010. It seems hit or miss whether 0x1020 reads the correct value or not, the longer I run the simulation the more chance that 0x1020 reads correctly. Why would changing the read order have an affect? Could the CRC errors could also be causing this? The last byte is missing or being cut off. I still receive the correct value though. 3 registers being read (0x1000, 0x1010, 0x1020) 1 register being read (0x2010) Cheers Mike

Hi Mike, I see. In that case the simplest approach is to use the TSE block (three state element), which moreorless combines two comparators with hysteresis. Kind regards Jaroslav

Hi Jaroslav, No, not causing an issue as such. Setting the LIN block in such a way fixes the problem and allows the fan to operate correctly. Cheers Mike

Ok, thanks Jaroslav. I'll use a combination of the ALB and what I currently have to achieve both. This way I'll get both live HMI and logged alarms. Cheers Mike

Hi Jaroslav, Thank you for the help. I will give that a go and let you know what happens. Cheers Mike

Hi Mike, unfortunately the REXYGEN runtime won't run on an ESP32, however you can integrate it with other REXYGEN enabled device using REST API and exchange data. Have a look at example "0302-11 ESP8266 REST API", which is originally meant for ESP8266 - I believe that the code will work also for ESP32 (with minor tweaks - don't have any ESP32 on my desk available for testing). Let us know about your progress. Regards, Tomas

Hi Jaroslav, That’s awesome, I will try this out during the week. I’ll let you now how it goes. Cheers Mike

Hi Jaroslav, Thanks for the reply, yes this was the case. With a bit of scaling added it works fine, only with slight loss of resolution. Not enough to cause issues tough. Cheers Mike

Hi Mike, not sure if I understand correctly what is the issue. Can you provide more information? Can you share screenshot of the project part and a sketch of desired behaviour? Is the issue about setting binary inputs sequentially which produces more logs to be written? Thanks. Cheers, Tomas

@jaroslav_sobota no problem

Hi Mike, thanks for clarification. I have no experience with that, but the Maxim MAX1721x with 1-Wire interface seems to be ideal for such a project with the Monarco HAT. Jaroslav

An update to the above. I'm now very sure I had a bad batch of sensors, it turns out I'm not alone. Over people have seen the same thing having bought sensors from certain websites. Be careful when buying 1-Wire sensors as it seems there are cheaper, not so reliable ones flooding the market. Cheers Mike

Thanks Jaroslav, So using a not block would be the preferred way for making it work for cooling. Cheers Mike

Hi Jaroslav, I will email you the documentation for the device. Cheers Mike

Hi Jaroslav, Awesome, thank you for your help. Cheers Mike

Hi Tomas, Thank you for your help. I understand how it works now, what you provided is where i wasn't sure what to do. It makes sense to me now. Cheers Mike

@mikeyh Did you mean analog inputs? The accelerometer outputs range from 0 to 3.3V... In general, it will work. Note that you'll not fully use the resolution of the A/D converter on the Monarco HAT and you'll be limited to 2 axes as the Monarco HAT has 2 analog inputs. If you meant digital inputs indeed, then it won't work. Logic high voltage of the DIs on the Monarco HAT is 3.5 V to 30 V. Hope this helps, let me know. Jaroslav