SPT Fubs check if in this particular configuration a SPT Fub is used

Ask Questions Mechatronics & Motion
1

Hi guys

I use multiple configurations. Some of the axes have deployed a parameter file containing SPT function blocks and some don’t.
When using MC_BR_ReadParId i always get errors back from the function and also get an axis error that can be read via MC_BR_ReadAxisError.
Is there a possibility to check if a specific parID is existent without having errors?

Lets assume i need to read the CMP_MODE - with the parID 6688 without error when it is not there.

image

Thanks for any thought on that matter
Cheers

2

Hi Patrick,

I’d imagine that MC_BR_GetParIDInfo is the function block you are looking for. You should be able to call it to determine if a ParID exists in a given configuration, and if it does then call MC_BR_ReadParId.

Hope this helps,
Connor

3

Unfortunately MC_BR_GetParIDInfo is not available on mapp Motion yet

image
image2061×1026 96.2 KB

but it was cool idea!

4

Hi Connor

Using MC_BR_GetParIDInfo worked even though i did not deploy any parameter file creating a CMP SPT function block.
The Fub returned the correct type and the correct length of a possible CMD_MODE+0 variable without it existing.
So this was a nice try but did not help detecting if there is a SPT function block used in a parameter file.

Any other thoughts on the matter?
Cheers
Patrick

5

I don’t think there is an easy solution with Acp10.
The statement SPT function block used in a parameter file, translates that this parameter file is downloaded to the drive. This could be traced by a network command trace for instance with function block MC_BR_NetTrace, but this then also depends on the number of parid’s downloaded to the drive and the size of this network command trace.

Probably that’s the reason that Acopos SptChart feature from mappMotion, could contain all spt networks in one SptChart.

6

Hello,
I don’t think there is a possibility out of the System to get this information.
Each Instance has to be created with ParID 777 FUNCTION_BLOCK_CREATE.
This functionality does have not any diagnostic data, as far as i know.
Typicaly you use the Mode ParID of the Fub, but i think the Mode ParID is also only generated after the 777 call.

I would recommend to use a SPT in all Configurations just to have a VAR_I4_0 or similar, were you can save 0 = no SPT , 1 = SPT.
So you have one ParID which is user Defined, allways accessible, and you have a information if you can expect more or not.

Greetings
Michael

7

Hi Michael

Thanks for your reply. After thorough testing, I couldn’t find any possibility to solve this issue. The solution you suggested, was one that I also had on my list. Alternatively i can solve this also in my application, but with more effort. Thanks for the discussion on this topic.

Have a great week
Patrick

1 Like