Yes, I also have the questoin same as you.

Thanks for the clarification Popov.
I am glad you are working on a new software...
But is it going to allow custom indicators? EA studio and mqlgen don't allow that only fsb pro

I HAVE TRIED TO IMPLEMENT IT FOR MT5 BUT ITS QUITE TOUGH....PLEASE CAN YOU HELP....

After studying this MT4-FST Library code in detail, I can provide you with a comprehensive analysis and recommendations for building communication between MT5 and FSB Pro.

## Analysis of the Current Architecture

The current MT4-FST Library uses a **named pipes** communication system with this structure:

```
Forex Strategy Trader (FST) ↔ MT4-FST Library DLL ↔ MT4 Expert Advisor
```

Key components:
1. **MT4 Expert Advisor** (`MT4-FST Expert.mq4`) - Runs in MetaTrader 4
2. **Bridge DLL** (`MT4-FST Library.dll`) - C++ DLL that handles communication
3. **Named Pipes** - Inter-process communication between FST and DLL
4. **Client/Server model** - DLL acts as server, FST acts as client

## Options for MT5 Integration

### Option 1: Complete Rebuild (Recommended)

You'll need to rebuild the bridge completely because:

1. **MT5 API is fundamentally different** from MT4
2. **MQL5 is object-oriented** vs MQL4's procedural approach
3. **Different DLL import mechanisms**
4. **Changed order management system**

#### Steps for Complete Rebuild:

**A. Create MT5 Expert Advisor (MQL5)**
```cpp
// New MT5 version would need to handle:
// - Different account information structure
// - New order management functions (PositionGet, OrderSend)
// - Different symbol information structure
// - MQL5's object-oriented approach
```

**B. Create New Bridge DLL (C++)**
- Update to use MT5's API structures
- Maintain similar named pipes communication
- Handle MT5's position-based system vs MT4's order-based system

**C. Modify FSB Pro Client**
- May need updates to handle any protocol changes
- Keep similar command structure if possible

### Option 2: Proxy Approach

You could create a proxy that translates between MT4 and MT5:

```
FSB Pro → MT4-FST Proxy → MT5 Expert
```

This would involve:
1. Running the existing MT4-FST Library
2. Creating a translation layer that converts MT4 commands to MT5
3. Developing an MT5 expert that understands the translated commands

### Option 3: Hybrid Approach

Use the existing DLL communication but create a new MQL5 wrapper:

```
FSB Pro → Existing DLL → MQL5 Adapter → MT5 Native Functions
```

## Recommended Best Practice

### 1. **Complete Rebuild with Protocol Preservation**

I recommend a complete rebuild but preserving the communication protocol where possible:

**Keep the same:**
- Named pipes communication
- Command structure (PI, SI, MA, OS, OC, etc.)
- Basic message format

**Update:**
- MT5-specific data structures
- New position management system
- MQL5 function calls
- Error handling for MT5

### 2. **Implementation Steps**

**Phase 1: MQL5 Expert Advisor**
```cpp
// Create new MT5 version with:
class MT5FSTExpert : public CExpert
{
    // Handle MT5's event-driven model
    // Implement OnTick, OnTrade, OnTimer
    // Use PositionGet*, OrderSend* functions
}
```

**Phase 2: Updated Bridge DLL**
- Update data structures for MT5
- Maintain backward compatibility with FSB Pro
- Handle MT5's different market data format

**Phase 3: Testing and Optimization**
- Test with MT5's strategy tester
- Optimize for MT5's multi-currency/multi-timeframe capabilities

### 3. **Key Technical Challenges**

1. **Position vs Order Management**: MT5 uses position-based accounting vs MT4's order-based
2. **Hedging Mode**: MT5 has different hedging capabilities
3. **Symbol Specifications**: Different market info structure
4. **Execution Model**: MT5's more complex execution model

### 4. **Sample MQL5 Structure**

```cpp
#include <Trade\Trade.mqh>
#include <Trade\SymbolInfo.mqh>

class FST_MT5_Bridge
{
private:
    CTrade trade;
    CSymbolInfo symbol;
    int connection_id;
   
public:
    bool Connect(int id);
    void ProcessTick();
    void HandleFSTRequest();
    // ... other methods
};
```

## Conclusion

**You need to rebuild the bridge completely** but can preserve much of the communication protocol. The named pipes approach and command structure can remain similar, but the MT5 integration layer must be entirely new due to fundamental differences between MT4 and MT5 architectures.

The most efficient approach would be to:
1. Study MT5's API thoroughly
2. Create a new MQL5 expert advisor
3. Update the bridge DLL for MT5 compatibility
4. Maintain the existing FSB Pro interface

This preserves your investment in FSB Pro while creating a modern MT5-compatible solution.