Convert existing EA or create new EA/Script to automate csv file sending

MQL5 Integration Sonstiges

Auftrag beendet

Ausführungszeit 21 Tage
Bewertung des Kunden
Great work, continuous dialogue and assistance throughout a tricky job.
Bewertung des Entwicklers
Great client, thank you for interesting job. Hope to work in the future.

Spezifikation

Ultimate aim is for an MT5 EA/Script to create and send a CSV file of each trade or pending order making a seamless automated process.

Pathway is MT5 to winSCP (https://winscp.net/eng/download.php) using PuttyGen (public/private key pair).


MT5 CSV output must have following format:


File name

The file name should have the following format:

lpxd_external_advisors_XX_yyyymmdd-HHMM.csv


File content

The file example below is for futures, but applies to equities as well. For equities, please use instrument Ric code for “internal_code”.

Here is a description of each column of the file:

1. “id_specific”: your QSEC id – here, the name/initials XX/Xavier Xander are used. Your QSEC id will be communicated to you by QRT.

2. “extra_key”: primary key of the file. Each value in a given file should be unique. A good way to generate it is to concatenate the columns “strategy” and “internal_code”.

3. “value_ts”: timestamp when you generated the file, preferably in UTC. Format is ‘yyyy-mm-dd HH:MM’. Used for audit purpose only.

4. “strategy”: name of the strategy generating the associated targets. Only used for audit purpose.

5. “internal_code”: QRT’s identifier for instruments. A mapping between usual tickers (Bloomberg, Ric..) and “internal_code” will be sent to you by QRT once you provided the list of the instruments you want to trade. “internal_code” should be Ric codes for single stocks.

6. “ric”: Ric code of the instrument. Used for audit purpose only. Can be filled with the value of “ticker” or “internal_code” if you don’t have Ric code.

7. “ticker”: Bloomberg ticker of the instrument. Used for audit purpose only. Can be filled with the value of “ric” or “internal_code” if you don’t have the Bloomberg ticker.

8. “target_notional”: targeted amount (in currency, not shares/number of contracts) in for the instrument.

9. “currency”: currency used for “target_notional”.

10. “target_contracts”: number of contracts/shares associated with the “target_notional”. Used for audit purpose only.

11. “ref_price”: instrument price when generating the file. Used for audit purpose only.

12. “advisor_name”: advisor name


Attached is the closest thing I could find that already exists in MQL, it maybe of use it may not.

A full PDF explaining requirements is available but unfortunately I cant upload it here.




Bewerbungen

1
Entwickler 1
Bewertung
(204)
Projekte
326
43%
Schlichtung
34
32% / 29%
Frist nicht eingehalten
83
25%
Frei
2
Entwickler 2
Bewertung
(27)
Projekte
43
7%
Schlichtung
18
6% / 78%
Frist nicht eingehalten
26
60%
Frei
Ähnliche Aufträge
I am looking for an experienced MQL5 or MQL4 developer with a strong background in low-latency algorithmic trading, market data integration, arbitrage and execution optimization. The project involves developing a high-performance HFT Expert Advisor (EA) for XAUUSD or US30 on IC Markets that is designed for robust execution in both demo and live environments. The EA may use market data feeds (such as lmax,one zero or
I need to replicate the trade i take on prorealtime to mt5 The bridge must be designed to transfer my positions from ProRealtime to MetaTrader 5 on VPS PC. Opening the transaction in the ProRealtime , i must see automatically the same deal in myMetaTrader. Changing my stop orders in the ProRealtime should also change my orders in MetaTrader

Projektdetails

Budget
50 - 300 USD
Ausführungsfristen
von 1 bis 10 Tag(e)