Error 053 with zorro 1.44.1

Hi

I get error 053 for some assets which have different name at my broker when I try to update the assetsfix list. I have added the right name of those assets in the symbol column but the problem is still there. Those assets are updfated correctly if I add a new line to the assetslist with the asset name of the asset at that broker.
I thought it is a problem with the 1.41.9 zorro version I was using so I used 1.44.1 with bridge 1.9. I use the same account list and assetfix and assetbroker files with both zorro 1.44 and 1.41. With 1.44.1 I get the 0.53 asset unavailable error not only for those assets I had error before but also for many other assets like GBP/USD.

btw... I have problems editting those assets files with excel. I tried to look in internet to have the right configuration and to save them correctly but each time I open zorro again, I get a 064 error when I open zorro again so I have to edit those files in a text editor. Where can I find out how to configure excel correctly?

Has some of you experience similar issues?

Excel uses your local separation character. Make sure in your PC regional settings that it's a comma, and the decimal is a point, otherwise Excel can not read standard CSV files. Zorro accepts both commas or semicolons.

For the symbol issue, check which symbols your broker requires. Slashes are automatically removed by the API plugin. If you use MT4, make also sure that you've assigned the Zorro EA to a EUR/USD chart. Otherwise the asset name is not automatically converted. You can see in the Experts log how your asset name is translated, so it should not be difficult to find the reason of the problem.

Thanks. Problem solved.

I thought it maybe a bug at 1.44.1. I did not know that the chart has to be at eurusd to download the asset data correctly.

I had the local separation ok at my pc. The problem was that I was not saving the assetsfix file correctly after I wrote the right symbol name into that column. So the symbol was written there after I opened the file again but the file was not saved correctly so zorro could not detect the new name on that file.