More questions on RFID

I am currently only using FACTORY I/O and CONTROL I/O. I have a mostly functional setup already and I am looking to expand on my project.

SCENARIO #1.
I am creating a manufacturing, storage, and order fullfillment “Business”. I have a stacker with 2 rows of storage totaling 108 slots. I have an RFID reader creating I.D.'s post emitter. I then have an RFID on the “Loader Conveyor” for the stacker to assign a storage location. I then want to pull a specific pallet type from the stacker and remove it. This means I would need to know where a pallet of the requested type lives so I can retrieve it.
I am creating pallets with small, medium, and large Boxes. I will have a certain number of each box in storage. I feel that, for the sake of efficiency, the individual pallets simply go to the next available storage location rather than having an assigned area for an assigned product (as long as the predetermined number of each box size is stored).
I created a small box pallet and sent it to the stacker. That pallet receives an “S” for small and a “1” for the first of its type to enter the “database”. When it arrived at the stacker the next available storage slot is slot 32. I assigned that pallet with S1 after the emitter then add a dash and 32. (-32) to the id to store its location. This “product” is now S1-32.

Questions:

#1. People say there is a “128 word” Identification storage. I understand that to mean I can create a single ID with up to 128 individual numbers letters and characters. How can I view these created I.D’s?

#2. How many individual IDs can I create? I have 108 storage locations. Can i create 108 IDs with “128 word” individual IDs?

#3. Scenario then questions.
Lets say I pull the pallet from slot 32. The rest of the slots are full. After removing that pallet I need to create a new pallet with THAT ID to refill THAT slot. If I create an ID then remove it from “circulation”, does that ID come back as an available ID?

#4 I hear that I can make control i/o use something like excel to store these IDs. How do I do this?

#5 more questions to come lol

Hello:

You are making a mistake, and you are making a mistake from the beginning of your approach, from here:

“I only use FACTORY I/O and CONTROL I/O”, so far:

“I have a stacker with 2 rows of storage totaling 108 slots. I have an RFID reader that creates identifiers after the issuer. Then I have an RFID on the “Load Carrier” for the stacker to assign a location”

You say, “the stacker assigns a location”, let’s see, the stacker is never going to assign any location, you have to assign it (either from an RFID or from a camera or from a value), and most importantly, you must save it in a file to know at all times and by reading the file the state of the machine, even after restarting the application, which will surely happen at some point.

You say, #1 “that means I can create a unique ID with up to 128 individual numbers, letters and characters”, that is UNINTELLIGIBLE for any further expansion, including to maintain proper functioning in future modifications.

You say, #2" “How many individual identifiers can I create?”, NONE you can create, that application cannot be created by assigning unique individual values ​​to each location in the storage, it must be DATA FIXED in advance, (not created), and that can be saved and RETRIEVED, for example, EST1, or PR1, otherwise it will never work for you.

You say, #3 “After removing that pallet, I need to create a new pallet with THAT ID to fill THAT space”, I insist, you cannot create a new pallet with that ID every time you change the pallet, you must recover the one you already created, (watch the attached video in the case of the times that I mention).

You say, #4 “use something like Excel to store these identifiers”, it can be EXCEL, ACCESS, SQL or any existing database, but keep in mind that neither FACTORY IO, NOR CONTROL IO, nor any PLC can work with databases, said databases must be external and be possible, both writing and reading, by the application that controls the shelves THROUGH the PLC, otherwise you will never be able to do what you expose.

And finally you say, How do I do it? The best thing is to generate an array beforehand, (NEVER CREATE ANYTHING, BUT DO IT IN A WAY THAT IT IS ALWAYS THE BASE AND ALWAYS WITH THE SAME VALUES ALREADY WRITTEN IN ADVANCE), in which you store the values ​​of the shelf, you must go through this array to use it, if it detects an empty position that will be where it should go, if you have three box partitions, there will be three arrays, when the application sends a box to a matrix, it is the application that must fill the matrix and no sensor of any kind can do so, in the same way, when a position is extracted, the application will be the one that leaves the corresponding space in the matrix blank, waiting for the next entry, when traversing the matrix, to be the free position the next entry.

Or what is the same, if you do this:

That palette receives an “S” for small and a “1” for the first of its kind to enter the “database.” When it arrived at the stacker, the next available storage space was 32. I assigned that pallet S1 after the issuer and then added a hyphen and 32 (-32) to the identifier to store its location. This “product” is now S1-32.

You will simply fail, but if from when the product enters it is already S1-32, it would be matrix 1 position 32, when you want to remove it go there, and go through the matrix before adding another one, which when it detects this empty position it will go there again, and you no longer have to worry about creating anything, or storing anything, nor do you have to worry about anything, it will be enough to go through the file.

minute 7:30 until minute 12/13 more or less…