Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

When I am using a serial to ethernet converter, how should I configure MatrikonOPC Server for SCADA Modbus?

AVEVA Plant SCADA Forum

A support forum for AVEVA Plant SCADA (formerly Citect SCADA). Share new and exciting product information, connect, learn, and collaborate with the ecosystem of Plant SCADA Users. AVEVA Plant SCADA a reliable, flexible and high-performance Supervisory Control and Data Acquisition software solution for industrial process customers. This forum is to connect, share, learn and collaborate new and exciting product information. Feel free to join and share to your Ecosystem of Plant SCADA Users.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Industrial Automation
  • AVEVA Plant SCADA Forum
  • When I am using a serial to ethernet converter, how should I configure MatrikonOPC Server for SCADA Modbus?
Options
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
olivier_vallee
Lt. Commander olivier_vallee
28
Oncom
Commander Oncom
6
BevanWeiss
Spock BevanWeiss
2
RoozeeR
Lt. Commander RoozeeR Lt. Commander
2
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to AVEVA Plant SCADA Forum
Anonymous user
Not applicable

Posted: ‎2020-07-07 03:05 AM

1 Like
3
4120
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-07 03:05 AM

When I am using a serial to ethernet converter, how should I configure MatrikonOPC Server for SCADA Modbus?

Serial to Ethernet converters can come in different varieties.

 

Serial to Ethernet Connector that allows you to work with Modbus to Ethernet. It enables you to provide shared access to a local Modbus device over network, so other network users can reach its content and functionality as if it were attached directly to their machines. In a similar way, you too can access a remote Modbus over Ethernet regardless your physical proximity to the device. 

Some converters, such as Lantronix, will simply receive serial data, encapsulate it in a TCP packet and send it to the desired IP address.  In this case, the underlying Modbus protocol is still the serial "Modbus RTU" or "Modbus ASCII". You will want to use the "0 RTU (CRC16)" or "1 ASCII (LRC)" format in your Modbus Unit configuration for the MatrikonOPC Server for SCADA Modbus. If you are using the MatrikonOPC Server for Modbus (non SCADA) you will want to use the "TCP/IP Terminal Server".

Some converters, such as Moxa and Garretcom, will go one step further and convert the Modbus protocol from Modbus RTU to Modbus TCP. This is useful in cases where multiple masters, such as redundant OPC servers, need to access the data. Modbus TCP differs from Modbus RTU, in that its messages do not use a CRC/LRC, and each message is prefixed with a 6-byte header. Make sure you choose the format "2 RTU TCP" in the Modbus Unit. If you are using the MatrikonOPC Server for Modbus (non SCADA) you will want to use the "Modbus Ethernet PLC (TCP/IP)".

 

  • Tags:
  • com port
  • english
  • modbus
  • scada
  • serial port
  • serial to ethernet converter
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic
Replies 3
Rodrigo_Garcia
Commander Rodrigo_Garcia Commander
Commander

Posted: ‎2020-07-20 06:55 AM

1 Like
2
4083
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-20 06:55 AM

Thanks for sharing!

Rodrigo G. 


Industrial Automation Community manager

  • Tags:
  • english
Reply

Link copied. Please paste this link to share this article on your social media post.

RoozeeR
Lt. Commander RoozeeR Lt. Commander
Lt. Commander

Posted: ‎2020-07-20 08:22 AM

In response to Rodrigo_Garcia
3 Likes
1
4080
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-20 08:22 AM

You have to define the IP address of the Serial to Ethernet converter and the Modbus address. The Modbus address depends on how your converter is configured. When it's configured to have Modbus slave(s) connected, the Modbus address = Modbus address of the slave. Be aware that you set your OPC request speed at a level that can be handled by the converter and your Modbus device.

 

Capture.GIF

When it's configured to have a specific slave connected, the Modbus address of the slave is probably defined in the converter. You should read the converters manual how to address the slave.

When a Modbus Master is connected to the converter, your OPC server should be able to receive (unsolicited) data form the converter. I'm not sure if Matrikon OPC can do this.

R.Roozee
Sr Solution Architect (SAE Master)
  • Tags:
  • english
Reply

Link copied. Please paste this link to share this article on your social media post.

BevanWeiss
Spock BevanWeiss
Spock

Posted: ‎2020-07-22 08:21 PM

In response to RoozeeR
0 Likes
0
4064
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-22 08:21 PM

There really are so many different ways to do this...

Some vendors (such as Schneider) provide ModbusTCP to ModbusRTU gateways.

Others like Perle / Moxa can also provide just pure serial<->ethernet converters with various features available.

 

I know that both Perle / Moxa have a driver that can be installed which can enable the converter to appear identical to a local serial port, down to DCD/CTS/DTR/RI (modem signal) emulation and all.. Moxa call this RealPort I believe.

In such a mode, it's possible to use it on a multidrop RS485 network (with multiple ModbusRTU masters if required).. the likes of Kepware / Matrikon typically support these just fine.

 

When using the RawTCP (aka Telnet) mode, then you just setup a straight TCP socket (often it can be configured who will be the initiator) and then bytes received on the serial port will just be sent across the TCP socket, and bytes received on the TCP socket will be transmitted out the serial port.  Typically in this mode you lose the flexibility of dynamic changes to baud rate, or modem signal support, but you also have less software layers involved, so fault finding can be easier.

 

I think it is all about horses for courses... certain situations will exhibit a preference for one solution over another.


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
  • Tags:
  • english
Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of