After consulting with M5Stack tech support they indicated the only way to re-mount a card after it has been ejected and re-inserted is to reboot the device.

It is definitely something to do with the size of the program. Once it reaches a certain size it will no longer run. All I have to do is delete anything (reducing the size) and it will run again. I provided a sample of my code to tech support and they are working with engineering to investigate.

Thanks for the feedback. After flashing the Core2 to a different version. It wipes out all my apps and leaves behind a Color app and temp app. Since they don't show in the Device File manager I think they want them left alone. I assume the color app could go but not sure how to delete without Device File Manager. The "Temp" app probably needs to stay. Your suggestion did get me to look a little closer I had spaces in my file name (should have known better) which resulted in the Device file manager splitting it into "3 Files". I assume that it created 2 empty files and actually 1 real file with my app. Anyway couldn't delete them so re-flashed to clean it up. When "Run" it, with additional code, it causes the device to reset without ever seeing the app run. If I "Download" it, after adding some additional code, it does not reset the device and appears to run. Might be something with RAM. Tried a different Core2 with same results. Here is a pic of the filename and the way it split it. If you have any additional suggestions that would be great.

Also have you seen instances where the buttons along the bottom of the screen don't process their "Press" code as well as the soft "Button" you place on the screen doing the same thing. I will have things working properly and not touch the code for those routines and next thing I know they aren't processing anymore. If I through a label into the press routine, for output, I don't see it change either like the button press is not being recognized. Thanks again

I have a program that I don't consider excessively large. It mainly has 6 different screen layouts along with that overhead. The file size is 97K. It has reached the point that it runs as is but if I add anything to it (ie: If I change the wording of a label) will not run and the Core2 resets itself. I have tried from v1.7.0 up to 1.7.2 with the same results. So, have I reached size limitation? If so how do I tell available space and what is being used? If anyone has any suggestions it would be greatly appreciated. I am using Blockly which is translated into 477 lines of Python.
Thanks for any insight.

On the Grey Core UIFLOW there is a volume command but on under the CORE2 Beta UIFLOW I cannot find one. Here is a screenshot. Let me know what you think. Thanks

Under "Speaker" in UIFLOW there is the ability to play wave files but the next step is to obviously change volume. Does anyone know how to change volume on a Core2 in UIFLOW or Python?

Just a follow up. I contacted M5Stack tech support and they told me the old modules have pins that are 2.5mm and the new board has pins that are 3mm. So in theory I have the newer board but it separates from the Core2 fairly easily. Meaning the pins are probably making contact but not great. Will have to get longer screws and screw the module down to ensure good contact. For reference to separate from the Grey Core it is very tight and I usually use a screwdriver. I measured and the Grey Core lets the pins seat approximately 1mm more than the Core2. Here is a picture showing how to measure pin length.

Ok, I have figured out how to detect when the card is ejected by writing a file within a try - except but once the card is out I have not figured out how to get it re-mounted in code. I can get it re-mounted by resetting the CORE2. The scenario would be you eject the card and the CORE2 detects it and notifies the user to insert a new card. Once the card is inserted the CORE2 would automatically mount it and make it available for use. I am sure there is a simple command that I am missing.
Thanks for any help.

try:
with open('/sd/IsCard.txt', 'w+') as fs:
fs.write('Test Write')
with open('/sd/IsCard.txt', 'r') as fs:
label1.set_text(str(fs.read(10)))
label0.set_text('Card has been read')
NoCard = 0
except:
label0.set_text('Except0')
NoCard = 1
label0.set_text('Card Not Installed1')

By your website I meant the m5stack.com website. In the previous post it was indicated that the new stock would have longer pins. So, I was just checking to see if maybe I ordered right during the transition and if I order another it will have the longer pins.

This is a follow up on the post from a month ago regarding compatibility with the GPS module and the Core 2.

On Dec 24th I ordered the u-blox NEO-M8N $26.39 module from your website. It works fine with the Grey Core. I recently received the Core2 and the pins are too short to connect. So, has something changed since I got this module? In addition what back will need to be utilized and how does the battery connect to the mother board with the GPS module in between the battery and the motherboard? I assume that the M5GO Battery Bottom2 feeds power through the interface connector to the motherboard to overcome this problem? Is this correct?
Thanks