If I run reports or customize a form while at the same time connected to a DX Cluster through Telenet, LOGic will crash eventually.

I need to disconnect from the cluster before doing those things and reconnect after I'm done.

73 de K1ESE
John

Dennis -

Any update on this? If I want to do anything in the Tools menu or in the Reports menu or in the QSL menu, LOGic will crash if telenet is enabled. If I turn off telenet, use those menus, and then turn telenet back on, LOGic still crashes. It's getting to be very frustrating. I have to start and stop the program between each activity. I suspect my Windows 7, 64-bit is not helping.

Anyway, any progress on this?

73 de K1ESE
John

Peter -

Thanks for the offer. I took 15 minutes and generated these three types of errors -

Error type 1
Start LOGic
started telenet
import lotw qsls
click on needed spot in spot log
index error, other database error messages
You can only clear the message box by clicking cancel and that causes program to quit

Error type 2
Start LOGic
started telenet
exported some qsos via adif
"LOGIC.exe has stopped working" Windows 7 error message
Restarting LOGic requires CLEAN
(This is the most common error)

Error type 3
start logic
telenet started
Reports - Awards - DXCC - CW -
RunPRG:An error occurred in ....
Error #11 Function argument value, type, or count is invalid
This type of error doesn't crash LOGic, but it also doesn't give me the report.

So, in 15 minutes a of doing stuff other than just logging QSOs I get all these different types of errors. Frustrating is an understatement. It might be something else on my computer that causes the problem. But, I don't have the problem with other loggers and I don't want to spend a great deal of time troubleshooting my computer. I'd appreciate any help that can keep me from giving up.

73 de K1ESE
John

G'Day,

I think you need to spend the time on your PC and installation of Logic - unfortunately.

I changed nothing - PC is running all sorts of stuff - I cannot begin to list it all. I simply read your post and started work. I don't want to boast - just make the tests real. Here's whats is running ...



Exited Logic. Waited for Foxpro run time to exit. Started Logic. Telnet started as usual.

Closed Telnet. One cannot run a backup while this "external program" is running.

Ran backup - love that automatic naming for the backup - quick and easy.

Started Logic - Telnet running.

Problem 1 - Import LOTW, then use spot log.

Imported Lotw - 64 qsos direct from the LOTW on the Internet.
Went to spot log - no spots. Clicked on an old spot in Alerts - set rig - OK. Removed spot filter in spot log - clicked on spot - set rig - band, freq and mode,- OK. Double click the spot - EY8MM - sets rig - band, freq and mode , adds record to log, looks up QRZ, shows other qsos - 3 of them! I fill n RST rcvd and sent and store record - OK. Telnet still functioning - no crashes. WhileI did that - another spot was added to the spot log. I erase the record - no crashes.

Problem 2 - export ADIF records.

Export several dozen records - no crashes. All still functioning.

Problem 3 - run a report.

Ran report - AWARDS, Allbanddxcc,cw - leave the rest as default - printed to screen - preview - looks OK. Close preview, close dialogue. Everything still functioning.

I'm sorry to say - I think Logic may not be completely to blame here.

I would ...

The first step is to check whether the problem is in Logic or your PC. You need to get a nice clean copy of Logic running and test your "problems" before you add too much of your customizing back into Logic.

Run Logic backup - and make a backup of your Log and pictures to another place or disk. Then take a complete copy of the Logic directory to another place or disk. Later, you can re-install Logic, and copy this "complete copy" over the top of the installation, and you will be back to the current position - errors included. But for now ...

Uninstall Logic. Then delete the entire old Logic directory.

If errors occurred doing all that - ask for advice.

Install Logic. You don't say what version of Windows you are using. I am using Win7 64bit, and have disabled User Account Control, and I run as Administrator. My Logic is actually installed in "Program Files". But, if you are running Vista or Win7, install in c:\logic9. If you are unsure - ask for advice.

Redo your basic configuration - station information etc. Don't change anything else.

Update to Logic 9.0.53.

Reconfigure your radios, and import your Log from the backup.

At this point you should be able to repeat the "problems" you are having. Your log needs lots of extras - user fields etc etc etc - but that can wait.

Now configure Telnet, wait for some spots, and re-test.

Let us know how you go.

Peter VK4IU

Dennis -

I tried to connect to DXSummit, but the IP address I found didn't work.
I connect to K1TTT using Telenet 1.

I tried this -
start LOGic
don't start Telenet 1
export ADIF
all seems fine
connect to K1TTT using Telenet 1
double click on a spot
Logic crashes - With the Windows 7 message.

Windows 7, 64-bit
serial port for rig control is Eltima virtual port
there is no serial port for Telenet, just TCP/IP
virus checker is AVG Anti-Virus Free 2013.

I didn't bother to try the other errors. I don't have a lot of time for troubleshooting.

73 de K1ESE
John

G'Day John,

I know how you feel. I have some similar problems with Ham Radio Deluxe - one of the reasons I am running DXLab. I am currently seeking help on the HRD forum.

I have been in IT for over 40 years - starting on large mainframes and finally retiring from managing a network of over 45 servers and 4000 plus PCs. So called "mainframes" were much simpler - but a lot more powerful. I don't wonder that PCs have issues like we both are experiencing. I am amazed that, given the thousands of pieces, and the fingers of so many in the pie, that they work with so FEW errors. Standards are such wondefull things - so many to choose from! WinXP and Vista and Win7 are a joy to use - compared to Win98. But - back to the issue at hand.

I think your issues are not just with Logic. Logic just makes "it" happen. You need to troubleshoot your "system" of things for the problem, and you need to simplify the system to find the problem. If you are not prepared to backup your log and start again with Logic - there are not a lot of alternatives. You will chase your tail for a long time tring to find the "error in the system".

What is NaP3 ??

Over the years I have tried a lot of things - and spent more money than I care to mention. I own licenses for CT, CT for Windows, Wrtelog, Wintest, DX4Win, Ham Radio Deluxe, and Logic. I have tried almost every "free" package available - too many to list. The biggest disappointment was with DX4Win. Logger32 was too restricted in ability for me.

I actually now only use N1MM for contesting, and Logic for DXing and analysis. All the rest are just tools for specific things.

Only Logic does everything I need to do by way of logging my QSOs.

Logging QSOs is much more flexibile - in fact infinitely flexible with Logic. The ability to layout log forms and customise them for working, or QSLing, specific DX is unmatched by anything. The ability to define an infinite number of "user fields" to meet any specific need is unique. Others have only one or two user fields. I also like the extensive "real time" data when working DX - other QSOs, memberships, QRZ, DX Info etc.

Best of all is the reporting. You will not find anywhere else such extensive facilities for reporting and QSL printing. I buy blank A4 card stock, have it cut up at the local printers for "a beer or two", and print everything on the QSL card myself. No double handling with stickers here.

The extensive filtering lets me do a lot of analysis of my contests. Who did I work, in what direction, when, on what band.

I operate SO2R and use only N1MM for contesting because of the SO2R support. I import all the QSOs into Logic for analysis to improve my effort in contesting, and plot my DX progress - DXCC, WAZ etc etc - and print QSL cards and upload to eQSL, LoTW and Clublog. I don't actually chase any "wall paper".

I use DXLab for SpotCollector. I like the "database" it creates for the spots over time, rather than just a list of spots that arrived - and Commander does a better job of "setting the rig". I import my log into DXKeeper but do not log into it - it just provides the data for the rest of the DXLab system. I run DXCommander so I can run Digital Master 780 and BPSK31. HRD and DM-780 do not like my K3s for some reason. I use BandMaster because it interfaces into all the DX Bulletins and propagation data. I let DXMonitor run in the background accumulating data, so later I can ask for the history over time of the Dxpeditions - when were they on what mode, at what time, on what frequency - I don't actually use it while DXing. It all helps me plan around being a "house husband".

You just need to ask if you want more help.

Peter VK4IU

Ok, you shouldn't need an IP address for DX Summit. The default URL of
http://www.dxsummit.fi/D...px?count=25&range=1
works fine.

But, try disconnecting telnet then double-click on a spot. That will tell if it is really Telnet or not.

This Altima USB device -- look at it in the Windows device manager and see who did the driver. FTDI is good, Prolific is bad, anything else is questionable but probably OK.

Try totally disabling the rig interface and see if the problems go away.

The main problem now is that we don't know if the problem is being caused by Telnet, the radio interface, the spot log, or something else.

I would be happy to call you and log into your computer and take a look around.

Tnx & 73,

Dennis WN4AZY

Dennis -

I did more experimenting. I turned off rig control, exported ADIF, and turned on telenet 1. It crashed.

Eltima is a VIRTUAL port, no USB, no Prolific, no FTDI. But, since the problem is still there with the ports disconnected, it's not the Eltima virtual port, anyway.

I tried it with no rig control and no telenet. No problems with that particular issue. No crash after ADIF export.

I then found what you meant by DXSummit. We new users are not as up to speed on all your terms and need a little more guidance than just saying try DXSummit. I was trying to access DXSummit through telenet. Then I found out it is a completely different form.

I don't like DXSummit because it is not real time but appears to download information at intervals. Anyway, I ran DXSummit for ten minutes or so with no problems. I closed DXSummit and opened telenet 1 which ran for about 5 minutes and then the program crashed. The problem is telenet 1.

I use ADIF export to test, but the same thing happens with many other commands. The pop up says "LOGIC.exe has stopped working". It's a Windows 7 error message. Restarting LOGic requires CLEAN first.

This does nothing to address problem 3 above. For the time being I will put up with using DXSummit until you find a cure.

73 de K1ESE
John

Hi John, Bill, Dennis, and others reading along with us,

Having Dennis "dial in" sounds like a good idea.

I think you need to be looking around the "virtual system" you are running. You may like to describe it in more detail so we get a better idea of where the issues may lie.

That you describe "Win 7" errors stopping Logic is also a clue. The problem is most likely external to Logic.

While we are all "shooting in the dark" - so to speak - let me descibe my experience - I hope it helps.

Keep in mind "virtual ports" need to have some performance. What they do is "interrupt" the normal flow of control through the deep caverns of your Windows system. They run on your system as "windows services" - in the background. They do not turn-off just because you stop using the ports. One needs to "STOP" the service to get it out of the loop.

I assume that you are using LP-Bridge 2 and the Eltima drivers - as compared to the older LP-Bridge. The older LP-Bridge and it's virtual port drivers, and the Eltima virtual port drivers, do NOT mix.

NaP3 will be sucking the life from your PC when it is running.

From the comment by Bill W7OO - that Telnet is not involved in his similar problem - I am more convinced than ever that these issues have something to do with how the systems are configured - external to Logic. Logic is simply the "trigger".

I did not describe my system completely - but I too am using Eltima Serial Port software to create virtual ports.

One of the issues you faced I am sure, is that every bit of software wants to "run the rig", and you needed to use LP-Bridge, and the Eltima software, to give access to more than one peice of software.

You say you are running DXLab - which wants to control the rig - and Logic - which wants to control the rig - and NaP3 - that wants access to the rig. You stitched it all together with "virtual ports". If you are running the K3 at 38400, and there are multiple virtual ports at this speed, you may need to "slow down" the polling of the radios. See below.

Larry Phipps at TelepostInc solved the basic problem with LP-Bridge - ver 1 and ver 2.

From my experience getting the following to work - I would be looking seriously at the LP-Bridge/Eltima/virtual port system, and the all the software that uses them, for the problem.

I too wanted to do what you are doing. My system that I have described, runs "Eltima Serial Port Splitter". Two FTDI based USB ports come from RemoteRig devices (that's another story) into the PC. The Eltima "splitter_share_service" runs in the background and splits COM19 to COM1,9,10 and COM20 to COM2,11,12. It took me a while to get it all to work correctly.

N1MM or DXLab use ports 1 and 2, and OmniRig uses 9, and 11, and my "test tools" use ports 12, and 13 - all at the same time running at 38400 to the real K3s elsewhere at my QTH. OmniRig is used via COM by three or four peices of software - including Logic.

My system is pure Eltima - no other serial port software at all - just tools that use the ports. And as already described, I have no issues worth mentioning - now.

For obvious reasons all the ports have to run at the same speed - in my case 38400 - two real and six virtual ports. This proved too much even for my eight core Intel i7 - even with very little software running. I still run the ports at 38400, but, where I could, I had to slow down the polling of the radios to give the whole "system" a chance to function.

For me, the Eltima service simply stopped, and I had to restart it - constantly, randomly. Initially I elevated the "process priority" for the Eltima service to real-time, and slowed the radio polling to a very low level - and it all worked for many hours. Then, over a week, I slowly lowered the service priority back to normal, and increased the polling to where the system started to again crash. Then I backed the polling off a little and the system now runs without error for hours and hours - and I run anything and everything else as well.

One addage has stuck with me over my years with computers. It is ...

Systems that are backed into a corner - come of crashing.

Make sure your system has "room to breath", and time to "catch it's breath" - so to speak. As you see from my system, that has nothing to do with how many programs one runs. It is the nature of the work that each component is asked to do, and the environment in which they have to do it, that is of concern.

During my professional life I had many, many, long days and sleepless nights, with these sorts of problems.

I hope I have helped in some small way. I hope you and Dennis have some luck. Good luck with it. Just ask if you need help.

Peter VK4IU

Hi John,

Totally agree - one should not have to debug commercial software.

But when does one get to work with "one" commercial bit of software?

We are dealing with "systems of stuff" - rarely does one work with anything in isolation. If software writers knew about every PC enviroment in which their software had to work, the PC world would be a better place. But ... that's utopia and is never going to happen.

Now I am curious - in your previous post you said ...



... why the "virtual ports"?

For me - 64bit, virtual ports, Win7 error messages, are pointing at your "system of stuff" - not one commercial software item in it.

After your answer to my "virtual ports" question, I will leave things to yourself and Dennis. Without detailed knowledge of your system, I have little more to add, beyond experience getting my own "system of stuff" to function - which I have already outlined.

Peter VK4IU