« previous next »
Pages: [1]

Author Topic: Inconsistency Version of a module between McStudio and Updater  (Read 150 times)

gaston

  • Newbie
  • *
  • Posts: 26
    • View Profile
Inconsistency Version of a module between McStudio and Updater
« on: June 22, 2016, 09:08:38 am »
According to Mc-ATO the Version of my module is 1v0.7r357. However McStudio, in device Maintenance and Connection, see it as Version 0.0-0.
The device is seen by the McGateway, as Beacon data and Lastbeacon are being updated.

The unit is connected to McSTudio.
Logged

Share on Facebook Share on Twitter

mc-John

  • Global Moderator
  • Full Member
  • *****
  • Posts: 212
    • View Profile
Re: Inconsistency Version of a module between McStudio and Updater
« Reply #1 on: June 22, 2016, 09:23:32 am »
You have to connect to the device once before the version is shown. The device list is created from beacons and information in the gateway and the version number comes out of the gateway. If the device is never connected to the gateway , the gateway does not know the version number.
« Last Edit: June 22, 2016, 09:28:50 am by mc-John »
Logged

gaston

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: Inconsistency Version of a module between McStudio and Updater
« Reply #2 on: June 22, 2016, 09:59:49 am »
The device was, once, connected to this McGateway. It is running a program (my device id is 0001004C).
I have 2 McGateway, but I have been using only one so far to get familiar with the programs and devices.

Do you have another explanation?
Logged
Pages: [1]
« previous next »