@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

If you change size to the rectangle shape, you do not see any effect on the UI preview.
The dimensions actually change whan you run the UIFlow code, but the "what you see, what you get" of UIFlow is totally faulty

Hi,
where are documented and described the flow blocks under Modules/Cellular.
Can they be used to drive the new LTE module based on SIM7600G? https://m5stack.com/collections/m5-module/products/com-lte-modulesim7600g

Hi
I'm pretty new and becaming familiar with Arduino IDE to program M5Stack-Core.
I was wondering if. before flashing your code on the device, it was possible to test the code on a emulated SW environment and avoid many try&errors.

Perhaps it won't be efficient in speed but at least allows you to make a first debugging.

Any tips?

Thanks

Thanks a lot, I rescued this limitation (which makes the mqtt client not compliant to the standard) by setting properly the server side

After several tests it seems that MQTT client implemented with UIFlow is not able to manage any subscription to topics built with wildcards.
In particular the single level '+' wildcard (e.g. 1st_level/+/3rd_level) does not work. Also multi level with '#' does not work as reported here in UiFlow MQTT topics
Who can confirm that also '+' wildcard is faulty?

Thanks,
later on I found that in UIFlow (top right corner) there is a button "Manager" that, when pressed, opens a Resource Manager window with a double usage: Images and Blockly. If you select Blockly you get the software app inventory that allows you also to delete the app you want.