@Paul: I think this is related to serial parsing, not creating FTP name for a file.
Hi Volker,
That is a bit difficult to have search string alter dynamically on CV.
The only possible way is rebuilding that date-time string via another serial port.
If you connect the sensor via serial sensor port, then have this trick on host port.
Connect pin 2 and 3 (add a jumper), then send 2SERIAL("{\d[22CV]\d[21CV]\d[20CV]^M^J}%s[1$]" )
22CV, 21CV and 20CV represent year, month and date from 22SV, 21SV and 20SV.
Then you can use 1$ in your search on serial sensor port:
2SERIAL("\m[1$]" )
Please note the incoming data will need to have the same value as 1$.
The second option would be using other method than date information.
Usually the incoming string have some sort of data delimiter, you can count the number of delimiter until reach the above date string.
The number of delimiter can be used to create discard parsing.
DT80 may be able to parse all those 36720 characters if the incoming flow is not fast, however during parsing DT is not accessible.
Parsing will take a couple of minute to finish and you need to create the right parsing loop.
If you can send me the sample of incoming string (255 characters) perhaps we can find solution for both requirement.
Best regards,
Rudy Gunawan
@Paul: I think this is related to serial parsing, not creating FTP name for a file.
Hi Volker,
That is a bit difficult to have search string alter dynamically on CV.
The only possible way is rebuilding that date-time string via another serial port.
If you connect the sensor via serial sensor port, then have this trick on host port.
Connect pin 2 and 3 (add a jumper), then send 2SERIAL("{\d[22CV]\d[21CV]\d[20CV]^M^J}%s[1$]" )
22CV, 21CV and 20CV represent year, month and date from 22SV, 21SV and 20SV.
Then you can use 1$ in your search on serial sensor port:
2SERIAL("\m[1$]" )
**Please note the incoming data will need to have the same value as 1$.**
The second option would be using other method than date information.
Usually the incoming string have some sort of data delimiter, you can count the number of delimiter until reach the above date string.
The number of delimiter can be used to create discard parsing.
DT80 may be able to parse all those 36720 characters if the incoming flow is not fast, however during parsing DT is not accessible.
Parsing will take a couple of minute to finish and you need to create the right parsing loop.
If you can send me the sample of incoming string (255 characters) perhaps we can find solution for both requirement.
Best regards,
Rudy Gunawan