dear sir,
I want to communicate with meter in Mode E with GXDLMSDirector.
most of the not but not always, when GXDLMSDirector receive ACK string "<ACK>252<CR><LF>" close the port and show message "Element Not Found"
would you please let me know the resone
the log is as blew :
GXDLMSDirector 9.0.2411.0501
Log created 10:16:49 AM
10:16:58 Initializing serial connection.
10:17:00 IEC Sending:/?!<CR><LF>
10:17:02 HDLC received: /KFM5\2Kaifa Technology<CR><LF>
10:17:02 BaudRate is : 9600
10:17:02 AM Moving to mode E.
06 32 35 32 0D 0A
10:17:02 Received: 252<CR><LF>
System.IO.IOException: Element not found.
at GXDLMSDirector.GXDLMSCommunicator.InitSerial()
at GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)
Hi, This error is coming…
Hi,
This error is coming from the Windows driver. Check that you have the latest USB driver installed.
What optical probe are you using? If it's a Bluetooth probe it might be that BaudRate, DataBits, Parity, or StopBits is not implemented for the driver.
BR,
Mikko
Thanks for your reply I used…
Thanks for your reply
I used Bluetooth optical prob.
I have two different types of Bluetooth module and I have this problem with one of them.
I think this problem will be solve with delay between closing, changing frame and baud rate and opening the com again.
some times, in the first connection, the communication continue but in the second connection, the communication stop and the massage "The port is closed" is showed
12:44:45 Initializing serial connection.
12:44:47 IEC Sending:/?!<CR><LF>
12:44:48 HDLC received: /EAA5\2JAM200S-V74<CR><LF>
12:44:48 BaudRate is : 9600
12:44:48 PM Moving to mode E.
06 32 35 32 0D 0A
12:44:49 Received: 252<CR><LF>
12:44:56 PM Send SNRM request.
7E A0 1F 02 23 21 93 21 E0 81 80 12 05 01 75 06 01 74 07 04 00 00 00 01 08 04 00 00 00 01 88 99 7E
12:44:56 PM
7E A0 1F 21 02 23 73 E6 C7 81 80 12 05 01 74 06 01 75 07 04 00 00 00 01 08 04 00 00 00 01 35 12 7E
12:44:56 Parsing UA reply succeeded.
12:44:56 PM Send AARQ request.
7E A0 2C 02 23 21 10 AF 9F E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 62 1E 5D FF FF 88 55 7E
12:44:56 PM
7E A0 38 21 02 23 30 34 E7 E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 10 05 00 00 07 8D FF 7E
12:44:56 Parsing AARE reply succeeded.
12:44:56 PM Reading object 0.0.43.1.0.255, interface Data
7E A0 1A 02 23 21 32 F6 72 E6 E6 00 C0 01 C1 00 01 00 00 2B 01 00 FF 02 00 7D 8F 7E
12:44:56 PM
7E A0 16 21 02 23 52 09 A6 E6 E7 00 C4 01 C1 00 06 00 00 0E AD 82 FC 7E
12:44:56 Disconnect request
12:44:56 PM Disconnect request
7E A0 08 02 23 21 53 B1 A2 7E
12:44:56 PM
7E A0 08 21 02 23 73 7A 43 7E
System.InvalidOperationException: The port is closed.
at System.IO.Ports.SerialPort.Write(Byte[] buffer, Int32 offset, Int32 count)
at Gurux.Serial.GXSerial.Gurux.Common.IGXMedia.Send(Object data, String receiver)
at GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force) in D:\SaaDucument\gurux\GXDLMSDirector-master\Development\GXDLMSCommunicator.cs:line 1448
at GXDLMSDirector.GXDLMSDevice.InitializeConnection() in D:\SaaDucument\gurux\GXDLMSDirector-master\Development\GXDLMSDevice.cs:line 327
at GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters) in D:\SaaDucument\gurux\GXDLMSDirector-master\Development\MainForm.cs:line 1771
Hi, There is not much you…
Hi,
There is not much you can do with this. This is an optical probe issue and it's always hard to fix device issues on the client side.
If delay helps, use it. The best option is not to use the optical probe that doesn't work correctly.
BR,
Mikko