Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Generic Modbus Driver - Serial & IP
#21
Oh, wait, how did you create the file? If you just right clicked there and created a new file, or you opened a text editor and saved to there, it won't have actually gone there. Unless you are running as admin it will get redirected to a per-user account location.

Run a text editor as admin, then go there and see if the file is there. If not, then that happened. Run another instance non-admin which should find your redirected one. Copy the text, then delete that file. Then create the new one in the admin instance and save it. See if that works.
Dean Roddey
Explorans limites defectum
Reply
#22
I just did a wireshark view of the comms and the driver appears to ask for a slave ID from the PLC. It returns an exception (as slave ID is only part of the serial modbus comms protocol, not Modbus TCP). Would I be correct in thinking that the driver is possibly trying to write this exception to a field and thus throwing the error or would driver account for that? On attached 192.168.1.10 is CQC, 192.168.1.16 is PLC.

Thanks Dean, I did check that alright. I used the config file given with the driver and resaved it as .csv before copying over.The file does indeed exist at C:\Program Files (x86)\CQC\CQCData\MacroFileRoot\Drivers\Modbus\ when running notepad++ as admin.

Jim


Attached Files
.jpg   Capture.JPG (Size: 45.08 KB / Downloads: 10)
Reply
#23
Hi,


So opening the driver in the harness gave a bit more detail.

Code:
CQCGenDrvS, MEng.User.CQC.Drivers.Modbus.Generic.DriverImpl.1195, Status/App Status
Could not open file: \Drivers\Modbus\modbus_FieldAlias.csv

Some questions;


1. Is \Drivers\Modbus\modbus_FieldAlias.csv referenced to the C:\Program Files (x86)\CQC\CQCData\MacroFileRoot folder? I assume it is but just want to check

2. Is it correct that it prepends the driver moniker (modbus in my case) and an underslash to the config file name as shown above? (Changing config file name to modbus_FieldAlias had no affect anyhow)

3. Is it an issue that it can't find the file or that it can't open the file due to contents of file?

Any ideas on how I can investigate further?

Jim
Reply
#24
It is relative to that MacroFileRoot, so it would in the end be MacroFileRoot/Drivers/Modbus/ and the file would be in there. It is prepending the driver moniker to the file name, so you should name yours that way. Fro the error I would say it's not finding it.
Dean Roddey
Explorans limites defectum
Reply
#25
Its been a long time since i looked at this and there is another version in development that has stalled.

The csv file needs the moniker in the filename - that way you can have multiple copies of the driver installed.

I tested this on a Modicon PLC and it would return the ID so I used that as a way of connecting, but since then I have found that not every MODBUS TCP device will report an address.

This is something I need to get back to as I have some modbus power meters going in, a new PLC using Modbus (Click), a VSD and a few other smaller cheap Modbus devices. I'm trying to model its flexability around the Matrikon OPC server for modbus as I use that in our production environment
Mykel Koblenz
Illawarra Smart Home
Reply
#26
Quote:Its been a long time since i looked at this and there is another version in development that has stalled.

The csv file needs the moniker in the filename - that way you can have multiple copies of the driver installed.

I tested this on a Modicon PLC and it would return the ID so I used that as a way of connecting, but since then I have found that not every MODBUS TCP device will report an address.

This is something I need to get back to as I have some modbus power meters going in, a new PLC using Modbus (Click), a VSD and a few other smaller cheap Modbus devices.  I'm trying to model its flexability around the Matrikon OPC server for modbus as I use that in our production environment

Do you think the driver could support this Heliodyne  device?  The outstanding question waiting for answer on is whether TCP is ascii or RTU.  Specs attached.Thanks,Ron


Attached Files
.pdf   HeliodyneModbus_2013Aug20.pdf (Size: 989.24 KB / Downloads: 3)
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Samsung HLxxA750 DLP Beta Driver jrunde 33 18,553 9 hours ago
Last Post: gReatAutomation
  Amazon Echo Hue Simulator Driver wuench 123 50,502 07-08-2019, 09:53 AM
Last Post: Dean Roddey
  Generic Irrigation Scheduler jkish 571 191,672 06-12-2019, 12:10 PM
Last Post: Dean Roddey
  New Driver - How hard would this be? kblagron 4 644 05-20-2019, 11:28 AM
Last Post: zaccari
  Cytech Comfort Driver znelbok 6 607 04-10-2019, 05:39 PM
Last Post: znelbok
  OpenHAB Driver whozeawhat 6 2,451 01-16-2019, 06:45 AM
Last Post: greymatter
  LIFX Driver bobskie708 14 4,083 01-10-2019, 06:36 PM
Last Post: Dean Roddey
  XBMC Driver wuench 428 188,258 12-28-2018, 11:07 AM
Last Post: dogman
  RunTimer2 driver rbroders 15 5,728 12-14-2018, 05:28 PM
Last Post: rbroders
  Driver for Bigass Fan lleo 7 1,022 11-25-2018, 08:57 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)