Your loop counter with 999999 as Max value in U16 will go in overflow, and rather soon.
Also you're using the DIgIN signal which will count once every program loop. If your program loop is longer than 40ms, the counter will add 1 for every program loop where the DIGIn value is seen as "high".
Use the .Count, and add them every program loop instead.

How are you counting the pulses?
I don't see anything on Pin 19. Is it the same as Pin 18 where there is a Carriage_Count signal connected from the DigIn to a loop counter in software?
This will be limited by the program loop time and any pin de-bouncing, etc. that may be done behind the scenes by the controller firmware.

You can use the Count signal from the pin which will report the number of pulses in the last program loop. You can add this each loop to keep a total count. See example in the image.

Forum is refusing to attach an image, so here is a link.
https://mallaghan-my.sharepoint.com/:i:/g/personal/alastair_cardwell_mallaghangroup_com/ERBvHI_ze29OiOCi19p-EW8B4ccK9Mk167E5wFAXvEP9SQ?e=1bjgWe

Apologies for the delayed response. 
I'm using pin 19, standard Danfoss speed sensor.  I have verified that it is properly adjusted.  I have attached a drive link to the .p1p file.  Many thanks for taking a look at it.

https://drive.google.com/file/d/1Y3IBoqeR5lJAkIsWtt3FziyghowtcL7y/view?usp=sharing

Hi,

I'll chime in as well with how I've used it.
1. I primarily use SVN although I've been using Git with Tortoise recently for several projects and my workflow for an application is slightly different compared to when I used SVN.

2. I don't really use the project view Tor mentioned unless I need to commit while the project is open. My primary method is to use the settings in Project Open/Close with the following settings checked.
"Close the project and delete temporary files in the project folder" I then have the search database, Test/debug folder delete options checked.
I would recommend having the backup file deletion on, and adding them to your .gitignore file.
I also add *.ddt and *.sdb to my .gitignore
Then when I need to commit I just close the project and the files I care about are good to go.

3. If you setup a devops pipeline, you could set up automated builds to generate the lhx, I still make them manually. During that build you could also setup regression testing with something like the GUIDE Test Tool. Making those pipelines does take some time though, so fair warning.

4. The trickiest part is the SCS file. I keep the main develop branch clean and require a PR to make changes, so all work is done in individual Branches. This forces the developers to make the merges manually. Compare SCS and the Module Viewer is basically mandatory for that part. This can be made a little easier by saving parts of the application as SCS files. Example: A block that contains a set of logic for controlling the motor, then you could give that block a version and some history for the developer to keep track of changes.
If you look at the Application Software Template you can see how using that type of approach could be achieved.
Having multiple developers in the same application is tricky, so taking the time to create a structured process and a structured application will set you up for success.

-Matt_Eng

Hello.

I have used GIThub desktop for years for my PLUS+1 projects without any issues with files pushes or pulls from the repository.
I always leave the projects unpacked when I push to the repository.

My Main branch includes a compiled base blank template, as you build in the applications create a a new branch on a compiled branch which as been merged onto the main branch/ development branch or release branch ( depending how you want to setup)
For visualization of the project build I use visual studio code GIT graph.

If you haven't used it before I recommend a trail with a non critical project.

PS. I also used tortoise but GIT hub desktop is preferred.