Error attempting download from B&W C-Touch to SPICED

Fair enough - and I agree that the context of the terms depend somewhat on people's background and also their perspective. For example, the transfer of data from PC to Touchscreen would be a "download" from the point of view of the Touchscreen Developer / Engineer.

Cheers, JC

 

You may have just provided us with an important clue as to what is happening. We have had other users report this problem, but I was unaware that they may have applied this series of steps. We will look into what can be done to prevent this.

This is correct.

Once it gets into this state, it is very hard to fix. It will need to be returned to CIS.

You only have a very brief "window of opportunity" to connect to the unit once it is in this state. If you time it just right, you can sometimes get it to connect.

You said previously that you had never been able to connect to the unit via serial. If you have tried all of the things in the FAQ, it may be related to your computer. Some computers (laptops in particular) have serial ports which are not within the RS232 specification, and they are unable to communicate reliably with the C-Touch. In this case, you will need to use a different computer or try a plug-in serial adaptor.

 

I have just checked and found that if you download a project to C-Touch via C-Bus, you get a message like :

Confirmation 14619

Please confirm that the following unit details are correct.
Failure to do so may damage the unit.
Network = Local Network
Unit Address = 23
Firmware Version = 2.0.00 - 2.19.99

YES NO HELP

I would have thought that this would be enough to prompt someone to check that the version was correct. Should it be worded differently ?

 

XDarren, that dialog message is fine for you developer guys, but a user cannot be expected to even KNOW what "firmware" means, let alone how to find out what it is. We expect that if we buy a brand new product (C-touch) and download the latest software to run it, then the 2 will be compatible straight out of the box.

Yes, I know the dialog asks for stuff to be checked, and even warn that the unit might be damaged... but, ummm (how do I explain this?)... we users haven't got time to decipher these obscure messages, and we might assume that it's just a warning that we are going to over-write the current programming or something.

Since the Firmware Version is held and is display-able within the unit, why not simply interrogate the unit (in software, via Cbus) and ensure that the new programming will be compatible? And don't even OFFER a "yes" option if there is even the slightest chance that it won't work.

Toolkit reports the Firmware version doesn't it? And it reads that via Cbus? Well, it works for switches but not so well for Ctouch, but it should. I just checked a current project I am working on and Toolkit 1.1.9 has stored in the Database that a B&W Touch with Serial 001001973708 is running Firmware 4.4.00. Now, I KNOW that the unit is running firmware 1.9 so there's a bit of a problem, eh...

Cheers, John

 

Not quite that simple John. There are multiple microprocessors in lots of these products. The Firmware version that Toolkit reports is the C-Bus interface firmware version. The 1.9 etc. firmware version stuff is the version of the main CPU that controls the screen. Which version number do you want Toolkit to display?

 

It's not *ME* that wants to read the firmware version - it's PICED that needs to read it properly... the thread above details the problems that occur when PICED is used to install a B&W C-touch program via Cbus.

The C-touch Firmware need to be updated to v2.x, but PICED doesn't detect v1.9 firmware when downloading over Cbus (rather than direct Serial connection), so PICED allows the install and resultantly kills of the touchscreen.

However, if PICED and/or Toolkit could read the Firmware correctly, it'd be trivial to add a software routine that prevented the user from proceeding with the download.

JC

 

Toolkit *should* show both. But it doesn't. This is a known issue and is planned to be addressed in a future version.

 

Thanks Darren, at least I know what the problem is now.

Is there anything I can do myself? I believe the unit may be outside of its warranty period, and I don't just want to throw it. Would it be possible to effect a fix to this situation via a future upgrade of the PICED software? Could you send me a specific fix in software form? As a last ditch measure, is there anything I can achieve by dismantling the unit itself !?......you do suggest that it is 'very hard to fix' but not impossible?

No, to be fair it is quite clear. However, I made the (false) assumption that the firmware on the unit would be the latest one. Also I assumed that any firmware would be updated via C-bus if this was required. It was only later that I read that C-Touch firmware updates are not possible via C-bus.

Sorry, not possible for me, even with my desktop PC


Thanks again....hope you can help further.

P.S. Very impressed by your INSTANT response last time!!

 

No. Unfortunately, the unit needs to be dismantled and connected to some special equipment to re-program the unit.

It will not be necessary to throw the unit away. Have a talk with your helpful local CIS representative. I am sure that they can get it sorted out for you.

Unfortunately, if you can't connect to the unit, there is nothing the PICED software can do.

We are going to make it so that the firmware version can be read via C-Bus in the future to make it impossible for this to happen.

You are most welcome. I am very grateful that you have provided me with enough information to understand what has happened. Other people appear to have done the same thing but have never provided the critical information needed to understand the cause, and it has been driving me crazy...