Hello,
One of our customer ask if PcVue can work with GPRS DTU protocol.
Does someone know that ?
Does somebody know something on it?
just to make this post on the top. 🙂
No sorry. DTU is from which manufacturer?
Thx, Nico.
On of the customer will use the DTU from Hongdian, China local manufacture. You can see the DTU Spec with this link: http://www.hongdian.com/en/product/details.aspx?pid=100000062423889.
Normally, the customer will use "No permanent connction" due to the cost of GPRS.
The modle is: H7118.
You can forgat.
We dont really manage "no permanent connection" protocols 🙁
DTU seems to mean Data Terminal Unit.
I think this is not a protocol at all.
So what is the protocol behind?
Hello,
I have the same feelings as Ludo.
About "non permanent connections", they are only (a bit) managed if you're communicating through an OPC server. You've then to activate two options on the variables and the OPC Groups.
For the variables: saved
For the OPC group: No synchronization > preserve saved value if quality is bad
This OPC option has been added first for the Sofrel OPC server wich manage GPRS non permanent connections.
Thank you for your ideas. I called the customer and get the following info:
1. Architecture he supposes to have: PcVue(COM Port)->DTU(with SIM Card)->Omron PLC(SYSWAY);
2. He succeed with this architecture: KingView/Omron software(COM Port)->DTU(with SIM Card)->Omron PLC(SYSWAY);
3. He'll use non permanet connection, because he succeed it in 2. As he said, the transimition within DTU is the Transparent transmission
🙂
For Omron PLC we advise to use their OPC server CXServer suite.
If he manage to have it working with KingView then the same setting should work with PcVue.
Good idea, i'll suggest him to do it as you advised.
I would like to learn more about typical solutions and best practices when doing data acquisition over permanent and non-permanent GPRS connections.
The question is how to set up a monitoring system for mobile assets, including alarm notification coming from these assets. I understand that PcVue does "not manage well" non-permanent data aquisition. However, when looking at the project references in certain sectors I assume that there must be at least some little experience available.
At the moment I have some very basic questions:
- What are the typical application layer protocols to use? I already read about OPC. I also assume that FTP and the telecontrol protocols could be suitable, right?
- How can I manage establishing connection and reconnection to the remote endpoint? Which of the two partners typically initiates the connection? How may this be achieved in an event-driven or cyclical manner?
- What are the typical traps to avoid?
- Are there any other questions to answer before actually starting to design the system?
2 points:
- Data read by PcVue: Here we can manage by scada basic to, cyclically or by event, Start and Stop the communication. in my point of view there is no problem except managing the NS COM state.
- Data sent by the device: Here is the problem. We have nothing to listen a medium. The typical behavior of a device not permanently connected is:
- Send by event an urgent alarm.
- Keep archives and send them every day.
You know that we don't have native tools to manage that.
I experienced several projects where the device sent all those information by SMS. Then a VBA task get the SMS and:
- Affect PcVue variables
- Import archives in proprietary/hds unit.
Of course, that kind of work around is really project specific and can apply on small projects...


