Hello,

Many thanks for library.

Just little feedback:
I have tested the saintsmart shield with the demo of arduino code, works.
I have tested (only display), the code @ Nov 06, 2016 12:21 am, works.
I have create new shield using the same schematic of saintsmart*, i have just added FET for backlight.
I test my new shield with arduino demo code, works.
I test with code @ Nov 06, 2016 12:21 am, not works !!!!
I have modified the library with the code from last post mkcreta, it's works.

Thanks
Olivier
* Stupid shield, not possible to get orther port....

Hi Neil,
My memory of all the steps needed to get an SD card going are long gone. And in any case I used them in simple SPI mode, so all those advanced access settings are different.

The repeated error 241 at initfilesystem is a bit odd, you should not get that, but I dont know if its significant.

Somehow I doubt really rare errors like you get are due to code, except possibly a marginal timing issue.

I would be more suspicious of power supply glitches. You do know that the cards themselves draw high pulse currents during the write cycles, up in the several 100 mA region ? That can cause problems with supplies. Even 1000 uF bypass may not be enough, when you work out the voltage drop over the current pulse time. You need very "stiff" regulators. FETS to switch the output can cause the same problems, its safer to switch the input side, if you go back to that idea.

Thanks Adrian,
Unfortunately in the latest population of boards, i cannot cycle the SD card power. On older boards I had a FET that allowed me to do this but (foolishly) decided it was not necessary. Because this issue is so intermittent, its hard to fault find, and I was hoping someone would spot an issue with my code. SD cards for me are a bit of a black art.

Reaching back into dark history...

I too had rare problems getting SD cards to respond. Maybe not the same failure, but effectively preventing access. My solution at the time was to use a card supply regulator which could be enabled and disabled by a processor port pin.

Never had any problems after that, but I have no idea whether the recovery cycle was ever tripped in the field. What one could have done was to log a failure to the card, after getting access back, but I never thought of that, and in any case I only very rarely had access to the cards once installed.

happy to help KenHorse...

[quote:3478a5d77f="six1"]made a loop for month and result is:

Search: repetition #3 of Sunday in 1-2019 is 20-1-2019
Search: repetition #3 of Sunday in 2-2019 is 17-2-2019
Search: repetition #3 of Sunday in 3-2019 is 17-3-2019
Search: repetition #3 of Sunday in 4-2019 is 21-4-2019
Search: repetition #3 of Sunday in 5-2019 is 19-5-2019
Search: repetition #3 of Sunday in 6-2019 is 16-6-2019
Search: repetition #3 of Sunday in 7-2019 is 21-7-2019
Search: repetition #3 of Sunday in 8-2019 is 18-8-2019
Search: repetition #3 of Sunday in 9-2019 is 15-9-2019
Search: repetition #3 of Sunday in 10-2019 is 20-10-2019
Search: repetition #3 of Sunday in 11-2019 is 17-11-2019
Search: repetition #3 of Sunday in 12-2019 is 15-12-2019[/quote:3478a5d77f]

Those are the results I obtain as well (although I did change the printout to reflect the US standard of M-D-Y

thanks again for your effort and assistance

[quote:5abc1eec95="six1"]Search: repetition #3 of Sunday in 12-2019 is 15-12-2019[/quote:5abc1eec95]
No one of your shown code is able to produce that result.

Either you're making things up, or finally you've found your grain of corn.

[quote:1f4975f597="KenHorse"]Really?[/quote:1f4975f597]
Really.
The code from your post Jul 23, 2019 4:52 pm gives with these values:
[code:1:1f4975f597] wday = 6 ' 0-6 0=Monday
repetition = 1 ' nth repetition of Day
month = 12
year = 19[/code:1:1f4975f597]
this result:
[quote:1f4975f597]Search: repetition #1 of Sunday in 12-2019 is 7-12-2019[/quote:1f4975f597]
Which is not the case.

The code from six1 from Jul 23, 2019 10:40 am, which six1 did edit already two times, puts out:
[quote:1f4975f597]Search: repetition #1 of Sunday in 12-2019 is 2-12-2019[/quote:1f4975f597]
Which is wrong too.

This means your shown codes work randomly, I'd call it guesswork-code.
It may be that there exists not shown code which produces reliable results.
I know it's feasible, well, it took me a hour.

Currently as I write this post, there is no correctly working code shown.

made a loop for month and result is:

Search: repetition #3 of Sunday in 1-2019 is 20-1-2019
Search: repetition #3 of Sunday in 2-2019 is 17-2-2019
Search: repetition #3 of Sunday in 3-2019 is 17-3-2019
Search: repetition #3 of Sunday in 4-2019 is 21-4-2019
Search: repetition #3 of Sunday in 5-2019 is 19-5-2019
Search: repetition #3 of Sunday in 6-2019 is 16-6-2019
Search: repetition #3 of Sunday in 7-2019 is 21-7-2019
Search: repetition #3 of Sunday in 8-2019 is 18-8-2019
Search: repetition #3 of Sunday in 9-2019 is 15-9-2019
Search: repetition #3 of Sunday in 10-2019 is 20-10-2019
Search: repetition #3 of Sunday in 11-2019 is 17-11-2019
Search: repetition #3 of Sunday in 12-2019 is 15-12-2019

[quote:15cb95f13a="MWS"][quote:15cb95f13a="KenHorse"]I must have tried it after the fix as I have not had an entered nth occurrence of a day yet fail to produce the correct result.[/quote:15cb95f13a]
There was no fix, the previous code puts out nonsense, as well as the current code does.
My previous message from 2:38 pm was for a reason, it reflected the tests I made with this code.
At least it's truly KenHorse-style code, shooting the horse from the back.

@Six1:
I'd suggest to post new code as new and don't edit old code in old messages, nobody can keep pace with such mess.[/quote:15cb95f13a]

Really?