I am relatively new to this but have successfully loaded cmh928's excellent all-in-one mode. I just want to try to understand how exactly the speed cam files are stored and updated on the F series, so that when I get updated speedcam files I can add them to the system in the best way.

I know that you can put either a speedcamtext.txt or a speedcam.spud file in the speedcam directory, but I am unsure as to what exactly the F series then does with those files.

Does it read the txt or spud file everytime it boots, only once and then stores the information somewhere else or a combination of the 2? Are manually entered speedcam locations added to the txt or spud file, or just stored internally? If stored internally would these remain in memory if an updated txt or spud file was created.

Sorry for all the questions, but I want to work out the best way to keep my speedcam files up to date without duplicating them.

I am relatively new to this but have successfully loaded cmh928's excellent all-in-one mode. I just want to try to understand how exactly the speed cam files are stored and updated on the F series, so that when I get updated speedcam files I can add them to the system in the best way.

 

I know that you can put either a speedcamtext.txt or a speedcam.spud file in the speedcam directory, but I am unsure as to what exactly the F series then does with those files.

 

Does it read the txt or spud file everytime it boots, only once and then stores the information somewhere else or a combination of the 2? Are manually entered speedcam locations added to the txt or spud file, or just stored internally? If stored internally would these remain in memory if an updated txt or spud file was created.

 

Sorry for all the questions, but I want to work out the best way to keep my speedcam files up to date without duplicating them.

AFAIK if you put a speedcam.txt file the unit creates a spud file out of it, and then all other manually added speedcams are just stored in the memory, regarding the rest of your questions i'm not sure how the unit handles those

I am relatively new to this but have successfully loaded cmh928's excellent all-in-one mode. I just want to try to understand how exactly the speed cam files are stored and updated on the F series, so that when I get updated speedcam files I can add them to the system in the best way.

 

I know that you can put either a speedcamtext.txt or a speedcam.spud file in the speedcam directory, but I am unsure as to what exactly the F series then does with those files.

 

Does it read the txt or spud file everytime it boots, only once and then stores the information somewhere else or a combination of the 2? Are manually entered speedcam locations added to the txt or spud file, or just stored internally? If stored internally would these remain in memory if an updated txt or spud file was created.

 

Sorry for all the questions, but I want to work out the best way to keep my speedcam files up to date without duplicating them.

 

AFAIK if you put a speedcam.txt file the unit creates a spud file out of it, and then all other manually added speedcams are just stored in the memory, regarding the rest of your questions i'm not sure how the unit handles those

TXT file is converted to SPDB file once. Manual additions and edits are stored in SPUD file.

I am relatively new to this but have successfully loaded cmh928's excellent all-in-one mode. I just want to try to understand how exactly the speed cam files are stored and updated on the F series, so that when I get updated speedcam files I can add them to the system in the best way.

 

I know that you can put either a speedcamtext.txt or a speedcam.spud file in the speedcam directory, but I am unsure as to what exactly the F series then does with those files.

 

Does it read the txt or spud file everytime it boots, only once and then stores the information somewhere else or a combination of the 2? Are manually entered speedcam locations added to the txt or spud file, or just stored internally? If stored internally would these remain in memory if an updated txt or spud file was created.

 

Sorry for all the questions, but I want to work out the best way to keep my speedcam files up to date without duplicating them.

 

AFAIK if you put a speedcam.txt file the unit creates a spud file out of it, and then all other manually added speedcams are just stored in the memory, regarding the rest of your questions i'm not sure how the unit handles those

 

TXT file is converted to SPDB file once. Manual additions and edits are stored in SPUD file.

Thanks Boris.

OK lets see if I've got it right, if I start with a TXT camera database, that is converted to SPDB on first boot up. This is stored on the system (in the same SPEEDCAM directory?). If I make any manual changes, that creates a SPUD file containing my changes, and the system uses the combination of the 2 files. If I then load another TXT file (newer updated camera database for example) and leave the old SPUD file in place, that will update the SPDB file but still leave any manual edits there as well?

Is the SPDB file an accumulation of previousy loaded TXT files, or is it emptied and reloaded each time it encounters a new TXT file? In other words, if the newer TXT file has some cameras removed compared to the older one will they be removed from the SPDB?

Sorry to be anal about this but rather than just throwing files at the system I really want to know what I am doing.

Thanks Boris.

 

OK lets see if I've got it right, if I start with a TXT camera database, that is converted to SPDB on first boot up. This is stored on the system (in the same SPEEDCAM directory?). If I make any manual changes, that creates a SPUD file containing my changes, and the system uses the combination of the 2 files. If I then load another TXT file (newer updated camera database for example) and leave the old SPUD file in place, that will update the SPDB file but still leave any manual edits there as well?

 

Is the SPDB file an accumulation of previousy loaded TXT files, or is it emptied and reloaded each time it encounters a new TXT file? In other words, if the newer TXT file has some cameras removed compared to the older one will they be removed from the SPDB?

 

Sorry to be anal about this but rather than just throwing files at the system I really want to know what I am doing.

You're welcome. I have read the explanation once, and can't say I quite understood it

As far as I understand it (I could be wrong here, though), on startup, iGO will process whatever text files are there that are newer than the SPDB file (there's only one). If, later on, you put a new TXT file, it will recreate the SPDB from that file only. It does not touch the SPUD AFAI,K, so it is recommended to delete SPUD when you load new speedcam database...

Thanks Boris.

 

OK lets see if I've got it right, if I start with a TXT camera database, that is converted to SPDB on first boot up. This is stored on the system (in the same SPEEDCAM directory?). If I make any manual changes, that creates a SPUD file containing my changes, and the system uses the combination of the 2 files. If I then load another TXT file (newer updated camera database for example) and leave the old SPUD file in place, that will update the SPDB file but still leave any manual edits there as well?

 

Is the SPDB file an accumulation of previousy loaded TXT files, or is it emptied and reloaded each time it encounters a new TXT file? In other words, if the newer TXT file has some cameras removed compared to the older one will they be removed from the SPDB?

 

Sorry to be anal about this but rather than just throwing files at the system I really want to know what I am doing.

 

You're welcome. I have read the explanation once, and can't say I quite understood it

 

As far as I understand it (I could be wrong here, though), on startup, iGO will process whatever text files are there that are newer than the SPDB file (there's only one). If, later on, you put a new TXT file, it will recreate the SPDB from that file only. It does not touch the SPUD AFAI,K, so it is recommended to delete SPUD when you load new speedcam database...

Thanks again. I think I get it now, even if I can't explain it very well

Thanks again. I think I get it now, even if I can't explain it very well

Any time