Launch of Consumer/Home Owner registration process!
We are pleased to announce the commencement of the Consumer/Home Owner Registration Process on Community. Consumers/Home Owners may now proceed to register by clicking on Login/Register. The process is straightforward and designed to be completed in just a few steps.
Implementation of DTM's to support Altivar Process drives and other Ethernet based products.
Geo SCADA and Remote Operations Devices Ideas
Use this portal to submit your innovative ideas to make Geo SCADA Expert and Devices such as SCADAPack, Trio and Realflo of greater value to you and to the SCADA & Telemetry community. Every idea will be individually reviewed by our team for merit and will be marked Under Consideration.
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
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 InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
The M580 makes use of DTM's to connect to Process drives, TesysT's etc. This allows for the use of IO Scanning registers on these devices through the use of Modbus Function Code 23 (might be incorrect code). I believe this is a key feature for quickly adding multiple Ethernet devices to the SCADAPack and help with advanced diagnostics on your Process network.
The SCADAPack family already has a more capable Modbus Scanner configuration than the M580 provides.
I agree that having a 'library' for a particular set of scanner entries to represent a device type is good, but I think having them as DTMs is terrible.
It should be possible to have a lightweight XML (or JSON) format which would represent a set of Modbus transactions, and their transforms into a set of controller objects. This could then be hand edited / created as needed for new devices.
Please say no to DTMs that you need to install and maintain version coherency with... it's painful.
We’re looking at adding libraries to RemoteConnect that could include pre-configured support for Altivar VFDs and TeSys T motor controllers. Are there other devices of specific interest?
My Apologies for only replying now, I have been neck deep in projects. I believe the VFD's and TeSys T are the most important, I have been playing with the TesysT Island as well which is an absolutely game changing project and it would be great if we can get integration of this as well.