Replies

ac@arconomy.digital
07 Jun 2023, 14:23

RE:

Hi Panagiotis,

Thanks again - I understand how to calculate the LotSize value now.

Is there a field that returns the name of the units.

For example..

For UK100:

lotSizeName: '"indices"

 

For EURJPY:

LotSizeName: "EUR"

 

Many Thanks

Ac

 

PanagiotisChar said:

Hi again,

And the other bit? Is there any way of getting the units for the Lot Size? ("Indices" for UK100  or "EUR" for EURJPY

Just divide the lotSize by 100.

Aieden Technologies

Need help? Join us on Telegram

Need premium support? Trade with us

 


@ac@arconomy.digital

ac@arconomy.digital
07 Jun 2023, 11:37

RE:

ok - great thanks. So ctrader is just storing the lot size an INT on cTrader side.

And the other bit? Is there any way of getting the units for the Lot Size? ("Indices" for UK100  or "EUR" for EURJPY)

Many thanks

ac

 

 

 

PanagiotisChar said:

Hi there,

It's a technical decision taken by the team so that they do not have to deal with numbers with decimals and its the same for all symbols.

Aieden Technologies

Need help? Join us on Telegram

Need premium support? Trade with us

 


@ac@arconomy.digital

ac@arconomy.digital
07 Jun 2023, 11:23

RE:

Hi Panagiotis,

Why 100? Is the same for all assets for all brokers on cTrader? 

I think this maybe the number of contracts (CFD's) in the lot - but is it always guaranteed to be 100 for all assets?

Is there any way of getting the units for the Lot Size? ("Indices" for UK100  or "EUR" for EURJPY)

Many Thanks

ac

 

 

PanagiotisChar said:

Hi there,

To make it simple, just divide everything by 100.

Aieden Technologies

Need help? Join us on Telegram

Need premium support? Trade with us

 

 


@ac@arconomy.digital

ac@arconomy.digital
06 Apr 2020, 01:17

RE:

ac@arconomy.digital said:

Did you mange to solve this? I am having the same issue.

The issue for me was the timeout being too short.

In the ProtoMessageReceiver class update the timeout.

private static final int TIMEOUT_WAITING_MSG = 2000;

@ac@arconomy.digital

ac@arconomy.digital
05 Apr 2020, 01:55

Did you mange to solve this? I am having the same issue.


@ac@arconomy.digital

ac@arconomy.digital
17 Jan 2020, 13:30

RE:

PanagiotisCharalampous said:

Hi ac,

The message asks you to set the sequence number to 10 (36=10). Any change you are sending another message in between? 

Best Regards,

Panagiotis 

Join us on Telegram

I found the issue. I am using QuickFixJ and there was an error saving the parsed response from the initial market order that seemed to cause a retry to send the message in the background.

 

Thanks again for your help pointing me in the right direction with the MsgSeqNum.


@ac@arconomy.digital

ac@arconomy.digital
17 Jan 2020, 11:49

RE:

PanagiotisCharalampous said:

Hi ac,

cTrader FIX API does not support subscription to position updates. Regarding the position report issue, make sure that you are sending the correct message sequence number. You can also check our FIX API example on how to request for positions.

Best Regards,

Panagiotis 

Join us on Telegram

 

Thanks for getting back to me Panagiotis.

The sequence number appears correct to me - here are the sequence of messages;

Place Market Order message Sent (msgSeqNum 34=8):

8=FIX.4.49=16435=D34=849=PEPPERSTONE.332708850=TRADE52=20200117-08:59:17.83456=CSERVER57=TRADE11=ORD_1_TEST_STRATEGY38=140=154=255=1001159=160=20200117-18:59:17.83210=197

fromApp response (msgSeqNum 34=8):

8=FIX.4.49=21135=834=849=CSERVER50=TRADE52=20200117-08:59:18.14356=PEPPERSTONE.332708857=TRADE11=ORD_1_TEST_STRATEGY14=037=6613446438=139=040=154=255=1001159=360=20200117-08:59:18.006150=0151=1721=3672374310=035

Position Request message Sent (msgSeqNum 34=9):

8=FIX.4.49=15335=AN34=949=PEPPERSTONE.332708850=TRADE52=20200117-08:59:25.43656=CSERVER57=TRADE710=a5ee13e4-60a0-471d-a695-42565fb51060_1579287563721=3672374310=072

Admin Response (reset to msgSeqNum 34=8):

8=FIX.4.49=13035=434=843=Y49=CSERVER50=TRADE52=20200117-08:59:25.55356=PEPPERSTONE.332708857=TRADE122=20200117-08:59:25.55336=10123=Y10=135

Can you see anything wrong with the message structure of the position Request?

Many Thanks

ac


@ac@arconomy.digital