Oanda cannot update the Oanda plugin, nor would that help with a wrong lot amount. They must update the lot amount in their API.

If it only happens with a direct connection, that would explain why some people have that problem and others not. We'll check if we get also the wrong lot amount here, and will then contact Oanda for solving the problem. Please stay tuned.

Ok, it seems that the problem is more complicated. The lot amount was in fact correct, but the the order units were changed from lots to contracts. Therefore the too large size,.

Please download a new Oanda plugin here: https://opserver.de/down/Oanda.zip

Please let me know if the problem still happens with that plugin.

I will re-start the TS next January and report any issues will arise. Will the new plugin be included in the 2.44 upcoming release. Will it be "compatible" with the new Oanda Asset list just announced with the same version?

Thank you

Looks good, just saw my script opened 1 Lot which now is 0.1 contracts on Oanda.

Thanks for the fix JCL. I can confirm that it rectifies the issue for Index CFDs but there is now an issue with the FX amounts.

The fix is impacting the order sizes for FX transactions. An example is an order for 10,000 Lots of USDCAD, where 1 Lot = 1, is now only transacting 1,000 USDCAD, 10 times less. The fix seems to have been applied across all products traded on Oanda rather than only the Index CFDs.

This is having unintended consequences with open positions which flips directions, close out long and then go short for example. Zorro now thinks my outstanding position sizes are 10 times smaller. Close orders are less than the actual open positions which are then followed by an order to open a new position in the opposite direction which results in Error 75 because my original position was never completely closed.

Can you have a look at the fix with the Oanda plugin and address this situation?

Now also getting another error message from Oanda:

"market_order_reject","rejectreason":"units_precision_exceeded","instrument":"eur_nok","timeinforce":"fok","positionfill":"reduce_only","reason":"trade_close","tradeclose":{"units":"5045.900000","tradeid":"464"}},"relatedtransactionids":["623"],"lasttransactionid":"623","errormessage":"the units specified contain more precision than is allowed for the order's instrument","errorcode":"units_precision_exceeded"}
Error 075 [EUR/NOK:Trend:S00464] - close attempt 2, 50459@10.27 at 10:00:02

Decimal places not permitted for currency orders. Decimals only permitted for Index CFD because of the change earlier this year to lower minimums.

I'm not getting that problem here, so let's find out what it is.

- Make sure that you have the latest Zorro version 2.44.4, the release candidate.
- Select your Oanda demo account and run the TradeTest script. Open and close some positions. If the problem then still happens, please post the log.
- If the problem only happens with your script, but not with TradeTest, please contact Support. They will then look into your script and try to reproduce the problem.

I upgraded to the latest version 2.44.4 and ran the TradeTest script. All tests out fine.

Now running my script. Will see what happens.

I can confirm that everything is finally working as should be now. The updated Oanda plugin was conflicting with the older Zorro version 2.30.

Thanks for all your help jcl!

I thought the issue was resolved but maybe it isn't?
With the new Oanda.dll, I reset the z12 instance I have running after getting the same error JayWilly reports above "the units specified contain more precision than is allowed for the order's instrument". I closed all trades and restarted everything, assuming this was happening with trades that were opened with the old plugin. But now it's happening with trades that were opened with the new plugin, too...



Zorro tries to close 91.1 units. The open position is 911 units. The log also correctly prints that 911 Lots are supposed to be closed. But the order comes out wrong. This is with the new Oanda.dll posted in this thread, I made sure. And since this is a Z system, I can't fix this in the code. Version 2.40

Edit: Just want to add that the same instance managed to correctly close a USD/CAD position before that. Whatever that means.