Hello,

still not check your prj but I recommend think about your idea how it all must working. How you know that next barcode isn't same, better say is that right one for next memory place to save? Generally only sequence of bytes representing BC code are received so you need check probably some right differ byte via which you can differ BC code type to what memory to save. This you need consult with your Project manager probably, I only talk about my experience in this area. If you can, better explain what you need to do, BC code internal sequence representation.

Hello Robinson,
the data destination with P_RCV is alway the identical DB. When you receive different frames in a sequence, you should check NDR=TRUE, then copy the data with BLKMOV and the received LEN to a different memory area.

Regards,
Kaulquappe

Hello Robinson,

in other case what I remember, you can receive also to other DB and also offset in recv DB so your idea about other offset recv BC code is ok but (as I mentioned) you need to know differ BC code type. For most cases Kaulquappe's sugestion is prefferable also to me.

Hello,

if this doesn't matter only you need differ 2 BC codes in differentd DBs, my sugestion can work. After NDR true you can set work flow of code to next P_RCV block with different DB number. After another receive you can set first P_RCV block with first DB number. This is situation that after each receive you can have BC code in different receive DB.

Duris_I

After NDR true you can set work flow of code to next P_RCV block with different DB number. After another receive you can set first P_RCV block with first DB number. This is situation that after each receive you can have BC code in different receive DB.

 P_RCV must only be called ONCE per LADDR! This is clearly stated in the manual.

You can of course change DB_NO /DBB_NO with NDR=TRUE, due to my experience it is better to use BLKMOV.

Regards,
Kaulquappe

Hello Kaulquappe,

there is no problem that user can call blocks as so much as he require, conditions are useful for this. If he don't want to call more blocks via conditions, you can use parametrized input fields with one block and use conditions for parameter set. Therefore we are programmers, we need think about more solutions, play with code not think about one solution from help, recommended by support.

Duris_I

Hello Kaulquappe,

there is no problem that user can call blocks as so much as he require, conditions are useful for this. If he don't want to call more blocks via conditions, you can use parametrized input fields with one block and use conditions for parameter set. Therefore we are programmers, we need think about more solutions, play with code not think about one solution from help, recommended by support.

 CP 340 manual secction 6.3:

Jobs which can be processed simultaneously

Only one FB P_SEND and one FB P_RCV may be inserted in the user program for each CP 340 used.

Yes my friend agree,

this is simultaneously priority of correct functionality. I've sugested each one with entry condition, this can be also EN cut condition with of course REQ handled. With correct sequence can be also working. All is up to him, nevermind I've mentioned also about parametrized block for more options, different offset receive. Maybe he made some tests and tell us about some solution.

Update: if my mentioned system isn't correct, apologize. To me is only logic more blocks existing on code but only one active at time.