Maybe some of the values in the RAW code is to short.

Frank,

If you upload your "Configuration.xml" file

 Dear Keith,

I wil do that.

Thanks so far

Frank

Santiago wrote:

beoandy wrote:

the only problem i have ist with the mixed macros (b&o and for example epson beamer ir commands in one macro) 

result: complete blocking the beo5 screen till the battery ist empty!!!

firmware 1.41a configuration tool 3.0.0.2

Hello beoandy,

That's exactly my problem too !!! so definitely we are both in the same situation, using this new "software-firmware" combi.

The only solution I've found until now is: delete all the non-B&O commands inside all "mixed" macros 🙁

remember that all those non-B&O commands works very well in stand alone "pure non-B&O" keys though.

Best regards.

Honestly, I'm afraid to upgrade now (so I will not until somebody figures this out), since mixed macros are one of the main reasons I went down this self-programmed Beo5 path.  I hope somebody can help you, because I'd like to upgrade.

Stan

Stan wrote:

Honestly, I'm afraid to upgrade now (so I will not until somebody figures this out), since mixed macros are one of the main reasons I went down this self-programmed Beo5 path.  I hope somebody can help you, because I'd like to upgrade.

Stan

if you need only mixed macros use the beo5 ct version 2.2. if you upgrade to 3.0.02 you can not go back to 2.2 anymore 🙁 (firmeware of the beo 5 goes to 1.41a) - if you need the ct version 2.2 let me know.

Some things i have experienced:

- The new Tool doesen't give you the ability to make Logo Buttons without Pictures. Meaning to use the Font only to send digits. Of course you can create them on your own. But if you have alot of Internet- Radio stations and dont want the pictures for them, you wont be able to use the channellist and have to make every button from scratch. This workd in the previous versions...

- It is nice to have a filter for the Logo's, you can select germany and only get those Logo's. The pre-made filters are worthless though, if you are in another country and have other Logo's you need on a daily basis. It whould be perfect if you could make your own filters. The search command is too time consuming if you have to find every Logo with it.

Over the past couple of weeks I have been reviewing many of the issues raised by the new version 3.0 including the points raised in this thread. I will be posting a complete list in the near future, but I have been currently researching the issue raised by Stan where you apparently get complete battery drain in the same way as happens (correctly) when you update the firmware.

I can confirm that I can now reproduce this problem consistently and whilst more work is needed to identify the exact cause, it appears to be linked to complexed configurations produced with version 2.2 which are subsequently modified/download using version 3.0

When you get the fault situation, the battery will not recharge and shows completely flat until you reload a previously working configuration. Subsequent to loading a previously working configuration, the battery returns to fully charged situation in a matter of minutes.

If other members have seen this problem I would be pleased if they would be so kind as to post their observations here to help narrow down the issue to a point where at least we can work around the issue

Whilst I believe B&O intended version 3.0 to be backward compatible with configurations produced by version 2.2, there are many situations where this is not the case particularly related to logo templates and modification of their IR commands.

beoandy wrote:

Santiago wrote:

beoandy wrote:

the only problem i have ist with the mixed macros (b&o and for example epson beamer ir commands in one macro) 

result: complete blocking the beo5 screen till the battery ist empty!!!

firmware 1.41a configuration tool 3.0.0.2

Hello beoandy,

That's exactly my problem too !!! so definitely we are both in the same situation, using this new "software-firmware" combi.

The only solution I've found until now is: delete all the non-B&O commands inside all "mixed" macros 🙁

remember that all those non-B&O commands works very well in stand alone "pure non-B&O" keys though.

Best regards.

perhaps santiago an i are the only one with this problem? who can help to solve this problem?

 

i testet a configuration made with 3.0.0.2 and with some before.  always the same problem.

please help!

Hello Beoandy,

I regret to confirm your problem and I have not found a work around to the issue yet.

It is very disappointing that extra functionality has been added to the Beo5 Configuration Tool which has caused previously working functions to be unavailable. Whilst I think it was intended that the version 3.0 should be backward compatible with configurations made with 2.2, it is not. Worst still, they clearly did not re-test all the functionality before release of 3.0 because the issues are so obvious.

The software quality assurance processes which most "best practice" software company's use clearly have not been adopted at B&O or by their software sub-contractors which is very disappointing given that B&O prides itself on quality when it comes to physical products. B&O seems unable or unwilling to understand that software development requires far different processes, procedure and associated skills than making a physical product.

Whilst I am a very strong supporter of the Beo5 and want it to be very successful, I find myself being highly critical of the software and firmware development particularly of this latest version given the amount of time the product has been on the market. It may be a tool for the dealers, but if the dealers are unable to produce a workable configuration for their customers with minimum technical knowledge themselves is one reason why so many dealers are understandably not willing to produce anything other than a very basic configuration for their customers, which in turn causes dis-satisfaction.

As previously stated I am compiling a detailed list of issues which I will publish soon of which the problem you highlighted is one of them.

I have been able to implement "work arounds" for many of the issues, but as yet not this one.