Jump to content
C4 Forums | Control4

4" Touch Screen Update


Recommended Posts


Hi Ryan

It is identified in the project. The touch panel when switched on displays as default the room that it is in. Also when I try to do the update you can see the touch panel device there but it just says it failed to connect after waiting about 5mins when trying to update.

I've attached the screen error below

Thanks

Link to comment
Share on other sites

Go into the connections tab and see if you see the device on the right side, I would try manually putting the IP address instead of the UUID name if you haven't done so already.

Also, go into system manager and make sure the IP / Gateway / Subnet and DNS entries are correct for the MTS.

Link to comment
Share on other sites

Hi Dan ... This makes sense as to why the MTS is able to see the different rooms and set the time etc but Composer is unable to control any parts of the device including being able to send updates. Will change the MTS to a static IP when I get back to my office tonight.

Will report my feedback later

cheers

Link to comment
Share on other sites

Just for an update. Tech Support have asked for the Update log

07/17/2008 20:41:33 Device control4_minicontroller added to device list.

07/17/2008 20:41:58 Setting Mini Touch Screen to new address of 192.168.1.105. Setting flag for reconnection on timer.

07/17/2008 20:43:28 No USB detected.

07/17/2008 20:43:28 Checking web interface for versions

07/17/2008 20:43:28 Using supplied URL of http://services.control4.com/Updates/v1_0/Updates.asmx

07/17/2008 20:44:55 No USB detected.

07/17/2008 20:44:55 Checking web interface for versions

07/17/2008 20:44:55 Using supplied URL of http://services.control4.com/Updates/v1_0/Updates.asmx

07/17/2008 20:45:02 Received START_UPDATE message

07/17/2008 20:45:02 Using supplied URL of http://services.control4.com/Updates/v1_0/Updates.asmx

07/17/2008 20:45:02 Starting update...

07/17/2008 20:45:02 Adding devices in project to saved list.

07/17/2008 20:45:02 StartUpdate called.

07/17/2008 20:45:02 New attempt initiated.

07/17/2008 20:45:02 <NewUpdateAttempt/>

07/17/2008 20:45:02 Disabling Navigator for initial update.

07/17/2008 20:45:02 Starting update to version 1.3.2.442. Director version is 1.3.2.442. Using URL of http://services.control4.com/Updates/v1_0/Updates.asmx

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot_1.3.2.438_arm.deb name=umboot

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot_1.3.2.438_arm.deb name=umboot

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-yoda_1.3.2.438_arm.deb name=umboot-yoda

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-yoda_1.3.2.438_arm.deb name=umboot-yoda

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-yoda_1.3.2.438_arm.deb name=umboot-yoda

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-tatung_1.3.2.438_i386.deb name=umboot-tatung

07/17/2008 20:45:07 CreateAllPackages found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-tatung_1.3.2.438_i386.deb name=umboot-tatung

07/17/2008 20:45:07 Removing the loadable packages

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-yoda-cop_1.3.2.438_arm.deb because it matches target version for loadables.

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-pumba-cop_1.3.2.438_arm.deb because it matches target version for loadables.

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-hc300-cop_1.3.2.438_arm.deb because it matches target version for loadables.

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-tatung-cop_1.3.2.438_i386.deb because it matches target version for loadables.

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-tatung-xp_1.3.2.438_i386.deb because it matches target version for loadables.

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-pumba-mc_1.3.2.438_arm.deb because it matches target version for loadables.

07/17/2008 20:45:07 Not deleting file /packages/loadable/navigator-skins-yoda-xp_1.3.2.438_arm.deb because it matches target version for loadables.

07/17/2008 20:45:07 CreatePackageData found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-yoda_1.3.2.438_arm.deb name=umboot-yoda

07/17/2008 20:45:07 CreatePackageData found umboot url=http://c4updates.control4.com/release/1.3.2.442/umboot-yoda_1.3.2.438_arm.deb name=umboot-yoda

07/17/2008 20:45:14 Disk space avail = 818110464

07/17/2008 20:45:14 UPM StartTimer received timer id 643801 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:45:14 cp -f "/packages/navigator-skins-yoda-cop_1.3.2.438_arm.deb" "/packages/loadable"

07/17/2008 20:45:14 cp -f "/packages/navigator-skins-yoda-cop_1.3.2.438_arm.deb" "/packages/loadable"

07/17/2008 20:45:14 cp -f "/packages/navigator-skins-yoda-xp_1.3.2.438_arm.deb" "/packages/loadable"

07/17/2008 20:45:14 cp -f "/packages/navigator-skins-yoda-xp_1.3.2.438_arm.deb" "/packages/loadable"

07/17/2008 20:45:14 Disk space avail = 818110464

07/17/2008 20:45:16 Disk space avail = 818110464

07/17/2008 20:45:26 Unable to locate device with binding id 9309

07/17/2008 20:45:26 Unable to locate device with binding id 9307

07/17/2008 20:45:31 Disk space avail = 818110464

07/17/2008 20:45:46 Disk space avail = 818110464

07/17/2008 20:46:01 Disk space avail = 818110464

07/17/2008 20:46:16 Disk space avail = 818110464

07/17/2008 20:46:26 Unable to locate device with binding id 9309

07/17/2008 20:46:26 Unable to locate device with binding id 9307

07/17/2008 20:46:31 Disk space avail = 818110464

07/17/2008 20:46:36 Unable to locate device with binding id 9309

07/17/2008 20:46:36 Unable to locate device with binding id 9307

07/17/2008 20:46:46 Disk space avail = 818110464

07/17/2008 20:46:49 Disk space avail = 818110464

07/17/2008 20:46:49 Attempting to install Update Service for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Possible error - package name of umboot-yoda_1.3.2.438_arm.deb does not equal computed umboot file name of umboot-yoda_1.3.2.442_arm.deb. Update may fail. Probable problem is with the USB stick or control-4 database.

07/17/2008 20:46:49 Attempting to connect to install update service of device Mini Touch Screen(192.168.1.105). Setting CONNECT_TIMEOUT for device.

07/17/2008 20:46:49 UPM StartTimer received timer id 644012 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Starting CONNECT_TIMEOUT for device Mini Touch Screen(192.168.1.105) because it is in state. We just attempted InstallServer() method.

07/17/2008 20:46:49 UPM StartTimer received timer id 644013 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105) timed out waiting for response. New state is: Updating

07/17/2008 20:46:49 Established socket connection to shell service of device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Sending packet to device Mini Touch Screen(192.168.1.105). Message is: ducati900ss

07/17/2008 20:46:49 Also starting CONNECT_TIMEOUT timer

07/17/2008 20:46:49 UPM StartTimer received timer id 644014 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105):

BusyBox v1.01 (2006.05.11-01:57+0000) Built-in shell (ash)

Enter 'help' for a list of built-in commands.

07/17/2008 20:46:49 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:49 UPM StartTimer received timer id 644016 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Sending packet to device Mini Touch Screen(192.168.1.105). Message is: ducati996

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105):/mnt/jffs2/etc/sysman.d# d

07/17/2008 20:46:49 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:49 UPM StartTimer received timer id 644018 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Sending packet to device Mini Touch Screen(192.168.1.105). Message is: rm /tmp/umboot-yoda_1.3.2.442_arm.deb

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105):ucati996

/mnt/jffs2/etc/sysman.d#

/mnt/jffs2/etc/sysman.d#

07/17/2008 20:46:49 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:49 UPM StartTimer received timer id 644019 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 GetInAddress returned 192.168.1.77

07/17/2008 20:46:49 GetMyIpAddress returning 192.168.1.77

07/17/2008 20:46:49 GetInAddress returned 192.168.1.77

07/17/2008 20:46:49 GetMyIpAddress returning 192.168.1.77

07/17/2008 20:46:49 Sending packet to device Mini Touch Screen(192.168.1.105). Message is: wget -P /tmp http://192.168.1.77/umboot-yoda_1.3.2.442_arm.deb'>http://192.168.1.77/umboot-yoda_1.3.2.442_arm.deb

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105):rm /tmp/umboot-yoda_1.3.2.442_arm.deb

/mnt/jffs2/etc/sysman.d#

07/17/2008 20:46:49 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:49 UPM StartTimer received timer id 644020 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Sending packet to device Mini Touch Screen(192.168.1.105). Message is: dpkg -i /tmp/umboot-yoda_1.3.2.442_arm.deb

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105):wget -P /tmp http://192.168.1.77/umboot-yoda_1.3.2.442_ arm.deb

07/17/2008 20:46:49 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:49 UPM StartTimer received timer id 644021 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Device Mini Touch Screen(192.168.1.105):Connecting to 192.168.1.77[192.168.1.77]:80

/mnt/jffs2/etc/sysman.d# dpkg -i /tmp/umboot-yoda_1.3.2.442_arm.deb

07/17/2008 20:46:49 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:49 UPM StartTimer received timer id 644022 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:49 Sending packet to device Mini Touch Screen(192.168.1.105). Message is: /tmp/umboot.sh

07/17/2008 20:46:50 Device Mini Touch Screen(192.168.1.105):/mnt/jffs2/etc/sysman.d#

07/17/2008 20:46:50 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:50 UPM StartTimer received timer id 644023 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:46:50 Device Mini Touch Screen(192.168.1.105):/tmp/umboot.sh

/mnt/jffs2/etc/sysman.d#

07/17/2008 20:46:50 Received data on the shell port - restart the CONNECT_TIMEOUT timeout

07/17/2008 20:46:50 UPM StartTimer received timer id 644024 for device Mini Touch Screen(192.168.1.105)

07/17/2008 20:47:01 Disk space avail = 818110464

07/17/2008 20:47:16 Disk space avail = 818110464

07/17/2008 20:47:31 Disk space avail = 818110464

07/17/2008 20:47:36 Unable to locate device with binding id 9309

07/17/2008 20:47:36 Unable to locate device with binding id 9307

07/17/2008 20:47:46 Disk space avail = 818110464

07/17/2008 20:47:56 Unable to locate device with binding id 9309

07/17/2008 20:48:01 Disk space avail = 818110464

07/17/2008 20:48:06 Unable to locate device with binding id 9307

07/17/2008 20:48:16 Disk space avail = 818110464

07/17/2008 20:48:17 Unable to locate device with binding id 9307

07/17/2008 20:48:25 Disk space avail = 818110464

07/17/2008 20:48:25 Could not connect to device. Verify the device is powered and has a network connection

07/17/2008 20:48:25 Device Mini Touch Screen(192.168.1.105) timed out waiting for response. New state is: Failed

07/17/2008 20:48:25 Updated: 0 Failed: 1

07/17/2008 20:48:25 Update Package Manager cleaning up ...

07/17/2008 20:48:25 Finished site update attempt

07/17/2008 20:48:25 Device Mini Touch Screen(192.168.1.105) needs updating.

07/17/2008 20:48:25 Received restart update timer id 644220

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.