I think the problem is the space between the value and the MB
causes the problem
(any custom tag with a space in the output will cause problems with the custom mysql, as the space is seen as a delimter, and so will be the sequence out of order)
I have removed the MB on the end of that custom tag now in a new WD .zip update , ready now
Still the same problem:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘674)’ at line 1
I see something strange in my custommysqlout.txt, it did not happen before:
12/10/11 23:55 14.9 95 22.7 55 14.2 1024.1 3.7 4.3 5.2 25 0.0 1.8 464.8 0.0 0 0.0 0 14.8 18.4 14.9 14.5 14.8 1767 100% 674
There is an extra blank space between the two red values. This is custommysqlin.txt and their respective tags:
%date% %time% %temp% %hum% %indoortemp% %indoorhum% %dew% %baro% %10minavspeedinmetric% %avgspd% %1mingustwind% %dirdeg% %dayrn% %monthrn% %yearrn% %currentrainratehr% %VPsolar% %VPuv% %currentsolarpercent% %windch% %humidexcelsius% %heati% %wetbulb% %feelslikedp% %cloudheightfeet% %vpreception2% %freememory%
Do you think this can be the error cause? Can please check if any of that two tags has an extra blank on their output?
I think its the % associated with %vpreception2% custom tag that is the next problem
use a new .zip update, where that is only added if not used for the custom mysql
Working now, thanks Brian 
And one last question (as I’ve never done it before): how can I add data in the gap that wdmysql has been stopped (about 62 hours)? Do I have to create any kind of file? Does WD read them from log or inf files?
the adding of past data does not work if using a custom mysql
you could have though used the older wdmysql.exe until this was resolved
Ummm… too late then. I see now some tags I use in the custom setup are never stored in WD’s database. I’ll try to do something by hand. Anyway thanks again for your great support from your atipodes.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.