Acti9 Smartlink IP in the EGX300?

[Anonymous user]

Hi,

May I inquire if it is possible to connect the new Smartlink IP to the EGX300?

We're having trouble with it.  We have put in the IP address of the Smartlink IP as a remote connection (just like what you do with the EGX100) but we couldn't get any information from it.

The old Smartlink modbus is ok.

Regards,

Adrian

[JamesJeanette · Accepted solution]

Hi Adrian!

If I'm not mistaken, I believe that you would need to add 255 as the remote ID for the Acti9 Smartlink IP.  This is something that we are working to add in the next firmware version; although it still needs to be tested.

Is this correct ?

James

[Randi_Dolan]

Yes, we will have support for "Remote" devices using ID 255 in our next firmware release.

[Anonymous user]

Thanks, guys.

Just to clarify, the IP address format should be something like xxx.xxx.xxx.255?

[Randi_Dolan]

No, the IP Address can be whatever.  But, in Modbus, there is a device ID.  In ModbusTCP devices, like the SmartlinkIP, this address is always 255.  You will have to put this in the EGX Device List as the Remote ID.

[Anonymous user]

Got it, Randi.  All clear now and we'll try it out.

[QuentinLt]

Just to clarify, the Acti9 Smartlink Ethernet is slightly different than Acti9 Smartlink: it has only 7 channels (vs 11) for Acti9 devices connectivity and 1 analog channel (2 analog inputs, 0..10V or 4..20mA).

So the data model will have to be renewed to. Is this planned ?

If not, we can work together to define the model.

[sesa205726_brid]

Hi Randi,

when will be released new firmware?

I already have installed new smartlink IP in a Demo Smart Panel and I have to configure EGX300.

Thank you

[sesa77557]

I agree with Quentin: we need a dedicated data model for Acti 9 Smartlink IP.

And please try to do something to better implement all the Smartlink offer (Modbus RS485 and Modbus TCP/IP) inside EGX300 WITHOUT requiring to add a customized web page...

The default visualization is so "poor and difficult to understand"...

Have a nice day.

Roberto

[Randi_Dolan]

The new firmware, that will support Remote Device ID 255, will be available mid Q4.

[JamesJeanette]

Hi Quentin/Roberto.

There is not a planned update for an Acti9 Smartlink IP webpage in the EGX300 as of yet...this will not be in the next release.  We can work together to define what is need for a future release.  Please send me a mail with this request and business impact.

James

[dborle]

Hi James,

What about support of Masterpact over IFE, where address x+200 isn't supported anymore (as it was the case until today with the "old" Masterpacts)? Will there be integrated a new driver for the "new" Masterpacts or must this be a custom device driver?

Thanks

Daniel

[Anonymous user]

Hi Randi,

I've put in the new firmware version but there seems to be something wrong.

Below is my setup under Device List.  When I do the Discover, it comes up as Unknown.

When I do a Communications Check under Diagnostics it looks good.

But when I go to the Monitoring tab, everything is out of service.

The products connected to the Acti9 Ethernet Smartlink are Acti9 breakers with iOF+SD, RCA's, Reflex's and a timer.

I am under the impression that they should display 1 or 0 as their status.

Are you able to advise if there is a work around this?  Thanks.

Regards,

Adrian

[sesa205726_brid]

Hi Adrian and Randi,

I confirm what wrote Adrian. I checked and the result is the same. Also the number of the channels is wrong: Smartlink IP has 7 digital I/O channels and 1 channel for analog inputs. the Acti9 Smartlink template shown by EGX300 is that of the Smartlink RS-485.

Regards,

Salvo

[Randi_Dolan]

Hello,

The EGX300 does not currently support the Acti9 Smartlink Ethernet.  However, it is possible to create a custom device type for this device.

Randi

[Anonymous user]

Hi Randi,

I honestly thought that the new firmware was to address the Smartlink Ethernet.

Do you have a procedure to create a custom device type specific for this?

Thanks.

Adrian

[QuentinLt]

Hello Salvatore, Adrian,

In our lab, we tested the 255 topic too, without the proper Acti9 Smartlink Ethernet device model. We simply declared and Acti9 Smartlink Ethernet at its IP address and using 255 as ID and used the standard Acti9 Smartlink model, like you did.

Good news:

If you want to log power and energy values from Acti9 Smartlink Ethernet, it seems to be working fine.

Just log the device, and the topics you want (just don't go beyond the channel 7). You can then get the data and display dashboards. Works fine here.

And this is really what EGX300 is for isn't it ?

Quentin

(Acti9 Smartlink Business Development)

[dkorte]

Hi,

in waths EGX300-Update-Version the Adress 255 works for Smartlink-IP. I test the 4.38-Version the EGX300 and the Smartlink-IP, but i cant see the function.

The Slave-Smartlink works correct with the EGX300 with the IP-Adress from the Smartlink-IP.

[QuentinLt]

Hi Dieter,

v 4.38 is the right version.

Just declare an Acti9 Smartlink Ethernet as an "Acti9 Smartlink", as usual, and use 255 as a slave address.

It's a workaround, so it will work only for logging Energy (kWh) data.

Any specific application ?

[dkorte]

Hi Quentin,

thanx for the fast answer.

That is what i have done.

But i dont know that only for logging Energy (kWh) data.

My application is the pulse-counter for gas and water.

Do we have a application for this?

[QuentinLt]

Hi Dieter,

Indeed, you can only display kwh units witht the current driver.

Do you intend to display the data with EGX300 dashboards or just log it and then use it with another solution ?

If locally for EGX300 => You will have to create a custom device type with these new units.

If you just need to log m3 for instance, no problem, you just discard the "kWh unit" info, there is no specific conversion in EGX300. You'll get the data and that what counts.

Hope this helps.