Hello, I need some help, please!

I have established a PPP connection over USB from my PC to a DT80. I can connected to the Dex interface through 1.0.0.3 and can ping the PC from the DT via 1.0.1.3. All good so far.

The problem is when I try to move data from the DT to the FTP server running on the PC. The DT does not have an Ethernet cable attached, just the USB. When sending the following command:

COPYD dest=ftp://USER: PSWD@1.0.1.3:50087

The DT responds with:
DT80> ETH SESSION: Starting
ETH SESSION: Failed [No cable]

I'd prefer to not have an Ethernet cable attached for this to work, but I have plugged one in anyway, and tried again. After this, the Ethernet session starts, and successfully loads the data file into the queue. However, every attempt to connect to the FTP server fails:

ETH SESSION: Starting (alarm/unload)
ETH SESSION: Ready (192.168.99.123)
Unload complete.
FTP: Connecting to server 1.0.1.3 (1.0.1.3)...
FTP: cannot connect to server (-2)
FTP: Failed - will retry
ETH SESSION: Completed

There is no firewall active. I am able to ping the PC just fine.
The FTP connection from the DT to the PC works fine over the Ethernet connection, so I know the FTP server is working.

Can anyone help me understand:
1) why I need to have an Ethernet cable attached to use FTP over PPP?
2) why I cannot connect to the FTP server over PPP, but it works fine over Ethernet?

Thank you in advance!

Hello, further to my previous post, I tried turning the Ethernet port off, and also tried connecting to the FTP server with P56=8 for further detail. Nothing helps, and surprisingly, the P56 parameter does nothing. The summary of the communication follows:

NO ETHERNET CABLE ATTACHED, ETHERNET TURNED OFF

PROFILE ETHERNET ENABLE=NO
P56=8
PING 1.0.1.3
COPYD dest=ftp://HUSKY: DT@1.0.1.3:50087

** RESPONSE *

DT80>
DT80> /h/E/M/R
DT80> PROFILE ETHERNET ENABLE=NO
DT80> P56=8
DT80> PING 1.0.1.3
1.0.1.3 responded in 16 ms
DT80> COPYD dest=ftp://HUSKY: DT@1.0.1.3:50087
DT80>
Unloading: UNTITLED A Data (280 records) -> ftp://HUSKY: DT@1.0.1.3:50087/011_20180828T204723.CSV
ETH SESSION: Starting (alarm/unload)
ETH SESSION: Failed [Disabled] - will retry
Unload complete.

NO CABLE, ETHERNET ENABLED

PROFILE ETHERNET ENABLE=YES
P56=8
PING 1.0.1.3
COPYD dest=ftp://HUSKY: DT@1.0.1.3:50087
SESSION LIST

** RESPONSE *

DT80> PROFILE ETHERNET ENABLE=YES
DT80> P56=8
DT80> PING 1.0.1.3
1.0.1.3 responded in 16 ms
DT80> COPYD dest=ftp://HUSKY: DT@1.0.1.3:50087
DT80>
Unloading: UNTITLED A Data (280 records) -> ftp://HUSKY: DT@1.0.1.3:50087/012_20180828T205126.CSV
Unload complete.
SESSION LIST
Email Alarm Queue (0/13):
Email Data Queue (0/13):
FTP Data Queue (1/12):
2018/08/28,20:51:27: 1.0.1.3, /012_20180828T205126.CSV, iface:eth, prio:norm, retry:0 (2018/08/28,20:51:27)
Ethernet session retry:3 (2018/08/28,21:18:24)

(...does nothing...)

ETHERNET CABLE ATTACHED, ETHERNET ENABLED

PROFILE ETHERNET ENABLE=YES
P56=8
PING 1.0.1.3
COPYD dest=ftp://HUSKY: DT@1.0.1.3:50087
SESSION STOP
SESSION CLEAR
SESSION LIST

** RESPONSE *

PROFILE ETHERNET ENABLE=YES
DT80> P56=8
DT80> PING 1.0.1.3
1.0.1.3 responded in 16 ms
DT80> COPYD dest=ftp://HUSKY: DT@1.0.1.3:50087
DT80>
Unloading: UNTITLED A Data (280 records) -> ftp://HUSKY: DT@1.0.1.3:50087/016_20180828T210256.CSV
Unload complete.
FTP: cannot connect to server (-2)
FTP: Failed - will retry
FTP: Connecting to server 1.0.1.3 (1.0.1.3)...
FTP: cannot connect to server (-2)
FTP: Failed - will retry
FTP: Connecting to server 1.0.1.3 (1.0.1.3)...
FTP: Failed - will retry
ETH SESSION: Completed
SESSION STOP
dataTaker 80 E114 - Command parameter error at column 13 [ SSION STOP<err> ]
DT80> SESSION CLEAR
DT80> SESSION LIST
Email Alarm Queue (0/13):
Email Data Queue (0/13):
FTP Data Queue (0/12):
DT80>

Hi pml7154,

PPP connection over USB will give you virtual TCP/IP connection, however you may need to set up your FTP server setting in order to utilise local host IP address.

Best regards,
Rudy Gunawan

Thank you, Rudy, I will give that a try.
I'm wondering, though, why an Ethernet cable needs to be plugged into the DT for the PPP connection to work. That is, when attempting to connect to the FTP server via PPP with NO Ethernet cable attached, the DT won't even unload the file in the session queue, and cites no cable attached as the problem.

Well, I looked into this, and the FTP server is listening on local host 127.0.0.1, so I would think that any incoming data on the FTP port would reach the server. When I have the DT execute a COPYD command to the same FTP server, but over a "real" Ethernet connection, it works fine and in this case, the FTP server is still listening on the local host IP of 127.0.0.1. Then, if the only thing I change is the connection from Ethernet to PPP, it fails.

FYI, DT firmware is at the latest revision.

Hi pml7154,

The reason behind Ethernet cable must be connected is because sending data via local-host IP address is not supported by COPYD command.
COPYD only acknowledge Ethernet or modem connection in its option.

Doing FTP transfer via PPP is not an easy work because basically you have to trick the logger into using local-host address.
And some difficulty also come from FTP server setting.

If you are using Filezilla server, please try to manually assign loop-back IP into target IP address.

Best regards,
Rudy Gunawan

Thank you for the information on why the Ethernet cable needs to remain attached.

As for the PPP connection to my FTP server (and it is FileZilla) I must apologize because I don't understand how to do what you are asking. I've searched the options for the server and I see no option to map an incoming connection on 1.0.1.3 to 127.0.0.1 (if that is what you are asking). Currently the server is running on the same PC that is connected to the DT via PPP. The server is listening @ 127.0.0.1, which is the local machine, so I must admit I'm a bit confused. I can ping 1.0.1.3 from the DT and receive a response.

Are you able to show me where to create this mapping in the options screen in FileZilla (0.9.60)?

Thanks in advance.

Hi pml7154,

Can you please check passive mode setting?
You can define the IP address on the second option.

Best regards,
Rudy Gunawan