administrators

Hello @asunc,
absolutely no problem. The Axon is running a debootstraped arm64 Debian with added repository of our packages via which we publish fixes and new versions of our software.

Best regards,
Martin

Hello @asunc,
the active development of Neuron line has finished although the support will be for many years to come. The current line Axon has LTE models: Axon S165, Axon M265 and Axon M565. Those are currently in public testing phase, you can request them at info@unipi.technology.

Best regards,
Martin

Hi @dealah-in-kóma,
there are basically two ways of achieving that. Both of them require connecting the Inepro energy meter via RS485. The difference is in who will be responsible for polling the Modbus data from the device.

1. The Evok way
   Evok can be configured in a way, that it will poll general Modbus devices. See https://github.com/UniPiTechnology/evok/blob/master/etc/hw_definitions/CUSTOM MODBUS DEVICE.yaml
   The updated data are available via standard Evok API.

2. The Node-RED way
   You can poll the Modbus device in Node-RED directly via node-red-contrib-modbus https://www.npmjs.com/package/node-red-contrib-modbus

Personally, I would suggest you the option 2, since configuration in Evok is not easy. For configuration you need a Modbus registers map for the given device, that can be found in the documentation from the vendor. Please note, that there are several HW and SW revisions for the device and you need to use the correct documentation. The latest one is here: https://ineprometering.com/wp-content/uploads/2019/04/PRO380-user-manual-V2.18v6.pdf and the Modbus registers map starts from page 27.

Best regards,
Martin

Hi @dirk,
which access to the IOs do you use? Which OS image? The Evok has some troubles running on the Raspbian Buster and the fix is currently in the making.

Best regards,
Martin

@roberts_lando In the next release axon-kernel we include more modules (at least 1wire devices)

If there are some missing modules, you need to compile it.
On Axon (or generaly any arm64 platform) do:

apt install build-essential git 
git clone https://git.unipi.technology/UniPi/axon-linux.git
make unipi-axon_defconfig

Now you can change kernel configuration to desired state

make menuconfig

Compile new modules

make modules

You can compile on amd64 platform using CROSS_COMPILE

make unipi-axon_defconfig CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64
make menuconfig CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64
make modules CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64

@boy-lenssen Yeah, that's something we are working on to protect bricking the units during the FW upgrade process. If the RUN led is dead, send it to us so we can reflash the FW.

Using Owfs with kernel modules ds2482 doesn't work well.
It requires to disable ds2482 in devicetree.
Insert this patch

fdt set /soc/i2c@01c2ac00/w1master@18 status "disabled"

into file /boot/boot.cmd, call

mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

and reboot.
If you have our new kernel, there is not file /boot/boot.cmd
In this case copy attached file attached file 30-disable-1wmaster.conf to directory /etc/bootcmd.d/src
and call

  cd /etc/bootcmd.d; make force; reboot

The files has been moved into a new repostirory: https://repo.unipi.technology/debian/ The FW tool for extension can be found here https://kb.unipi.technology/files:software:tools:00-start#extension_firmware_update_tool

Can you provide screenshot where we could see the configuration of the PI controller with all the parameters?