@gaviota I confirm that I found the problem you described also on the on-line version 1.7.0 of UIFlow. Thanks to your trick (click on each block again in Black-Maker will fix the proper rendering once imported into UIFlow) I was able to rescue.

@m5stack:

On the Core display I am a able to select COM.LTE as additional connectivity as shown here.
BUT the next picture (I guess taken from M5Burner configuration, right?) is different in my case because it shows only WiFi, while the APN section is missing .
The final result is that if I select on the Core display COM.LTE and reboot it fails to connect. .
Please note that the modem is working fine, since I'm able to drive it with my UIFlow code (via AT commands) moving data back and forth perfectly.
My ultimate need is to use the UIFlow MQTT client not through the WiFi but natively through the mobile connection.
THANKS!

I'd like to show that the UIFLow 1.7.0 or 1.7.1 configuration mask does not present any panel related to  to be compared with the similar one posted on Twitter

@m5stack thanks but then I'm not able to follow the procedure shown here on Twitter (showing from M5Burner, right?) aimed to pass the APN to the module. Currently I'm on UIFlow 1.7.0.
I posted a topic also here Can you help me?

@m5stack said in UIFlow 1.7.1:

COM.LTE

Is the COM.LTE connectivity supported only in Core2 and not Core (Basic)?
If so, when extended also to Core?

Re: UIFlow 1.7.1
Hi, I need to configure M5Stack-Core to use COM.LTE connectivity as shown here
Currently my Core mounts UIFlow 1.7.0 where that option is available in the device setup menu, but once selected did not work

1. Does it work also with Core or just on Core-2 ? Can I hope also to get it work on Core?
2. The M5Burner configuration of 1.7.0 does not offer that same extended option with COM.X as shown in the link above; Shall I upgrade to 1.7.1?
3. Where can I find the entire step-by-step setup procedure (shall I act on M5Burner as well as on device setup?)

Thanks!

@ciniml could you please explain the new Cellular UIfow blocks and give an example on how to use them in sequential order?

I also saw the Soracom m5f example and I wonder if the flow can start as it did, checking the SIMstate without setting any UART communication in advance?

If I start running just the first two instructions, shall I expect returned True as you?

I'm chasing who can help me in using the COMx.LTE module with those UIflow methods

Thanks

@teiafra said in SORACOM 3G Module support in UI Flow:

@ozbk Thanks a lot for sharing the example.
Could you please provide explanation or point me where each cellular block of UIFlow are described to understand their usage and succeed to manage the COM.LTE module since from its first installation onto M5S-Core?

In what order those blocks are supposed to be called in a more general flow? E.g do I have to start with cellular.init (you did not use it and instead call for restart after SIM is checked)

I complain that that entire palette of blocks is not documented at all :-(

I continue to dig and compared your Soracom flow with the example on SI800 available here.
If I may guess many blocks of module.CELLULAR library, the biggest doubt is about modem initialization and communciation ports setting.

The SIM800 flow clearly set the UART rx/tx channels in the init function while I do not understand in your Soracom example if the cellular.init or cellular.restart block of the library avoid to do this UART setting. Do the Core and the Module communicate each other automatically?

Similarly, Arduino code to drive COMx.LTE also sets up the tx/rx as reflected by the dip switches: does the Cellular UIflow blocks avoid the user to care of it, instead? That would be wonderful!

What difference is between "send" and "sendline" function block?

Any help is really appreciated!!

@ozbk Thanks a lot for sharing the example.
Could you please provide explanation or point me where each cellular block of UIFlow are described to understand their usage and succeed to manage the COM.LTE module since from its first installation onto M5S-Core?

In what order those blocks are supposed to be called in a more general flow? E.g do I have to start with cellular.init (you did not use it and instead call for restart after SIM is checked)

I complain that that entire palette of blocks is not documented at all :-(

More specifically I need to know if the Arduino code downloadable here can be alternatively implemented by means of the UIFlow blocks belonging to the Cellular palette and, if so, I'd be interested to know how.
Thanks