Using communication plugins with mcbcom

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Using communication plugins with mcbcom

ソリューションへジャンプ
1,881件の閲覧回数
Haitham_Ismail
Contributor III

I am trying to develop a 3rd party application that uses the mcbcom library. I am using the TCP plugin for the project. I already tested the setup with TCP plugin using FreeMASTER desktop and FreeMaster lite and it works as intended. However, when I use the mcbcom library in the application I get an "Error occurred" (code 0x80000000). I am using imxrt 1050 board and here is the connection string

"NET;169.254.120.174;type=TCP;port=3344;timeout=500"
 
So I was wondering what are the implementations of the communication plugins in the mcbcom library.

Thanks in advance

PS: I know that it is not from the rest of the code since I tested it on USB CDC & LPUART connections first
0 件の賞賛
返信
1 解決策
1,864件の閲覧回数
iulian_stan
NXP Employee
NXP Employee

Hi @Haitham_Ismail,

Are you using the mcbcom.dll from FreeMASTER or FreeMASTER Lite folder. There is slight difference in the way each library handles the plugins.

  • The one located in FreeMASTER uses uses plugin CLSID register in Windows system. You need to use 6D13CD9D-9F2D-4066-B655-45B54CA7494B instead of NET key in the connection string
  • The one located in FreeMASTER Lite folder uses a relative path and a friendly name. Your connection string should work with Fmstr Lite dll, but you need to include plugins folder next to the dll because of the relative path discovery.

Kind regards,
Iulian

元の投稿で解決策を見る

1 返信
1,865件の閲覧回数
iulian_stan
NXP Employee
NXP Employee

Hi @Haitham_Ismail,

Are you using the mcbcom.dll from FreeMASTER or FreeMASTER Lite folder. There is slight difference in the way each library handles the plugins.

  • The one located in FreeMASTER uses uses plugin CLSID register in Windows system. You need to use 6D13CD9D-9F2D-4066-B655-45B54CA7494B instead of NET key in the connection string
  • The one located in FreeMASTER Lite folder uses a relative path and a friendly name. Your connection string should work with Fmstr Lite dll, but you need to include plugins folder next to the dll because of the relative path discovery.

Kind regards,
Iulian