Open seisfeld opened 3 years ago
-------------------------------------------------------
Profile of this DFPlayer device
-------------------------------------------------------
The following devices have been discovered:
-> SD, announced on reset, discovered by getTotalTrackCount
Does NOT react on setPlaysourceFlash
Does NOT react on 0x3F queries
getFolderTrackCount...
-> for SD returned 2 files in Folder /01/
GetCurrentTrack for SD returns correct value 1599ms after start of track
Sends 1 callback(s) on SD track end
Continue playback after Ad for SD works
Wakeup from sleep by reset does NOT work
Wakeup from sleep by setting playsource SD does NOT work
Looks like this one can never be brought back from sleep mode, hm?
Honestly I can't really interpret the output. 😅 But from the chip side of things this is the first one i saw which uses a newer IC with just 16 legs (compared to the 24 usually). This is most likely because the chip all the DFPlayers are build upon is discontinued by the supplier. Because of that, i assume the software build is not the same as previous MH ET LIVE based DFPlayers.
Honestly I can't really interpret the output.
The summary states: Wakeup from sleep by reset does NOT work Wakeup from sleep by setting playsource SD does NOT work
So there's no (known) way to wake it up from sleep. All the details yadayada before the profile summary is about the actual communication with the device. The latter conclusions are from TestWakeupAfterSleep where you see the communication data to and from the player, e.g.:
[82395] Packet sent (->): 7E FF 6 C 0 0 0 FE EF EF -> Cmd: C (Reset), arg: 0
That means at millisecond 82395 after chip start, the Arduino sends bytes 7F FF 6 C ... to the player (->). The command in that string is C (hex) which actually is "Reset".
Result of that command sent back from the player to the Arduino (<-) is:
[82951] Packet received (<-): 7E FF 6 3F 0 0 2 FE BA EF <- Msg: 3F (StorageDevices), arg: 2
3F is "Storage Devices" information package and 2 as an argument means "SD Card available"
More on that protocol can be found here.
"ERROR 129" just means "timed out while waiting for reply from DFPlayer".
For the TestWakeupAfterSleep the device is put into sleep mode by sending command for sleep (i.e. hex 0A) and then trying to wake it up by either reset (command 0C) or SetPlaybackDevice (command 09) but both variants result in "ERROR 129" when trying to get the status from the device.