Hi @klaschudi,
can you please post the exact commands (or tutorial) which you followed to install docker? It is not exactly clear just from the error output. Thank you.
In general, Docker is able to run on Patron.
Hi @klaschudi,
can you please post the exact commands (or tutorial) which you followed to install docker? It is not exactly clear just from the error output. Thank you.
In general, Docker is able to run on Patron.
Hello @FabioIT,
the development of Codesys support has been dropped altogether. The Codesys can be still used on Neuron via ModbusTCP. The Unipi 1.1 doesn't have IOs accessible via ModbusTCP, only scattered over I2C, GPIO and so on - nothing easily configurable.
Best regards,
Martin
For the record, this issue is currently being dealt with over email.
Martin
Hello everybody,
the upgrade to bullseye is planned for March.
Best regards,
Martin
Hello @juergschwarz,
none of the outputs are capable of being drived by PWM signal. The analog output has a filter + amplifier to create smooth(ish) output. This cannot be bypassed.
Other outputs are the relay outputs - and if your frequency is not in tens of seconds (or better in minutes), then I would not advise to use PWM to drive them.
You can try using some I2C expander connected to the external I2C bus.
Best regards,
Martin
Hi @Tase,
you are trying to use variable (instance of a TPG function blok) which is in another function block. This is possible, but it is usually not good idea, since you would broke the "encapsulation" provided by the function block. What might be better is to create a HMI function block template and use it in the HMI template.
Best regards,
Martin
Hello @M1che1,
this package is not included in our images, only our is: https://flows.nodered.org/node/@unipitechnology/node-red-contrib-unipi-evok
The packages can be added later of course. Using another OS image (such as Raspberry Pi OS) can be harder to configure - you need to install Evok. The Ubuntu Core OS is not supported and probably won't work because of the different package names and versions.
Best regards,
Martin
Hello @M1che1,
the Unipi 1.1 has been designed for needs of Raspberry Pi 2. Since then, the RPIs got more power hungry and the internal connections might not be suitable for powering both the RPI and the Unipi 1.1. That depends on what RPI you are using and what you are running on the RPI. It is definitely safer to use separate power supplies.
Best regards,
Martin
Hello @JakubSzlaur,
we are experimenting with Balena for Unipi Neuron. There is already a public support, we just don't have any examples of how to use it: https://github.com/balena-os/balena-raspberrypi
The Unipi Gate doesn't run on Raspberry Pi, but rather a Rock Pi. There is no support or work in progress for this platform we now of.
Best regards,
Martin
Hello @daminou53,
we are working on mirroring to Github, it should be ready within few days, if not today:)
Best regards,
Martin
Hello everyone,
we have just released updated Zulu kernel, which solves this particular problem.
The problem has been in the memory lock, which overused the swap, even when the swap is off on all our OS images. This has been fixed in kernel 5.10.17+. The new kernel is 5.10.35.
Whole suite of OS images is currently being generated and within an hour uploaded to the Download section
Thank you for reporting the issue nad have a nice day,
Martin @ Unipi
Hi everyone,
this issue is new to us, although we have experienced some performance issues with our kernel module - it might be related to what you are experiencing. I have contacted both of you over email with more details.
Thank you and have a nice day,
Martin
Hi @L-E-F,
it looks like you have selected the child profile. Try selecting the main profile, right below the "System":
Best regards,
Martin
Hi @romainletendart,
the serial number is available in the hostname of the PLC, which is set by the unipicheck service.
The serial number is unique per model, e.g Neuron S103, Neuron M103 and Axon L505 can have serial number 10.
Best regards,
Martin
Hello @HPC,
I am not sure if I understand the problem. Can you please specify what is connected to what on via which protocol / interface?
Thank you and have a nice day,
Martin
Hello @wzp, we don't have such thing, but you can find STEP models or CAD drawings for our products in the download section: https://kb.unipi.technology/en:files:products:00-start
Best regards,
Martin
Hi @lukas009,
it is the same issue. We will release Bullseye OS images once the support for all products is done. Looks like it could be next month.
Best regards,
Martin
Hi @knebb,
we are currently working on the Bullseye packages for the Unipi PLCs, but some important are still missing. The official release from our side will be after the official release of the RaspberryPI OS.
Best regards,
Martin
Hi @knebb,
you have verified, that the HW is working and returns correct value via standard tool. Checking and fixing your code is unfortunately beyond the scope of the free support.
Thank you for understanding and have a nice day,
Martin
Hi @knebb,
the firmware has been updated on our Knowledge Base as well: https://kb.unipi.technology/en:files:products:05-sensors:iaq
Martin