www.dl2rum.de

Dear RUMLogNG users,

I am currently considering to switch to RUMLog since the microHAM MKII seems to be much better supported compared to my current logging program. The only issue is, that do not get it to work with my setup.

I am running a FT1000MP MARK-V with a microHAM MKII (FW 6.12) connected. The connection between RUMlogNG and the MKII seems to be OK, although I am not able to switch the MKII mode but the settings can be written and also the MKII is connected in the microHAM window.

Somehow the MKII seems not be connected to my FT1000MP MARK-V since when the VFO A Frequency is not visible in MKII display and of course not in RUMlogNG and the MKII is not following the mode of the MK1000MP MARK-V..

Maybe someone has a similar setup and may give a hint?
Below are my settings, maybe there is something wrong there?

Thanks
Alex, DC1LEX

Displaying frequencies in the MKII isn't supported for the FT-1000MP. I could add it.
First you have to get CAT working. The port settings are correct?

Thanks Tom for answering.
Which port settings do you mean? In RUMlog?
I posted the settings as pictures and those should be OK I think?

Yes. I don't know which settings the FT-1000 requires.

So what I found out so far:

- using uHRouter (http://www.w7ay.net/site/Applications/Router/index.html) and my other log program everything works fine
- using uHRouter I am able to read the VFO frequency and then also the CAT symbol on the FT1000MP display lights up

- using RUMlog (without uHRouter) I have access to the mKII but the mKII does not connect to the FT1000MP since the CAT symbol on the FT1000MP never lights up

Is there anything like a debug log or error log in RUMlog where I can see what maybe is going wrong?

Thanks
Alex, DC1LEX

as a serial Interface the FT1000MP needs 4800,N,8,2 (4800 baud, no parity, 8Data bits, 2 Stop bits). But since the radio is connected to the mKII it should be handled by the mKII, right?

Thanks
Alex, DC1LEX

The MKII is handling nothing! As soon it is connected to a host, it acts just a deaf CAT interface. It's all in the host software.
There may be a problem with the CAT interface in RUMlog.

1. Try to get CAT running without the MKII.

When this fails, I would like to connect to your trx remotely using this tool: http://dl2rum.de/RUMlogNG/TCP2Serial.zip

without the MKII it works...

Good news. I can't see an issue with the MKII yet. YAESU doesn't need flow control?

No, no flow control...