Thursday, November 15, 2012

US232 FTDI USB -serial trouble clear ini file settings helped

In the end it was simply an error in the  N1MMlogger.ini
But before I came to that I walked some byways..

My new FTDI  US232  USB to serial failed to work with my Radio / N1MM logger Notebook.

Using COM2  with this US232  ( 12345.. all tried as well)
It will not send CW using DTR =CW  as used to with the 
HQ USB-rs232  Prolific chip type.
Since N1MM was generating more and more time out  / overflow errors/ popups with the CAT connection I decided to change to the FTDI type  as this was advised by the N1MM community.
The US232 was installed quick no driver disk was needed and the CAT  connection with N1MM worked instantly.
But to my surprise I could not send CW
Pressing F1 =CQ  RTS  asserts  high, TX is on but DTR stays low. RTS would not return low until ESC was pressed. 

Changing to  TR4W logger using the same USB-serial com2  all is okay!

DTR keys CW , RTS switches T/R  normally.

When I plug this US232 in my other Laptop  it takes COM2  also there it works normal.


DTR is keying CW   RTS is T/R switching like it is configured in N1MM

Also TR4W logger worked normal using DTR RTS and CAT  on com2 on the 2nd PC



The text is distorted by  W7 for free!

When pressing ctrl T  N1MM starts tuning the K3 with DTR high!  So DTR can be controlled by N1MM for the tune command but just not for CW anymore
Some setting must have been altered?

Question is  what process /setting can cause this?

I did reinstall drivers  tried other ports.
The result  is that also the other HQ USB-rs232  that worked okay before is now having the same problem! 

TR4W  logger can use both  converters on this Notebook..
Using TR4W  logger is no option I have tried this before.
This logger is useless but its interfacing seems  good!
N1MM is good but it's interfacing   using CW IF.EXE ????

Strange problems after using N1MM that long, first with a fixed system com-port  and later  on the Laptop using the USB-rs232 with good result.

But it worked best with a normal System USART chip  sure thing.
The USB serial  gave this  CAT errors  more and more  and generates more noise too.

Might have to go back to an old XP  desktop with system comport onboard or  PCI serial card?


Possible  a MOXA USB-serial would be okay  we have many applications at QRL using  MOXA  PCI multi serial ports  C168U  8-ports   and  N-port servers 8 / 16 serial ports  running


Strange thing is that TR4W  is working okay but N1MM will not with the same converter on the Notebook D420 W7pro32.

On the 2nd laptop both work okay in a short test not yet contest proven...
Running a contest is the real test since only then Murphy will come along too..

I am the only one having this problems it seems.

The response delay  and the  frozen  QSO data  I have experienced in the past only seem to happen here.

These USB -serial devices are a real pain in the ass sometimes with unpredictable results.


Could not let rest the subject

I looked into the  N1MMlogger.ini file  this is a text file can be opened with notepad
I use Notepad++ for this
 I could no see any difference between both PC  ini file data

Then I tried N1MM config -> clear ini file settings    all is reset then





Before doing this keep note of settings ..  well for ports setting I had my training by now.

I knew the digi settings and some other tweaks
Need to set comport K3  DTR RTS  Digimode  etc  MMVARI - using sound-card here

Eureka ! DTR was active and CW sound again pff..

Must have been the port address,  2E8  was  set on the Notebook
and now it is 2F8  This was altered by N1MM  I did not change it manually.
Afterwards I remember 2F8 is the default address of com2  3F8 is com1 changing this only could have done the trick.
By switching between USB devices this setting must have changed?
This reset also seems to fix the unwanted DIGI mode changing to GMSK after every band switch.

Now I can test and see if the US232 with its big blue flashing LEDS a bit overdone ..is holding its promise..

until now it has been working without failure so I am hoping the CAT trouble will be over now.



No comments:

Translate