Hi,
we have the OBIS codes and meters for a DLMS meter.
But we don't have the meter config software or the specific DLMS protocol implementation documents.
Would this be sufficient for you to write the protocol driver for PNPSCADA to be able to read this meter type, and what is required for data integrity.

Hello,
No, it would not be sufficient.
DLMS as a standard is quite wide, and to say that a meter talks DLMS, is really a very generalized statement. Even within the standard itself there are quite a lot of different options, e.g. HDLC or TCP wrapper protocol, just to name a mayor one.
Additionally, there are manufacturer specific codes, which can mean anything.
Even the BER-like encoding used by Itron for their ACE6000 and SL7000 meters has some primitive data type codes that are not defined in the DLMS standards documents, but specific to the Actaris/Itron meters.
Also, the codes for specifying what different event value codes mean is actually not at all defined in the DLMS standard (there are different countries that have standards in that regard to make up for this lack in DLMS, e.g. Netherlands and India I know has some standards for standardized event codes).
The fact of the matter is that none of the DLMS meters we have integrated implements DLMS in exactly the same way. Some meters like the Itron ACE6000 and SL7000 meters do not even keep the normal energy total at the standard OBIS code address, but it returns all the current energy registers together in a manufacturer specific list register, and then in the list register there is a column with the normal OBIS code, so you know which register goes where.
There are also other differences. Above are just some examples. We have found Chinese DLMS meters to be remarkably easier to use in general, however, there are still some idiosyncrasies, and then the ever present problem with the meter event codes that are completely different for every manufacturer.

So, with the above realities in mind, it would probably not be sufficient to just give us a list of OBIS codes and say the meter 'talks DLMS', for us to be able to write the protocol driver.
Under normal circumstances, when we try to talk to the meter while developing the protocol, and fails, we can just fire up the meter manufacturer software, and do the equivalent communication, while seeing what signals travels through the wire or over the network. We can then decode and interpret those communication packets according to the documentation to see exactly what the meter manufacturer himself is actually doing when reading his own meter, and that helps us to get past such an obstacle.
If we don't have access to the meter manufacturer's software, it means that an obstacle like that is much harder to traverse, and even if we miraculously get it talking, we could still be missing something.
So we need full documentation of e.g. event codes, but we also need access to the meter manufacturer's software to talk to the meter. (over the AMR port the modem connects to, so that we can confirm that it is actually working. And sometimes the protocols are different)
I'd say to have the proper meter manufacturer's software changes the chances of success of implementing a protocol driver from 20% to 95%, and it effectively cuts the time to develop it to easily a quarter of what it would be otherwise. Therefore, if you ask us to develop a protocol driver without giving us the meter manufacturer software, the price would be x4, and we would want half the money up front, un-refundable in the event of failure. If you give us the meter manufacturer software and some protocol documentation (or if it is an IEC standard); standard rates and delivery times and payment terms would apply.

However, even if we do manage to create the PROTOCOL driver without the meter manufacturer software, there are some other fundamental concerns that makes this a really bad idea:
If there is ever any doubt that PNPSCADA is reading a meter correctly, one can use the meter manufacturer software to read the meter directly, and confirm that the meter data is truly stated within PNPSCADA. It effectively takes PNPSCADA out of the loop in terms of troubleshooting, making it easy to put the blame in the correct place. Otherwise, a common stance for meter manufacturers to take is that it cannot guarantee PNPSCADA, since it is not their product, and therefore they won't give you support for your meter problem.
From that perspective, it is also important that we at PNPSCADA must have access to the software, otherwise we can also just blame the meter company for having a bad meter, and refuse to give support, because we don't have the meter manufacturer software to 'prove' that we are at fault.
And even from a practical standpoint, even if someone else can prove that PNPSCADA is at fault, how can we fix it, if we don't have the means to see how things should be done, and then test our software after applying a fix, to see that it now reads the value correctly, where correctly is defined as the result returned by the meter manufacturer's software on the same meter.
And therefore we cannot guarantee the data integrity of the meter readings in PNPSCADA if we don't have access to the meter manufacturer's software ourselves.
Lastly, from an owner of a meter's perspective, how on earth can you buy an AMR meter without the basic means to read or configure it. Surely it is a contravention of common sense property law for a manufacturer to sell you a meter, which is your property, and refuse for you to read it, or refuse for you to be able to configure it. How can the meter manufacturer's software not form part of the package sold to you, as the owner of a meter, when you buy the meter. That is so fundamentally wrong, that you could probably take the meter manufacturer to court and force them to either give your money back or give you the software. It is as basic as property law - you'll have a good case.

I am sorry that i am messing the thread but i really need help with this theme:   ( https://wiki.pnpscada.com/fpost.jsp?thread=584 )

I will be very thankful, even i am ready to pay if you guys help me with HexView , thanks in advance .

@1100modd
I don't understand what it is that you need help with?
Do you want the Hexing Software? you can get it from Hexing
or do you want to register the Hexing Software? you have to do it via Hexing
or do you want to setup the Hexing modem? you can follow the steps in the screenshot.