FYI - Another trunker/etrunker Windows port

[brandon]

Here is the error I get after a while monitoring EDACS

Program decodes fine for a while and eventually just closes without any warning - usually within 10-20 minutes. When I run from a command window here is what shows up after the program terminates.

The memory could not be written.
Exception fielded by 0x00422ae0
EAX=0x003e6598 EBX=0x003e6598 ECX=0x00000004 EDX=0x00000000
ESI=0x0043ea6c EDI=0x00004232 EBP=0x0006fd98 ESP=0x0006fd68
EIP=0x0040a0cd EFL=0x00010202 CS =0x0000001b SS =0x00000023
DS =0x00000023 ES =0x00000023 FS =0x0000003b GS =0x00000000
Stack dump (SS:ESP)
0x00004000 0x77d48d5f 0x0006fd94 0x00004232 0x0043ea6c 0x004298c4
0x00416c49 0x003e0649 0x003ee3bc 0x003e6598 0x003e6598 0x0006fd49
0x0006fdd8 0x00004232 0x0043ea6c 0x004175df 0x00000000 0x00007030
0x003e6598 0x003e6598 0x0041dc30 0x003e06e0 0x003ee3bc 0x003e6598
0x003e6598 0x00004000 0x00000002 0x00004000 0x000084c9 0x00004232
0x0043ea6c 0x004047b6 0x00000000 0x00000000 0x00000000 0x00004232
0x01c6001c 0x00000000 0x0000ffff 0x00000000 0x00405067 0x3f2b6014
0xc1097adb 0xadad8e4d 0x405f0bdc 0xadad8e4d 0x404f0bdc 0xfcf63aed
0xc1097ccb 0x69681197 0xc10969b6 0x00000000 0x40c2c000 0x00000000
0x40c2c000 0x0000026d 0x00000000 0x00060000 0x00008d31 0x0040b601
0x0006fe80 0x3a92492e 0x01c6927a 0x00000000 0x0006fea4 0x00000108
0x0040e06c 0x00000001 0x003e00bc 0x0006fea4 0x0006fe98 0x3a92492e

This has not happened to me when monitoring a Motorola system.

 

[EricCottrell]

Here is the error I get after a while monitoring EDACS

Program decodes fine for a while and eventually just closes without any warning - usually within 10-20 minutes. When I run from a command window here is what shows up after the program terminates.

The memory could not be written.
Exception fielded by 0x00422ae0
<snip>

This has not happened to me when monitoring a Motorola system.

Hello,

I have not seen these problems when I monitor EDACS here. I need some more info to track this down.
What version were you running, a1 or a2?
What is the voice radio connected to the serial port and what is the comport number?

73 Eric

 

[EricCottrell]

Hello,

I may have found a problem. It looks like a bug that was in the DOS version but did not cause a problem under DOS.

For people having the EDACS problem try the version attached and see if it works. Version number is the same as A2. If you need narrowband do a xcopy ewtrnk.exe ewtrnk48.exe.

73 Eric

 

[brandon]

Hi Eric,
It was happening on both versions. I will try the one you just attached and report back on the result.

 

[SCPD]

I may have found a problem. It looks like a bug that was in the DOS version but did not cause a problem under DOS.

Eric - there are several boundary condition problems in the old code that won't fly in a protected mode environment. Watch out for negative array indices as an example.

-rick

 

[SCPD]

I still havent been able to get mine to work ..... it just sits there.

It starts up ... and does nothing. (no errors ... just nothing happens)

I am using XP Professional, environment variable as in the DOS version points to a etrunk.txt file where i jsut have the one item in. The program will start .. doesnt do any importing and just says 'want win' i think on the latest version.

Anyone have any suggestions ?

 

[SCPD]

Sorry if I'm sounding like a recording but ...

Run an oscilloscope program to get a view of the actual signal. You may need to adjust the signal's level - it could be too high, too low or too distorted. You may need to compare microphone vs. line input. Sometimes that makes a difference.

-rick

 

[DaveNF2G]

I've been scrolling through the thread and I've seen mention of this problem before, but the solution is not clear.

1) wtrunker.exe - displays "WantWIn" and does not decode.

2) ewtrnk.exe - displays "WantWIn" and does not decode.

Operating system is Windows XP Pro SP-2.

 

[fmon]

I've been scrolling through the thread and I've seen mention of this problem before, but the solution is not clear.

1) wtrunker.exe - displays "WantWIn" and does not decode.

2) ewtrnk.exe - displays "WantWIn" and does not decode.

Operating system is Windows XP Pro SP-2.

I too have the same OS and the same problem with both exe's.

However, when wtrunk first came out, it fired up and worked several times.

 

[brandon]

Hi,
I tried that modified version and it still tanks after about 5 minutes. Let me know if there is anything you want me to try.

 

[SCPD]

I have attached 2 screen shots of what I am getting from my R7000 (right) and BC780XLT (left) ..

Maybe Rick you can let us know what they look like from your perspective ? They both give me 100% on Etrunker (DOS Version)

 

[SCPD]

Maybe Rick you can let us know what they look like from your perspective ?

Kevin;
I've got bad news and good news. The bad news is (from my perspective) those signals look awful. I see you've selected a sample rate of 11,025. For a 9600 baud signal that is only 1.14 samples per symbol. A higher ratio of samples per symbol is needed. Here's the good news: try a higher sample rate (looks like 44,100 samples per second from the screen shot). That should give us a better picture of your signal.
-rick

 

[pro92b]

To Eric, you probably are well aware of what you are up against with the LTR decoding portion of the program. I've documented it in the file below for convenience.

 

[SCPD]

Here's the truly goofy thing about the above. The waveform shown is either (a) after voice frequencies have been filtered out or (b) while no voice was present (silence).

If you add voice, the low frequency portion passes straight through. You'll get better results while someone is talking than with silence.

-rick

 

[slicerwizard]

Here's the truly goofy thing about the above. The waveform shown is either (a) after voice frequencies have been filtered out or (b) while no voice was present (silence).

He did say it was an idle burst.

If you add voice, the low frequency portion passes straight through. You'll get better results while someone is talking than with silence.
-rick

Not surprising. Sorta like how PIN diodes pass RF better when fed a DC supply. Sorta.

If the sound card can't handle pure low speed data, mix a 1 kHz tone with the discriminator audio.

 

[mws72]

I tried running the ewtrnk384a2 (second version) last night. It ran for a over two and half hours on a site with 7 LCNs. Another site has 5 LCNS and it ran ok. Both sites are moderate to low traffic levels. Then I tried it on a site with 10 LCN with higher traffic levels. All these are part of a regional system in Iowa. It will not run more than a couple of minutes at most while at this site. Sometimes I get the microsoft box about have to close this app. But usually it goes away.

 

[EricCottrell]

Hello,

I ran ewtrnk with a recording of the San Antonio, Texas EDACS and not crashes. The recording was short (1 minute) but it was during an active time. So I eliminated the radio code, normal affiliation, and group calls. I suspect the problem only occurs when something special occurs like a status message. If you monitor a system that causes the crash and can record a 44.1K sample rate wave file, I would appeciate a zipped wave file of the system. Five to ten minutes should be fine. Even better if you can record a file and when you play it back into ewtrnk it causes a crash. Send the zip files to eac&AT&shore.net as the attachment size here is limited. Replace the &AT& with the at sign.

Unfortunely Motorola has a lock on the area and EDACS is few and far between. The local MBTA EDACS is not busy enough and uses the new SitePro over-the-air protocol.

73 Eric

 

[EricCottrell]

Hello,

Thanks to a email with a crash dump and a recording of the edacs control channel I understand the crash problem. I may need some edacs protocol help.

The crash occurs when the program is processing a 0xF418000 0xF418000 set of frames. This decodes as an icall (radio to radio call) on LCN 3 from radio id 0 to radio id 0. Since it is unusual for a radio to call itself this code must mean something special.

In my reading of various EDACS information, I remember a system tester feature that checks the various repeaters. This tester has a radio id of zero. So I assume the icall crashing the program is the tester testing the LCN 3 repeater.

This may explain why the crashes occur within 5 minutes or so or never happen depending on the site having this feature.

73 Eric

 

[EricCottrell]

Hello,

I posted the a3 version over on the Yahoo Trunker group. This version fixes the EDACS crash problem.

73 Eric

 

[mws72]

The newest version ran great last night. No making like a genie and disappearing. The only problem is the laptop is getting too hot! I gave the table a bit of brown mark by the exhaust of the laptop. The cpu monitor says it was running 100% and the fan was running in spurts. Oh well I'll just use it for quick looks.