@сергей said in Why is support not responding?:

Why is support not responding? I asked a few questions in the Russian-language forum thread and now a few days have passed and someone has not answered anything. I have just started learning m5stack and the advice of professional developers is important to me. Which is hard to answer. If I asked something wrong, at least answer yes or no !!!!!

@сергей said in Why is support not responding?:

Why is support not responding? I asked a few questions in the Russian-language forum thread and now a few days have passed and someone has not answered anything. I have just started learning m5stack and the advice of professional developers is important to me. Which is hard to answer. If I asked something wrong, at least answer yes or no !!!!!

Hello, I haven't seen the Russian Moderators in a while. I expect they are all busy trying to work out how things work. Please be patient.

it works! thanks =)

@uli said in Port "E", Port "Custom" and Pogo:

Pogo pins, they are only for charging, right - using them as interface is not possible?

According to the product page, the pogo pins can also be used for I2C (GPIO 21 and 22) on supported devices (BALA)
https://docs.m5stack.com/#/en/base/m5go_bottom?id=pinmap

I've loaded the M5Stack library and the ESP32 library from Espressif. When I try to upload my program I get this error message trail:

ash: line 0: [: too many arguments
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory
exit status 64
/Applications/Arduino.app/Contents/Java/arduino-builder returned 64
Error compiling for board M5Stick-C.

Thank you for trying to help me!

Just wanted to provide an update on this topic. I too am having issues with HTTP POST to an endpoint on my local network. I'm trying to program a simple on/off remote button for my Hyperion ambient lighting setup that is behind my TV. This is my flow...

0_1612103278676_Screen Shot 2021-01-31 at 9.26.56 AM.png

First I need to switch to an instance before I can send the on/off command. When I press button A on the M5StickC, it completely locks up the device during the HTTP POST command. I cannot even short press the power button to reset it. I have to hold down the power button for 6 seconds to fully power it off, then I can power it on again. Same exact thing with the M5StickC+. The M5Fire is a little better. It doesn't lock up, but I still can't get the HTTP POST to be a success or a fail. I would expect some type of failure if it didn't work properly... but instead I get nothing.

I'll continue to troubleshoot. It might be due to the IP:port in the HTTP request, as my test with https://httpbin.org/post works fine and it doesn't use a port. I'll let you know if I figure anything out.

that's very very unusual, have you tried to burn the new firmware using m5stack burner to see if it solved the issue?

hello, could you please attach a screenshot of your serial monitor to understand more? have you made sure that the baudrate is correct?

Hello, as this is seeedstudio product, it doesn't natively support m5stack software, you might need to modify their software to make it work on the m5stack device.

Thank you! Nice community you have here!

Hello @braddo

there are Functions in UIFlow.

Thanks
Felix

Hello @veryalien

nice work-a-round. Hopefully it will be fixed soon though.

Thanks
Felix

@keesjan With micropython, port 22 works fine, and as expected:

CDS_PIN = 33
TX = 19
RX = 22

As an aside, the idea that the labeling of the pins is "oriental logic" shows an unawareness of the history of rs232 and is a bit insulting. The question of what to label the pins depends on whether the manufacturer thinks of the device as DTE or DCE: StackExchange has a good explanation of the history.

In particular:

'some manufacturers try to "help" by effectively labelling their DTE equipment as if it was a piece of DCE. They mark their data input pin as Tx so that user just connects "Tx" from the external device (which, if it's DTE, will be the data output from there) to the pin marked "Tx" on their equipment (which they know is an input). Thereby allowing them to say "just connect Tx on your device to Tx on our equipment". They think they are trying to help, but such labelling often just adds to the confusion.'