@andrew-winton tday I had a chance to test AIN with raspberry pico 2 W and it is detetcting ok

RaspberryPico2W with AIN

@robski :

Edit: The address conflict is not with the ENV IV units, but with something else - either way I must remain on UIFlow 2.

I checked with two additional controllers: Atom matrix, and Stick C plus : The same issue.

However, odly I am able to "fool" the controllers for a brief timeperiod by going through a very particular sequence in Block editor:

add a PaHUB with some other sensor unit assigned to it in channel 0 of the HUB, and run the script - ALL OK Physically replace the sensor (channel 0) on the HUB with the thermal unit, but assign it directly to the i2c bus, and run the script - ALL OK Add several other sensor unit to the Pa.HUB (but keep the thermal unit assigned to the i2c bus, and run the script - ALL OK (runs several times without an issue, and all sensors respond correctly)

After saving the project and relaunching UIFlow 2, the script does not run, with this message: "Thermal unit maybe not connect"

Quite confused by this.

@Kris said in AIN 4-20mA Is this correct?:

@fkarner Tak mam podłączone i odczyt wynosi ciągle zero

this works for me:

ain1.PNG

ain2.jpg

@NickMaddock Hi Nick,
sorry that i do not have a direct answer to your question. I have a question about the Roller Unit and did not get any response from the M5 Team yet. But it should be easy to answer for your: Is the Position resolution in Position mode restricked to the encoders incremental resolution or interpolated to a finer level? I'm interested in the product but would like to use is for some kind of gimbal application (mirror steering). Therefore the resolution of the encoder might be too coarse. The datasheet of the sensor states 12bit for incremental output but 15 bit using the serial interface. Unfortunately the videos from the roller unit seem to show 12bit resolution.

The question is: what is the minimal achievable setting resolution in position mode?

@ChrisFSB Any ideas here folks? Thx!

@Arn_8
Problem fixed !
Thanks !

@Elliptic3612 @matthewchan @SB12345 @sqbaczek
We have fixed this problem, please wait for the next version of UiFlow2 firmware

@HappyUser is there a way to operate them bot? I'm using it with platformio so maybe is easier to achieve that micropython?

@kuriko

Ohhhh, what a pity!

Thanks

I was also struggling with drift and negative values. I also receive a traceback error when I invoke tare(). The function works, when I go in and edit the python code (removing the parathesis). I suggested an update to the GitHub.

I found the miniscale.py definitions in the firmware uiflow-micropython project. It has more details on the implementation of object class.
https://github.com/m5stack/uiflow-micropython/blob/master/m5stack/libs/unit/miniscale.py

Thanks a lot for the fast reply. Very helpful.

@teastain Thank you - I had misunderstood what the Z was for. Because on the ky040 the middle pin is for the "switch" functionality (i.e. pushing down on the encoder) I assumed it was for this. I realise now that I need to treat that as a button and take it off to a different pin, which I know how to do.

Thanks for your help!

Hi,

Yeah I guess I'm in disbelief, or maybe hoping it is a mistake. Seems a bit odd to design something that is meant to work on a CAN bus and then stop it from working as a bus.

Suppose my only option is to open it up and try to remove the termination resistor.

I could use the I2C bus, but I see they have put pull ups in to break that bus as well.