KoCoS Limo Modem Kocos Push Meter

corriee
2024-02-12 14:16
Last Edited 2024-09-04 15:49

To Add a?Kocos Push Meter to te System:

Add a Login account on your profile with a limited?Role where only following functionality?is enabled:

Kocos Push Meter?(Pages:Undone/Recent?Push?Attempts))

And

View only selected?Entities

Also leave Can Add?anything

Use the login details MyCo.Login as user name and the password.

This can read multiple types of meters including Echelon Meters with WEP port

Smappee (Home Automation)

Elster Meters

Setup example:

http://196.22.139.148/kocosMeter.jsp?LOGIN=subdomain.login&PWD=password&MTYPE=ECHELON&RECTYPE=LP where

196.22.139.148 is your server's IP or URL

subdomain.login is your login

and password is the password

and MTYPE is type for that meter

So this URL is to be added to the Limo moden's Cloud Service section.

http://196.22.139.148/kocosMeter.jsp?LOGIN=subdomain.login&PWD=password&MTYPE=ECHELON&RECTYPE=LP

Tags: kocos kocos limo kocos push meter limo modem modem setup

sdg.matiaan
2025-12-17 15:09

for modbus meters you can use MTYPE of Generic Modbus

also, please remember to escape special characters (including in your password), like hash (#) becomes %23, ampersand (&) becomes %26 and space ( ) becomes plus (+)

and the IP should be the IP of your specific server

http://196.22.139.148/kocosMeter.jsp?LOGIN=sdg.testme&PWD=hash%23&MTYPE=Generic+Modbus&RECTYPE=LP

sdg.marinusvz
2026-07-02 17:56
Last Edited 2026-09-15 12:30

Please note that the values from KOCOS LIMO modems are almost generic, BUT you can still break things if you don't configure the right values to be pushed.

A BIG discrepancy is when the Profile is pushed, usually meters put the cumulative energy total in its profile. But some meters put only the energy that was used in a particular profile period, e.g the ELSTER and ISKRA meters. Clearly the LIMO just pushes what the meter gives to it, without normalizing the data or even distinguishing between totals and consumption values for profile, even giving 2 completely different things exactly the same tag in json.

THEREFORE, if your profile values are not the actual meter reading (cumulative energy register) at the end of the profile period, but simply the amount of energy used in the particular profile period (e.g. a half hour), pls make sure your MTYPE is something like 'Elster A1140' or 'ISKRAMT172'. Something that contains iskra or elster.
A good MTYPE for profile expressed as totals is ECHELON.

The MTYPE can be set up in the LIMO meter as part of the URL (as a cgi variable), or you can enter it as a value to go in the json (called mtype or MTYPE).
HOWEVER, sometimes it was setup wrong on the LIMO and you need to override the MTYPE context on PNPSCADA, in which case you can set it up under Advanced Meter Settings.

sdg.marinusvz
2026-09-15 12:35
Last Edited 2026-09-15 12:39

Please note, If you only want to read Totals for the meter, and interpolate the profile, you would typically just enable INST and not LP on the modem, and in PNPSCADA Advanced Meter Settings, you would just check the Totals checkbox and NOT the Profile checkbox.

This is the default way the meter is added to PNPSCADA. So if a meter is coming in as a Totals only meter, but you want to enable Profile, make sure you send LP packets also, wait for the meter to stop changing, then go into Advanced Meter Settings and switch on the Profile checkbox.

Then go into Meter Details, move the maxdate back to the comdate (deleting all following profile and totals), and go to communications monitor and ask to read the meter in again. What that would do, is to cause all the packets from the start to be re-read again, as if for a Profile enabled meter. HOWEVER please note that this happens in other threads, not the main Acquisition Thread, so it would appear to have read in, but it will probably still be busy 'reading it in'. Re-open the Edit->Meter Details screen repeatedly and see how the maxdate advances, or Edit->Meter Totals to see how more totals are put in, or Meter Graph to see how the profile is built, until it stops. Then you know it is done.

sdg.marinusvz
2026-09-15 13:05
Last Edited 2026-09-15 13:11

Please note, that on the Acuvim-L meter, the profile come in as totals, so if you want to read profile for that meter in, it is probably best to set the MTYPE to ECHELON, enable to Profile checkbox in Advanced Meter Settings, and set the MAXDATE back and 're-read' the meter in Comms Monitor.

However, please also check your Total Progression in the Edit->Meter Totals screen, and see if there are any breaks in your total progression, e.g. if the energy total has large jumps in reverse or forwards. It might be better to Uninstall the existing meter after setting the maxdate back to the place where the total progression went wrong (thereby making the kocospush queue packets available), and then uninstall the meter on the Edit->Meter Details screen through the uninstall link. This will change the serial number to _OLD, and then when the packets come in again, a new meter should be created, with a comdate in the new range after the break in the total progression.

Sometimes on the same meter, you might want to enable Profile only at a later point, where you enabled LP packets to be sent from the meter, in a similar way: set the maxdate back to where the LP packets start, and immediately go to Edit->Advanced Meter Settings and enable the Profile checkbox.

If the meter calls in too quick after setting the maxdate back, try switching on disabled first, in the Meter Details screen.

A problem that sometimes happen on the LIMO, is that the submits come in out of order. For instance, on the Acuvim-L meter, you can sometimes get profile with a gap (implying a spike on the end profile period, just before the spike), and then later on addition pushes, you can get profile periods inside the gap. In which case we make the spike smaller and put in the profile period inside the gap. Sometimes some gaps appear to remain.
If you have too many gaps that should not be there: If you don't need the profile periods to be absolutely accurate, you can always switch off the Profile checkbox and then the totals would interpolate, spreading spikes following gaps into the gaps.

The spikes after gaps in the case of gap-spikes, have a status of Interpolated, so they should not be taken into account for MD calculation on bills.

sdg.marinusvz
2026-09-15 13:19

PLEASE try to pass the same registers or energy quadrants (Active Forward, Active Reverse, Quadrant 1 Reactive, Quadrant 2 Reactive, Quadrant 3 Reactive, Quadrant 4 Reactive) into both LP and INST, so that we do not get apparent discrepancies. Also, please make sure that the Multiplier settings on the LIMO are reasonable, or at least the same, between LP and INST. When they are different, we obviously get discrepancies. Sometimes we get discrepancies already, when the timestamp on the INST appear to be too late in relation to the LP, and then the check total values appear to be too small. Unfortunately we are just meter readers, this cannot be fixed on PNPSCADA's side, you might want to actually stop sending totals for the 6 registers in INST to avoid this problem. Although, it might point to deeper problems in the modem, that we cannot fix: perhaps ALL the INST values you get are not on the correct timestamp as sent to us.
You will have to test and verify this yourself, we do not have physical access and cannot check with multi-meters and oscilloscopes ourselves.

Please log in to post a comment