Forum Home › Forums › Rapid SCADA on Linux Controllers and Raspberry Pi › Any questions about Rapid SCADA and Raspberry Pi
Tagged: Raspberry Pi 4
- This topic has 88 replies, 16 voices, and was last updated 3 months, 3 weeks ago by Mikhail.
-
AuthorPosts
-
October 10, 2018 at 8:36 am #4375IncineratorX2Participant
– edit – sorry wrhong thread
- This reply was modified 6 years ago by IncineratorX2.
October 10, 2018 at 8:44 am #4376manjey73ParticipantThe formula name must be entered correctly, as specified in the formula itself
public double GetBit(double val, int n) { UInt64 uintVal = (UInt64)val; return (uintVal >> n) & 1; }
GetBit
And so it is necessary to write for all formulas
- This reply was modified 6 years ago by manjey73.
October 10, 2018 at 10:04 am #4380IncineratorX2Participantsorry i replied on the wrong thread.
February 26, 2021 at 9:02 am #8331percy011ParticipantI use raspberry pi 4 I found problem how to solve
- This reply was modified 3 years, 7 months ago by percy011.
February 26, 2021 at 1:29 pm #8336MikhailModeratorJanuary 23, 2024 at 8:38 am #13975niel.j@raumix.co.zaParticipantGood day, before i buy a Raspberry Pi 5 board, will there be any issues on running Rapid SCADA on the new Raspberry PI 5, or is it expected to perform the same as on Raspberry Pi 4 Board.
Kind regards
NielJanuary 23, 2024 at 9:38 am #13976manjey73ParticipantRapid Scada v6 runs on ARM v7 and higher processors
Version 5 including ARM v6For version 6, first check dotnet support by processor type
I don’t think there will be any problems on the Raspberry Pi5January 24, 2024 at 8:14 am #13978MikhailModeratorHello,
Rapid SCADA 6 works on Raspberry Pi 3, 4 and 5.January 24, 2024 at 8:15 am #13979MikhailModeratoris it expected to perform the same as on Raspberry Pi 4 Board
Yes.
June 12, 2024 at 5:22 pm #14673ArunRuchirParticipantI have successfully installed RapidScada on Raspberry Pi 4 and also created the deployment profile. Created MQTT connection and a Tabel view. Everything is working fine, except that Table view on web display is not showing current/any data. While data is visible on Device and Tag but not on web display. No specific error log also visible.
Please help if I have missed any specific setting.June 13, 2024 at 8:19 am #14680zzzParticipantDo you have channels bound to the tag_code or cnlnum ?
– topic needs to have a
tag code
defined in mqttclient.xmlProperties
.
–Bound to the configuration database
needs to be checked inLine options
– That same
tag code
needs to be filled intoCode
col ofChannels
table in conf db.For
Channels
related setting changes to take effect when uploading the conf db, both Server and Communicator needs to be restarted.- This reply was modified 3 months, 3 weeks ago by zzz.
June 13, 2024 at 9:39 am #14687MikhailModeratorThe above advice is correct.
@arunruchir, could you provide screenshots of the settings and device data page?- This reply was modified 3 months, 3 weeks ago by Mikhail.
June 13, 2024 at 1:07 pm #14692ArunRuchirParticipantThanks ZZZ and Mikhail,
It started working partially. I had missed mapping tag code into code col of Channels table in conf db.Enclosed are 4 screen shots.
1) I have mapped 2 identical Channels to fetch MQTT data from broker using same topic. Its updating properly also. However, the same are not reflecting on Table view on Web page? There is mention of channel 302…… why ? and How ?
2) Although current readings started getting displayed in table, no other readings are reflected for the past. This is running for nearly 2 hour now.
3) I have to add many more devices using same MQTT Broker. Will it be a good idea to create separate lines or add more tags on same line ?Thanks in advance for help.
https://drive.google.com/drive/folders/1t2LtMAM7Cre5t8mcVvUOPq708ua42aZf?usp=drive_link- This reply was modified 3 months, 3 weeks ago by Mikhail.
June 14, 2024 at 9:46 am #14700MikhailModeratorThe above link is not public.
The issue does not seem Raspberry specific. I suggest to find a proper topic related to MQTT communications for continue. -
AuthorPosts
- You must be logged in to reply to this topic.