Log4OM

Bonsoir Eric,

that's the Magic built in Log4OM


73
Roland

gm Terry
ah may be where ? because morning i check again setup in log4om and i cant see anywhere xml rpc ..only in flidigi i can see 73 Eric

Roland
i check , its ok i have same that you..in TCP-IP sessions

73 Eric

F1SMV wrote: 29 Jan 2020, 07:07 gm Terry
ah may be where ? because morning i check again setup in log4om and i cant see anywhere xml rpc ..only in flidigi i can see
fldigixml.PNG

73 Eric

Not sure what version of FLdigi your using but it should be 4.1.08 or later and you need the I/O config tab not rig control

sorry if I insist, but I think that Eric's problem continues to be the com port is not split.
N8VBvcom does not do this but only virtual com.
The original problem was no TX

Bonjour Terry

i use fldigi 4.1.09.12 version ...

Mark
do you think i must back on vspe ? ..but i try without more success..

this morning i test in same cfg my "old version" of log4om (version 1), work ! tx is ok

for your info i put my setup , i see tcp port arent the same does i must change in misc\tcpip sessions ?
73 Eric

Indeed Eric.
I don't remember if in V1 I used the com splitter port.
Certainly V2 does not command TX via TCP / IP, or at least it does not work for me.
This is why I insist on splitting the com port.

@ Terry: Can Log4OM V2 send the rig in TX via TCP/IP?
Thanks

IK0TIX wrote: 30 Jan 2020, 09:05 Indeed Eric.
I don't remember if in V1 I used the com splitter port.
Certainly V2 does not command TX via TCP / IP, or at least it does not work for me.
This is why I insist on splitting the com port.

@ Terry: Can Log4OM V2 send the rig in TX via TCP/IP?
Thanks

No and neither did V1, PTT is triggered within FLDigi

GM
in earlier versions of fldigi the connection of log40m v1 with fldigi worked without a problem, now these versions of fldigi do not want to work even with other software, as separate software works without a problem. this is my observation
Regards

HI Eric
FLdigi 4.1.09 has new look of Configuration window and look on picture where you find TCP-ip session.
It is working for me.
73 Bojan S51CN