Hello,
yes, you can absolutely work with csv files. Your current tables look like this:
$ Survey : chr "tagged_13ag2020" "tagged_13ag2020" "tagged_13ag2020" "tagged_13ag2020" ...
$ Station : chr "AA10" "AA10" "AA10" "AA9" ...
$ Idcamara : chr "C13" "C13" "C13" "C14" ...
$ Species : chr "Meles_meles" "Meles_meles" "Meles_meles" "Vulpes_vulpes" ...
$ DateTime : chr "21/06/2020 22:14" "21/06/2020 23:51" "27/06/2020 23:05" "24/06/2020 5:19" ...
$ metadata_Nindividuals: int 1 1 1 1 1 1 1 1 1 1 ...
$ Y : num 37 37 37 37 37 ...
$ X : num -6.45 -6.45 -6.45 -6.45 -6.45 ...
which in camtrapR terms is a record table (which species, where, when). In general what you need in addition is the camera trap table (which station was set up where, and when?). The X and Y columns need to be in the camera trap table. They are redundant here because all records at the same station have the same coordinates. You will need to add the setup / retrieval dates and possibly dates of malfunctioning.
See
data(recordTableSample)
data(camtraps)
for a simple example of both tables.
In your specific case you may not need the camera trap table if the analysis is strictly about activity and specific camera trap information are irrelevant (you pool data from all stations). The activity* functions only need the recordTable, which you have already.
Just load your data with
read.csv(..., sep = ";") # your csv uses semicolon as column separator
Then proceed with the activity analysis. See e.g. ?activityOverlap, the example section
Best regards,
Jürgen