You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was having trouble with an OpenLog a couple weeks ago. Nothing was getting logged. I reformatted with FAT16 using fdisk on Debian GNU/Linux and still...nothing. I then accessed the OpenLog through a MAX232 chip. I found it was dropping me right into the command console. I think then I tried creating a file and got this message: "Failed to create config file!Too many logs."
A web search for formatting FAT16 partitions showed me something I failed to do: Create a DOS filesystem on the new FAT16 partition.
A more helpful error message would be nice in this case. But a note in the documentation would suffice. Or, since you provide a link to your GitHub page, this bug report may be enough for people with the same problem. (That's why I came here in the first place ;) )
The text was updated successfully, but these errors were encountered:
Good find/fix! Thanks for getting back to us with your solution. I've added the following near the top of the datasheet:
The microSD card can be any size from 64MB to 16GB. Before using OpenLog be sure to format the card either FAT16 or FAT32. We recommend using windows to format your card. If using Linux, be sure to create a DOS filesystem after formatting the card.
I was having trouble with an OpenLog a couple weeks ago. Nothing was getting logged. I reformatted with FAT16 using fdisk on Debian GNU/Linux and still...nothing. I then accessed the OpenLog through a MAX232 chip. I found it was dropping me right into the command console. I think then I tried creating a file and got this message: "Failed to create config file!Too many logs."
A web search for formatting FAT16 partitions showed me something I failed to do: Create a DOS filesystem on the new FAT16 partition.
A more helpful error message would be nice in this case. But a note in the documentation would suffice. Or, since you provide a link to your GitHub page, this bug report may be enough for people with the same problem. (That's why I came here in the first place ;) )
The text was updated successfully, but these errors were encountered: