@endurojunky I am glad you got it to work. :)

I couldn't get my RFID unit working in the beginning too, so I used an Android app for testing. That app tells you what keys it used to access the individual sectors. I then google for rfid default keys and found the link I mentioned. The UIFlow block doesn't allow to change the keys, so I looked at the source code of UIFlow. That source unfortunately wasn't update for two years, but the RFID unit is in there. There I found the default key being used: https://github.com/m5stack/UIFlow-Code/blob/master/units/_rfid.py#L284. This also helped me to find out how to set the keys.

@ramaker please clarify which module you are using for the dc motors, is it the go plus or lego as there are a few that control dc motors, once I know the one I should have a better idea of which cables you need

Thank you for the answer.
I will try the PaHub.

K.D.

This problem is solved now. The following instruction needs to be updated:
https://docs.m5stack.com/#/en/quick_start/unitv/v_function
The instruction does not specify what driver is needed to communicate with hardware. It came out that the user needs a different driver than the one used for M5Stack core products.
In case anyone has the same problem, please make sure you have the newest VCP driver by FDTI installed on your machine. My advice is to use their website to check out the latest version:
https://www.ftdichip.com/Drivers/VCP.htm

@skink said in M5Paper:

hier kannst Du sie bestellen !! "https://eckstein-shop.de/M5Stack"

eckstein-shop.de: Delivery time : approx. 61 - 63 days

Still 8 in stock for immediate dispatch at Distrelec.

@sodoku
I have to admit that I'm an absolutely newbie so I was not aware of this standard behavior for all 360s but really helpful to know :-)

Hi, I just ran some test and the LED doesn't work if the lithium battery in the base is below 3.8 volts. the microprocessor wont start up and so the M5StickC can't communicate.

Is this problem already solved?

It seems to be a mistake in the sample program.

Although, the variable 'count' in the function i2c_transmit() should be global, it is interpreted as local.

I modified the function i2c_on_transmit() as follows:

def i2c_on_transmit (): global count count = count + 1 print ("on_transmit, send:", count) return count

Then, it worked well.

Hallo @felmue

I have tried it and it works, thanks for the quick help!!!
I am glad that I can finally continue working on my program :)

In this situation, we haven't met. our all firmware is used 240MHz default. maybe you could check it does related to your program.

Maybe they are busy using it.

@m5stack I have tried Tag36H11 images for numbers and this makes no difference. UnitV with M5Stack Fire and UIFlow did not decode the images. I did not make any alternation to my UIFlow code. Did you test this software?

Hi Van

If you like to experiment there is a magnetometer BMM150 in M5Core Gray, Fire and M5GO. Also the M5StickC ENV Hat contains the same BMM150. But I guess you already knew that.

Cheers
Felix

this bug has been fixed.