Skip to main content



      Home
Home » Eclipse Projects » 4DIAC - Framework for Distributed Industrial Automation and Control » Sting to BOOL and vice versa not working on raspberry PI(String to BOOL and vice versa conversion FB not working on raspberry PI)
Sting to BOOL and vice versa not working on raspberry PI [message #1834277] Fri, 06 November 2020 06:09 Go to next message
Eclipse UserFriend
I have modified blinking program to use String to BOOL FB and BOOL to string FB between publish and subsribe FBs. I found this is working good when deployed on two PCs. but when i use one PC and other part of the program on raspberry PI i am getting "Datatype error" on subsribe FB. Please check the attachments. I want to use this conversion because finally i want to use MQTT for data transmission between PC and raspberry PI which takes on srings as the input and outputs only strings.
index.php/fa/39218/0/
index.php/fa/39219/0/
index.php/fa/39220/0/

If i do it vice versa then program works till BOOL to String FB but thereafter it does not transfer data.

[Updated on: Fri, 06 November 2020 06:12] by Moderator

Re: Sting to BOOL and vice versa not working on raspberry PI [message #1834286 is a reply to message #1834277] Fri, 06 November 2020 09:14 Go to previous messageGo to next message
Eclipse UserFriend
Can you please check the deployment console for any deployment errors. It looks like that the green part of your applciation or at least the F_STRING_BOOL was not deployed to your raspberryPY.
Re: Sting to BOOL and vice versa not working on raspberry PI [message #1834291 is a reply to message #1834286] Fri, 06 November 2020 10:20 Go to previous messageGo to next message
Eclipse UserFriend
yes .. there seems to be some errors:

<!-- 192.168.1.108:61499 -->
<Request Action="QUERY" ID="0">
<FB Name="*" Type="*"/>
</Request>

<Response ID="0"/>


<!-- 192.168.1.108:61499 -->
<Request Action="CREATE" ID="1">
<FB Name="EMB_RES" Type="EMB_RES"/>
</Request>

<Response ID="1"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="2">
<FB Name="E_PERMIT" Type="E_PERMIT"/>
</Request>

<Response ID="2"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="3">
<FB Name="E_CTU" Type="E_CTU"/>
</Request>

<Response ID="3"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="4">
<FB Name="SUBSCRIBE_1" Type="SUBSCRIBE_1"/>
</Request>

<Response ID="4"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="WRITE" ID="5">
<Connection Destination="SUBSCRIBE_1.QI" Source="1"/>
</Request>

<Response ID="5">

</Response>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="WRITE" ID="6">
<Connection Destination="SUBSCRIBE_1.ID" Source="raw[].mqtt[tcp://192.168.225.34:1883, forte1, output]"/>
</Request>

<Response ID="6">

</Response>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="7">
<FB Name="F_STRING_TO_BOOL" Type="F_STRING_TO_BOOL"/>
</Request>

<Response ID="7" Reason="UNSUPPORTED_TYPE"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="8">
<Connection Destination="E_CTU.CU" Source="E_PERMIT.EO"/>
</Request>

<Response ID="8"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="9">
<Connection Destination="SUBSCRIBE_1.INIT" Source="START.COLD"/>
</Request>

<Response ID="9"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="10">
<Connection Destination="SUBSCRIBE_1.INIT" Source="START.WARM"/>
</Request>

<Response ID="10"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="11">
<Connection Destination="E_PERMIT.EI" Source="F_STRING_TO_BOOL.CNF"/>
</Request>

<Response ID="11" Reason="NO_SUCH_OBJECT"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="12">
<Connection Destination="F_STRING_TO_BOOL.REQ" Source="SUBSCRIBE_1.IND"/>
</Request>

<Response ID="12" Reason="NO_SUCH_OBJECT"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="13">
<Connection Destination="E_PERMIT.PERMIT" Source="F_STRING_TO_BOOL.OUT"/>
</Request>

<Response ID="13" Reason="NO_SUCH_OBJECT"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="CREATE" ID="14">
<Connection Destination="F_STRING_TO_BOOL.IN" Source="SUBSCRIBE_1.RD_1"/>
</Request>

<Response ID="14" Reason="NO_SUCH_OBJECT"/>


<!-- 192.168.1.108:61499: EMB_RES -->
<Request Action="START" ID="15"/>

<Response ID="15"/>
Re: Sting to BOOL and vice versa not working on raspberry PI [message #1834295 is a reply to message #1834291] Fri, 06 November 2020 10:46 Go to previous messageGo to next message
Eclipse UserFriend
The crictical error message is: UNSUPPORTED_TYPE

this means that you the F_STRING_TO_BOOL FB tpye is not availble in the 4diac FORTE version runing on your raspi. you need to add the iec 61131-3 module where this fb is contained in.
Re: Sting to BOOL and vice versa not working on raspberry PI [message #1834300 is a reply to message #1834295] Fri, 06 November 2020 11:34 Go to previous message
Eclipse UserFriend
Thankyou Alois. Yes... I checked FORTE_MODULE_IEC61131 in CMake tool and rebuild the FORTE for raspberry PI and it is working!
Previous Topic:SIFB with ANY type plug/socket
Next Topic:Conversion of array to string
Goto Forum:
  


Current Time: Sun Jul 13 14:33:44 EDT 2025

Powered by FUDForum. Page generated in 0.04317 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top