News:

  • October 03, 2026, 09:48:35 AM

Login with username, password and session length

« previous next »
Pages: [1]

Author Topic: MQTT Client server name resolution  (Read 11794 times)

Andrew S

  • Hero Member
  • *****
  • Posts: 144
MQTT Client server name resolution
« on: September 06, 2019, 01:20:40 PM »
If I'm using a POM with DHCP for ethernet connectivity, does the DNS resolution for the server address work in the MQTT Client device?

I've just found out that DNSLOOKUP and PING don't work with the POM so I'm trying to catch all the other items that won't work too. What did I miss?

Thanks, Andrew.
« Last Edit: September 06, 2019, 01:33:04 PM by Andrew S »
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6176
  • Yes Pinky, Do-more will control the world!
Re: MQTT Client server name resolution
« Reply #1 on: September 06, 2019, 01:35:34 PM »
The ECOMLT is a subset of the ECOM100. It is s co-processor that is just for programming and HMI. It is not adding another Ethernet port to the CPU.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

Andrew S

  • Hero Member
  • *****
  • Posts: 144
Re: MQTT Client server name resolution
« Reply #2 on: September 06, 2019, 01:43:10 PM »
Oh dear, that's very bad news. To be honest I'm only using it as a workaround because there's no DHCP support for @IntEthernet.
Did you decide whether or not you'd add DHCP support for the internal ethernet interface, and if so do you have any kind of ETA? It looks as though my project's on hold until that's available.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6176
  • Yes Pinky, Do-more will control the world!
Re: MQTT Client server name resolution
« Reply #3 on: September 06, 2019, 01:46:30 PM »
Quote from: Andrew S on September 06, 2019, 01:43:10 PM
Oh dear, that's very bad news. To be honest I'm only using it as a workaround because there's no DHCP support for @IntEthernet.
Did you decide whether or not you'd add DHCP support for the internal ethernet interface, and if so do you have any kind of ETA? It looks as though my project's on hold until that's available.

No ETA. Right now we are extremely busy and it isn't trivial.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

Andrew S

  • Hero Member
  • *****
  • Posts: 144
Re: MQTT Client server name resolution
« Reply #4 on: September 06, 2019, 01:47:59 PM »
Ok. Thanks for the response. I'll have the customer go with a different solution for now.

Andrew.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6176
  • Yes Pinky, Do-more will control the world!
Re: MQTT Client server name resolution
« Reply #5 on: September 06, 2019, 01:52:29 PM »
You might be able to do some kind of hack to let the ECOMLT fetch an address, then configure the internal port with that address and de-configure the ECOMLT.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

Andrew S

  • Hero Member
  • *****
  • Posts: 144
Re: MQTT Client server name resolution
« Reply #6 on: September 06, 2019, 02:05:02 PM »
Quote from: BobO on September 06, 2019, 01:52:29 PM
You might be able to do some kind of hack to let the ECOMLT fetch an address, then configure the internal port with that address and de-configure the ECOMLT.
I love the way you think Bob. The use-case won't allow for 2 ethernet cables or a local switch but thanks for the hackery.
Logged
Pages: [1]
« previous next »