@hamnet Great! If you are familiar with C++ and Arduino, stick to it! I'm not familiar with the Paper product but the display consumes no power when the image is static, and you can run it on a USB cube power supply. The other M5Stack products have an LCD display with constant current needed to power the backlight. As I am not familiar with PAPER, I guess I'm "deflecting" a little! M5Stack sometimes lacks in documentation and that's why this Community exists. Try this other Community post! https://community.m5stack.com/topic/2892/m5paper-shutdown-deep-sleep-wakeup/3

Hi Felix. Thaks for your repply, and sorry for my late resonse. I had some issues logging in again after I created my account. Your links got the example code to at least build. But once uploaded to the board I never get past "Connect Error" in the setup. I have two hats, and two M5StickCPlus, and same issue on both. So guess I still have some troubleshuting to do.

Hello @yuza_tipo there is a lan.get_ip_config() function which returns the current IP etc. as a 4 tuple like this ('192.168.x.x', '255.255.255.0', '192.168.x.1', '8.8.8.8'). I also found there is a lan.set_ip_config() function but when I feed the above 4 tuple as argument I get an error that the function takes 5 positional parameter, but only 2 are given. I tried many other ways to format the 4 arguments, but all I got are different error messages. Thanks Felix

I am designing a GPS disciplined oscillator and the goal is for a short-term stability to be better than 1 part per 10 to the 9th cycles. The uBlox GPS has 2 counter inputs. Approximately every second (1 measurement cycle) the GPS reports the count and the time of the last rising and falling edges on the counter inputs. These are reported to the nanosecond (10 to the -9 seconds). By subtracting the previous count and rising edge time from the current measurement you will get the number of counts and the time difference. From this you can calculate the frequency to approximately 1 part in 10 to the 9th. In the actual implementation you do this over a period of hundreds of seconds. In the example I gave the single precision calculation was in error by over 46 milliseconds. In a 1 second measurement this is approximately a 4.6% error! The problem arises because you are adding a very large number (5.31316281 x 10 to the 5th) to a very small number (657346 x 10 to the -4) and you need a result accurate to 9 decimal places not 1 decimal place. In the actual calculation these numbers were first scaled by a factor of 1000 and 1000000000 respectively so they were even larger numbers to start with. This code runs fine on a Pyboard with their double precision code. I would prefer to use a Core2 unit which has a much nicer display and form factor than the Pyboard and its display. I believe the effort to create this new image is as simple as changing 1 definition to tell the compiler to compile code for double precision instead of single precision. If you interested here is a link to an individual who did this for the PI Pico. https://forums.raspberrypi.com/viewtopic.php?t=319525 For someone with the correct tools, knowledge and the source it appears to be a relatively easy task. Tools and knowledge I don’t have. In this case most of the effort would be in making people aware of the other firmware image and making it available for download.

@kawabatapaper said in M5Station-485: A guide to the Station will be coming!

Hello @Hamnet it takes time for a new board to be included in Arduino and subsequently into PlatformIO. So when M5Paper came out the easiest way to create an M5Paper PlatformIO project, was to take a similar board, in this case M5Stack Fire, which was already available. (The key here is that both M5Stack Fire and M5Paper use PSRAM.) And later on, I guess, M5Stack engineers simply forgot to fix that. Thanks Felix

In this example two pages with the same layout, but in practice this is of course not necessary: As an extra example from practice (one of my first programs in UIFlow) with two different screens:

Hello @fried_chips thank you for reporting - you made me curious so I checked the traces (with a multi-meter) on my Timer Camera board and the Power/Wake button (through a diode) is connected to GPIO37 as mentioned in the documentation and as it is on the schematic. However you are correct in that it doesn't work. The reason is GPIO34-39 are input only GPIOs and they lack internal pull-up or pull-down capabilities. And since there is no external pull-up resistor on the board, reading the Power/Wake button doesn't work. In my case it always reports LOW. That said, after adding an external pull-up resistor, I can now read the Power/Wake button state correctly through GPIO37. Unpressed it reports HIGH (external pull-up) and pressed (connected to GND) it reports LOW. BTW: I did try to read GPIO38, as you suggest, and interestingly it works, however the states are the other way round. Pressed reports HIGH and unpressed reports LOW. Looking at the schematics I think it 'works' because no battery is attached to my board. And GPIO38 is used to read the battery voltage. So my conclusion is that the documentation is correct, but unfortunately on the Timer Camera board the required external pull-up resistor has been forgotten. Thanks Felix

Hello, It helps to select a different color first. Then you can still make copies. An annoying detour indeed.

Hi, It's also my experience that it doesn't always work if you have multiple switches, input fields, buttons, etc. I see "Switch 4" with you, so I assume that there are multiple switches. The solution I used in one of the projects with multiple input fields is to apply custom variables. Then suddenly it works! Hopefully that will help you too.