I am currently working with a Compactlogix and I am trying to get a barcode scan into a string file to be compared by another barcode scan later in the same process.
I have 19 "index" locations and I am having no troubles getting the [10]data into one of the locations HOWEVER, somewhere, somehow I am getting "Garbage" into these indexes that has nothing to do with the ASCII or anything else within the code. It sometimes shows up to 87 characters.
I am doing this by receiving the barcode through a ******* device (serial to ethernet) as a SINT then COP this to an ASCII file then MOV [10] into a temporary file.
I then have a save routine that CTU 19 and then RES @19. this enters the string into a location in the INDEX. with this I am MOV bits that I received from ALTA (seperate parts picking software/computer)for color and sonic welding.
If I start to fill up the index, the "garbage" will travel down the INDEX in unison (INDEX 11 is now 12, INDEX 12 is now 13 etc.) and when the CTU RES occurs, the "garbage" circles back around to the top (INDEX 1) and erases the true data in that location.
Any suggestions??? I have tried SEVERAL different methods and have either the same type of issue or others like the data just diaapearing on it's own.
Any help would be greatly appreciated.
I have 19 "index" locations and I am having no troubles getting the [10]data into one of the locations HOWEVER, somewhere, somehow I am getting "Garbage" into these indexes that has nothing to do with the ASCII or anything else within the code. It sometimes shows up to 87 characters.
I am doing this by receiving the barcode through a ******* device (serial to ethernet) as a SINT then COP this to an ASCII file then MOV [10] into a temporary file.
I then have a save routine that CTU 19 and then RES @19. this enters the string into a location in the INDEX. with this I am MOV bits that I received from ALTA (seperate parts picking software/computer)for color and sonic welding.
If I start to fill up the index, the "garbage" will travel down the INDEX in unison (INDEX 11 is now 12, INDEX 12 is now 13 etc.) and when the CTU RES occurs, the "garbage" circles back around to the top (INDEX 1) and erases the true data in that location.
Any suggestions??? I have tried SEVERAL different methods and have either the same type of issue or others like the data just diaapearing on it's own.
Any help would be greatly appreciated.