Re: DStarRepeater QnetGateway
I am wondering if this means anything.
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: Reading file /usr/local/etc/qn.cfg
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: module_b = 'mmdvmhost'
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: gateway_tomodemb = 'tomodemb'
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: module_b_internal_ip = '10.0.2.126'
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: module_b_local_port = 20011
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: module_b_gateway_port = 20010
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: log_qso = false
Apr 10 19:00:55 dstarrepeater qnrelay[372044]: Waiting for tomodemb server to start...? It never says connected. Is this where the issue is?
Apr 10 19:00:56 dstarrepeater qnrelay[372044]: msock=3, gateway=4
N8MFN Hamilton Wireless Radio Club
I have been watching qnetgateway while connected to ref030 C
Apr 10 21:34:28 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id 7903
Apr 10 21:55:10 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id 9a16
Apr 10 22:18:30 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id e721
Apr 10 22:26:29 dstarrepeater qngateway[372108]: Got a valid slow data header but module -33 doesn't exist
Apr 10 22:26:31 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id f64a
Apr 10 22:37:02 dstarrepeater qngateway[372108]: Got a valid slow data header but module 2 doesn't exist
Apr 10 23:23:32 dstarrepeater qngateway[372108]: Got a valid slow data header but module -33 doesn't exist
Apr 10 23:25:23 dstarrepeater qngateway[372108]: Got a slow data header: KR4AIK GKR4AIK BCQCQCQ ?KQ4KK ? KENT
Apr 10 23:25:23 dstarrepeater qngateway[372108]: Got a slow data header: KR4AIK GKR4AIK BCQCQCQ ?KQ4KK ? KENT
Apr 10 23:25:24 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id f679
N8MFN Hamilton Wireless Radio Club
Everything is still in the correct spot. I just pointed to the source to see if maybe that was the problem. No echo doesn't come through the repeater.
Here is what I get for echo. Apr 09 21:30:16 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:30:20 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:30:23 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:30:27 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:35:36 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:35:37 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:35:39 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:35:47 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:35:49 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:35:52 dstarrepeater qngateway[129386]: Finished playing It all looks like it is working. Just missing something coming back.
Very basic.
ircddb_login='N8MFN'
module_b=mmdvmhost
module_b_callsign='N8MFN'
module_b_internal_ip='10.0.2.126'
gateway_send_qrgs_maps=true
gateway_local_irc_ip='10.0.2.169'
file_dtmf='/root/QnetGateway'
file_announce_dir='/root/QnetGateway/announce'
dash_show_order='MO,LH,SY,UR,IP,PS'
I will place the announce directory back to normal. I was also trying to figure out how to make my own .dat files on the fly.
N8MFN Hamilton Wireless Radio Club
On Fri, Apr 9, 2021 at 7:40 AM Tom Early < n7tae@...> wrote: Does Echo work? It might also be helpful to post your qn.cfg file. You've moved stuff from the standard locations to /root/QnetGateway. How come?
|
Re: DStarRepeater QnetGateway
I have been watching qnetgateway while connected to ref030 C
Apr 10 21:34:28 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id 7903
Apr 10 21:55:10 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id 9a16
Apr 10 22:18:30 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id e721
Apr 10 22:26:29 dstarrepeater qngateway[372108]: Got a valid slow data header but module -33 doesn't exist
Apr 10 22:26:31 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id f64a
Apr 10 22:37:02 dstarrepeater qngateway[372108]: Got a valid slow data header but module 2 doesn't exist
Apr 10 23:23:32 dstarrepeater qngateway[372108]: Got a valid slow data header but module -33 doesn't exist
Apr 10 23:25:23 dstarrepeater qngateway[372108]: Got a slow data header: KR4AIK GKR4AIK BCQCQCQ ?KQ4KK ? KENT
Apr 10 23:25:23 dstarrepeater qngateway[372108]: Got a slow data header: KR4AIK GKR4AIK BCQCQCQ ?KQ4KK ? KENT
Apr 10 23:25:24 dstarrepeater qngateway[372108]: Inactivity to local rptr module B, removing stream id f679
N8MFN Hamilton Wireless Radio Club
Everything is still in the correct spot. I just pointed to the source to see if maybe that was the problem. No echo doesn't come through the repeater.
Here is what I get for echo. Apr 09 21:30:16 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:30:20 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:30:23 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:30:27 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:35:36 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:35:37 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:35:39 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:35:47 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:35:49 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:35:52 dstarrepeater qngateway[129386]: Finished playing It all looks like it is working. Just missing something coming back.
Very basic.
ircddb_login='N8MFN'
module_b=mmdvmhost
module_b_callsign='N8MFN'
module_b_internal_ip='10.0.2.126'
gateway_send_qrgs_maps=true
gateway_local_irc_ip='10.0.2.169'
file_dtmf='/root/QnetGateway'
file_announce_dir='/root/QnetGateway/announce'
dash_show_order='MO,LH,SY,UR,IP,PS'
I will place the announce directory back to normal. I was also trying to figure out how to make my own .dat files on the fly.
N8MFN Hamilton Wireless Radio Club
On Fri, Apr 9, 2021 at 7:40 AM Tom Early < n7tae@...> wrote: Does Echo work? It might also be helpful to post your qn.cfg file. You've moved stuff from the standard locations to /root/QnetGateway. How come?
|
Re: DStarRepeater QnetGateway
Everything is still in the correct spot. I just pointed to the source to see if maybe that was the problem. No echo doesn't come through the repeater.
Here is what I get for echo. Apr 09 21:30:16 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:30:20 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:30:23 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:30:27 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:35:36 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:35:37 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:35:39 dstarrepeater qngateway[129386]: Finished playing
Apr 09 21:35:47 dstarrepeater qngateway[129386]: Recording mod B for echotest into file:[/var/local/B_echotest.dat]
Apr 09 21:35:49 dstarrepeater qngateway[129386]: File to playback:[/var/local/B_echotest.dat]
Apr 09 21:35:52 dstarrepeater qngateway[129386]: Finished playing It all looks like it is working. Just missing something coming back.
Very basic.
ircddb_login='N8MFN'
module_b=mmdvmhost
module_b_callsign='N8MFN'
module_b_internal_ip='10.0.2.126'
gateway_send_qrgs_maps=true
gateway_local_irc_ip='10.0.2.169'
file_dtmf='/root/QnetGateway'
file_announce_dir='/root/QnetGateway/announce'
dash_show_order='MO,LH,SY,UR,IP,PS'
I will place the announce directory back to normal. I was also trying to figure out how to make my own .dat files on the fly.
N8MFN Hamilton Wireless Radio Club
On Fri, Apr 9, 2021 at 7:40 AM Tom Early < n7tae@...> wrote: Does Echo work? It might also be helpful to post your qn.cfg file. You've moved stuff from the standard locations to /root/QnetGateway. How come?
|
Re: DStarRepeater QnetGateway
Does Echo work? It might also be helpful to post your qn.cfg file. You've moved stuff from the standard locations to /root/QnetGateway. How come?
|
Re: DStarRepeater QnetGateway
Apr 08 23:04:51 dstarrepeater qnlink[129407]: sending File:[/root/QnetGateway/announce/connected2network.dat], mod:[B], RADIO_ID=[WELCOME TO QUADNET? ]
Apr 08 23:05:27 dstarrepeater qnlink[129407]: sending File:[/root/QnetGateway/announce/already_unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Apr 08 23:05:32 dstarrepeater qnlink[129407]: sending File:[/root/QnetGateway/announce/already_unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Apr 08 23:06:32 dstarrepeater qnlink[129407]: sending File:[/root/QnetGateway/announce/already_unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Apr 08 23:06:43 dstarrepeater qnlink[129407]: sending File:[/root/QnetGateway/announce/already_unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Apr 08 23:06:53 dstarrepeater qnlink[129407]: sending File:[/root/QnetGateway/announce/id.dat], mod:[B], RADIO_ID=[N8MFN??? NOT LINKED ]
None of this transmitted to the repeater. It is RXing now with out error. That is Awesome! but I can not get anything in return. I even connected to 30 C and got nothing from it.
|
Re: DStarRepeater QnetGateway
Apr 08 22:17:33 dstarrepeater qnlink[124504]: #Gateways: /usr/local/etc/gwys.txt=7001
Apr 08 22:17:33 dstarrepeater qnlink[124504]: read 62 indicies from /usr/local/etc/index.dat
Apr 08 22:17:33 dstarrepeater qnlink[124504]: QnetLink QnetLink-606 initialized...entering processing loop
Apr 08 22:17:33 dstarrepeater qnlink[124504]: xrf4=4, dcs4=5, ref4=6, gateway=7
Apr 08 22:17:52 dstarrepeater qnlink[124504]: sending ACK+text, mod:[B], RADIO_ID=[NOT LINKED????????? ]
Apr 08 22:17:55 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/connected2network.dat], mod:[B], RADIO_ID=[WELCOME TO QUADNET? ]
Apr 08 22:17:59 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/id.dat], mod:[B], RADIO_ID=[N8MFN??? NOT LINKED ]
Apr 08 22:18:16 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/id.dat], mod:[B], RADIO_ID=[N8MFN??? NOT LINKED ]
Apr 08 22:19:18 dstarrepeater qnlink[124504]: sending link command from mod B to: [REF030? ] mod C [18.221.55.237]:20001
Apr 08 22:19:20 dstarrepeater qnlink[124504]: sending ACK+text, mod:[B], RADIO_ID=[TRYING??? REF030? C ]
Apr 08 22:20:09 dstarrepeater qnlink[124504]: Unlinked from [REF030? ] mod C, TIMEOUT...
Apr 08 22:20:09 dstarrepeater qnlink[124504]: sending link command from mod B to: [REF030? ] mod C [18.221.55.237]:20001
Apr 08 22:20:10 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/unlinked.dat], mod:[B], RADIO_ID=[LINK TIMEOUT??????? ]
Apr 08 22:20:11 dstarrepeater qnlink[124504]: Unlinked from [REF030? ] mod C
Apr 08 22:20:12 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Apr 08 22:20:36 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/already_unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Apr 08 22:20:44 dstarrepeater qnlink[124504]: sending link request from mod B to link with: [XLX180? ] mod C [192.241.240.7]:30001
Apr 08 22:20:44 dstarrepeater qnlink[124504]: Connected from: XLX180?? C [192.241.240.7]:30001
Apr 08 22:20:46 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/linked.dat], mod:[B], RADIO_ID=[LINKED XLX180 C???? ]
Apr 08 22:22:57 dstarrepeater qnlink[124504]: sending ACK+text, mod:[B], RADIO_ID=[LINKED TO XLX180? C ]
Apr 08 22:24:13 dstarrepeater qnlink[124504]: Unlinked from [XLX180? ] mod C
Apr 08 22:24:15 dstarrepeater qnlink[124504]: sending File:[/usr/local/etc/unlinked.dat], mod:[B], RADIO_ID=[UNLINKED??????????? ]
Yes, That is working But I am wondering why I am not getting the voice responses from Qnet?
|
Re: DStarRepeater QnetGateway
Hi Ryan, I think I might know what's going on.
Could you please try the "rc" branch:
sudo make uninstallbase && sudo make uninstallrelay
make clean
git checkout rc
git pull
make base && make relay
sudo make installbase && sudo make installrelay
|
Re: DStarRepeater QnetGateway
So I am sending I command. I am getting this:
Apr 08 02:37:12 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24
Apr 08 02:37:13 dstarrepeater qnrelay[5157]: Read error on 'tomodemb': Connection reset by peer
Apr 08 02:37:13 dstarrepeater qnrelay[5157]: Restarting 'tomodemb'...
Apr 08 02:37:13 dstarrepeater qnrelay[5157]: Waiting for tomodemb server to start...
Apr 08 02:37:13 dstarrepeater qnrelay[5157]: DEBUG: Run: read zero bytes from 0
Apr 08 02:37:29 dstarrepeater qnrelay[5157]: Read error on 'tomodemb': Connection reset by peer
Apr 08 02:37:29 dstarrepeater qnrelay[5157]: Restarting 'tomodemb'...
Apr 08 02:37:29 dstarrepeater qnrelay[5157]: Waiting for tomodemb server to start...
Apr 08 02:37:29 dstarrepeater qnrelay[5157]: DEBUG: Run: read zero bytes from 0
Apr 08 02:37:29 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24
Apr 08 02:37:39 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24
Apr 08 02:37:45 dstarrepeater qnrelay[5157]: Read error on 'tomodemb': Connection reset by peer
Apr 08 02:37:45 dstarrepeater qnrelay[5157]: Restarting 'tomodemb'...
Apr 08 02:37:45 dstarrepeater qnrelay[5157]: Waiting for tomodemb server to start...
Apr 08 02:37:45 dstarrepeater qnrelay[5157]: DEBUG: Run: read zero bytes from 0
Apr 08 02:37:45 dstarrepeater qnrelay[5157]: DEBUG: ProcessMMDVM: unusual packet len=24
I am taking it there is a configuration issue?
|
Re: DStarRepeater QnetGateway
So, I am coming to the conclusion that there is something different from MMDVM and DStarrepeater. It will take my commands. But no matter what I do. I can not get rid of this.
Apr 08 02:12:55 dstarrepeater qnrelay[1119]: DEBUG: ProcessMMDVM: unusual packet len=24
Apr 08 02:13:06 dstarrepeater qnrelay[1119]: DEBUG: ProcessMMDVM: unusual packet len=24
Apr 08 02:13:15 dstarrepeater qnrelay[1119]: DEBUG: ProcessMMDVM: unusual packet len=24
Also I get this every key up in gateway log file:
Apr 08 02:24:58 dstarrepeater qngateway[1900]: Inactivity from local rptr module B, removing stream id a1e1
Apr 08 02:25:19 dstarrepeater qngateway[1900]: Inactivity from local rptr module B, removing stream id a6b6
It will not transmit. I will keep trying. But I think I have hit the road block. I can halt the system reboot the system via the HX and RX commands.
Thanks for your efforts
|
Well, I found version 1.05 and ran that, now the serial number is back and it runs fine with qnet, so the 1.07 messes up the s#. I upgraded as it randomly crashed with pistar, and 1.07 seemed to fix that. Will see how it behaves with qnet. Question for Tom, is it possible to run the mmdvm modem on vhf and uhf concurrently if there is a duplex hat installed?
Horst, vk2hl
toggle quoted message
Show quoted text
On 26 Mar 2021, at 19:40, Robbert J. van Herksen <rescueteam@...> wrote:
? The fact that you see a garbled SN# string means that your DVAP has been updated to FW 1.07
Did you ever upgraded it yourself? Maybe you bought it second hand and the original owner updated it ?XS Max (512Gb) On 26 Mar 2021, at 05:52, horst.vk2hl@... wrote:
?Hi Robert,
That link does not seem to work. When I run updater, it displays the serial number as AP.... and then some non ascii characters.
Would appeciate if you could test that link, it ceratinly does not work here.
|
The fact that you see a garbled SN# string means that your DVAP has been updated to FW 1.07
Did you ever upgraded it yourself? Maybe you bought it second hand and the original owner updated it ?XS Max (512Gb)
toggle quoted message
Show quoted text
On 26 Mar 2021, at 05:52, horst.vk2hl@... wrote:
?Hi Robert,
That link does not seem to work. When I run updater, it displays the serial number as AP.... and then some non ascii characters.
Would appeciate if you could test that link, it ceratinly does not work here.
|
Hi there.
Actually, before doing that update with that program, I could read the SN# of the the dongle.
After the update, the SN# was all garbled. I think the update obviously shifted the location of the version string, picks up the SN from the wrong location.
I will check with the designer of the dongle, Guus / PE1PLM
73 de Robbert / PA3BKL (aka TA2IX)
toggle quoted message
Show quoted text
On 26 Mar 2021, at 05:52, horst.vk2hl@... wrote:
?Hi Robert,
That link does not seem to work. When I run updater, it displays the serial number as AP.... and then some non ascii characters.
Would appeciate if you could test that link, it ceratinly does not work here.
|
Hi Robert,
That link does not seem to work. When I run updater, it displays the serial number as AP.... and then some non ascii characters.
Would appeciate if you could test that link, it ceratinly does not work here.
|
It's me again, Robbert / PA3BKL, replying to my own post.
?
After THINKING that I had bricked my red DVAP during a FW update, I left the unit disconnected for about 10 mins.
I just tried to flash it again, and? YESSS: I managed to update the AppRev from v1.05 to v1.07, and BootRev was v1.03 and was not changed.
?
My red DVAP works like a charm again.
?
Feels good!!
?
73 de Robbert / PA3BKL
|
Here is a solution:
Download this program from here:
Run the program, and click the "Read DVAP Info" button
BUT DO NOT PRESS UPDATE BUTTON!!! ever (unless you want to destroy your DVAP (like I did.... bummer)
Let me know it you were able to find the SN# and FW version
Best
Robbert / PA3BKL (aka TA2IX)
|
Hi Tom,
You hit the nail on the head... the serial number in the DVAP is corrupted, that is why DVtools doesn't want to talk to it either. Luckily pistar doesn't worry about it. I guess I could try and downgrade to 1.6, but really don't want to risk bricking it altogether.
Thanks for your help Horst
On Wed, Mar 24, 2021 at 12:09 AM Tom Early < n7tae@...> wrote: Hi Horst,
Please don't give up, at least just yet. Colby and I would like to get to the bottom of this...
I fired up my DVAP and it is on FW version 1.7 as well.
The very next message you should see after the "... now locked for exclusive use" should be something very similar to either:
"Using /dev/ttyUSB0:? AP123456, because serial number matches your configuration file"
or
"Device /dev/ttyUSB0 has serial AP123456, but does not match your configuration value AP654321"
In other words, it should print a confirmation that you have the correct serial number, or an error message that you don't have the correct serial number, and then
The fact that your log says "[108B blob data]" means that there is a non-printable (non-ascii) character somewhere in that 108 bytes. The problem is, is that neither one of these log messages is even close to 108 bytes, so something is very strange.
It would be very useful to see you qn.cfg file. It would also be useful for you to configure "AP123456" in your config file and see what happens.
Also after reviewing the code I now remember why a serial number is required while dstarrepeater doesn't require a serial number. For dstarrepeater, you have to specify the /dev/ttyUSBX device address, and for qndvap, it doesn't require a /dev address. Rather it starts at /dev/ttyUSB0 and keeps trying until it finds your DVAP by incrementing the number. This was built so you could have something else on /dev/ttyUSB0 (or 2 or 3 or ?) and qndvap should still be able to find it without you having to figure out which /dev/ttyUSBX it was installed on by your OS.
|
Hi Horst,
Please don't give up, at least just yet. Colby and I would like to get to the bottom of this...
I fired up my DVAP and it is on FW version 1.7 as well.
The very next message you should see after the "... now locked for exclusive use" should be something very similar to either:
"Using /dev/ttyUSB0:? AP123456, because serial number matches your configuration file"
or
"Device /dev/ttyUSB0 has serial AP123456, but does not match your configuration value AP654321"
In other words, it should print a confirmation that you have the correct serial number, or an error message that you don't have the correct serial number, and then
The fact that your log says "[108B blob data]" means that there is a non-printable (non-ascii) character somewhere in that 108 bytes. The problem is, is that neither one of these log messages is even close to 108 bytes, so something is very strange.
It would be very useful to see you qn.cfg file. It would also be useful for you to configure "AP123456" in your config file and see what happens.
Also after reviewing the code I now remember why a serial number is required while dstarrepeater doesn't require a serial number. For dstarrepeater, you have to specify the /dev/ttyUSBX device address, and for qndvap, it doesn't require a /dev address. Rather it starts at /dev/ttyUSB0 and keeps trying until it finds your DVAP by incrementing the number. This was built so you could have something else on /dev/ttyUSB0 (or 2 or 3 or ?) and qndvap should still be able to find it without you having to figure out which /dev/ttyUSBX it was installed on by your OS.
|
The "[108B blob data]" is probably the error message we want, but
it looks like qndvap is reading some binary data instead of an
ascii string when trying to read the serial number.
It might be useful to put in AP123456 and see if qndvap reports
the actual serial number.
Yes, did all that. 
?Here is the log.. doesn't really show any causes.
On Tue, Mar 23, 2021 at 2:24
PM Colby Ross W1BSB < colbypr@...> wrote:
Horst
?
You re-ran qnconfig and set the
serial number, yes?? It should be in the format Tom
indicated, AP123456. I believe its case sensitive as
well. If you¡¯ve done that, run an uninstall, and
install, and it should restart the programs. If qndvap
still isn¡¯t running after that, at the command prompt do
a sudo journalctl -u qndvap -f and send us what it shows
you.
?
Colby
?
?
?
Found the serial number, it is
actually printed on the casing and it was obscured by
a bit of velcro... duh...however, it still does not
work. It just says the module is not running and when
I try to manually start it in the maintenance menu,
two leds flash briefly and then it goes back to the
slow pulsing one. The firmware in my dvap is 1.7. I
updated that because it kept crashing with pistar and
that fixed it. However, it also no longer works with
the original dvap tool. I can¡¯t see an option to look
at the log because it hasn¡¯t started.
?
On Mon, 22 Mar 2021 at 23:47,
Tom Early <n7tae@...>
wrote:
The serial number for my old
red 2M DVAP is on a white sticker on the
bottom-side of the PCB next to the USB socket,
visible through the translucent case. In any event
if you can't find your serial number, put in
"AP123456" in you qn.cfg file and then boot up
your system. Then look in the qndvap log file. It
will report the actual serial number found when it
tries to lock the device. Then you can set the
correct number in your config file.
I'm not quite sure why Scott KI4LKF originally put
this serial number check in the code, but I am
reluctant to remove the check. It has some
usefulness if you were wanted to set up a 70cm/2m
dualband hotspot based on two DVAPs.
--
___________________________
73
n7tae (at) tearly (dot) net
|
Before you give up, please show me the contents of your qn.cfg file. If you type cat qn.cfg you can then copy and paste it here.? If it works in pi-star, it should work with QNetGateway as well, which leads me to believe it¡¯s a minor configuration error somewhere. ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of horst.vk2hl@... Sent: Tuesday, March 23, 2021 00:25 To: [email protected]Subject: Re: [QnetGateway] DVAP ? Hi Colby, Did that, but it basically showed the same thing, no extra info that I can see. When I restart the module, the blue and red led flash for a second or so, and then it stops. It looks like it is attempting to start. The log shows no more than what I can see, just says it doesn't?work or something to that effect.???. I did turn on the extra logging in qnconfig, but it seems to have made no difference in what it shows. I might give up and plug it into my pi-star again. It does work there. ? On Tue, Mar 23, 2021 at 2:54 PM Colby Ross W1BSB <colbypr@...> wrote: Please do the following: ? sudo grep qndvap /var/log/syslog ? It¡¯ll be big, but it¡¯ll show more. Try to capture a couple of iterations of the program starting and stopping. ? Colby ? ? ? Yes, did all that.
?Here is the log.. doesn't really show any causes. ? On Tue, Mar 23, 2021 at 2:24 PM Colby Ross W1BSB <colbypr@...> wrote: Horst ? You re-ran qnconfig and set the serial number, yes?? It should be in the format Tom indicated, AP123456. I believe its case sensitive as well. If you¡¯ve done that, run an uninstall, and install, and it should restart the programs. If qndvap still isn¡¯t running after that, at the command prompt do a sudo journalctl -u qndvap -f and send us what it shows you. ? Colby ? ? ? Found the serial number, it is actually printed on the casing and it was obscured by a bit of velcro... duh...however, it still does not work. It just says the module is not running and when I try to manually start it in the maintenance menu, two leds flash briefly and then it goes back to the slow pulsing one. The firmware in my dvap is 1.7. I updated that because it kept crashing with pistar and that fixed it. However, it also no longer works with the original dvap tool. I can¡¯t see an option to look at the log because it hasn¡¯t started. ? On Mon, 22 Mar 2021 at 23:47, Tom Early <n7tae@...> wrote: The serial number for my old red 2M DVAP is on a white sticker on the bottom-side of the PCB next to the USB socket, visible through the translucent case. In any event if you can't find your serial number, put in "AP123456" in you qn.cfg file and then boot up your system. Then look in the qndvap log file. It will report the actual serial number found when it tries to lock the device. Then you can set the correct number in your config file.
I'm not quite sure why Scott KI4LKF originally put this serial number check in the code, but I am reluctant to remove the check. It has some usefulness if you were wanted to set up a 70cm/2m dualband hotspot based on two DVAPs.
|
Hi Colby,
Did that, but it basically showed the same thing, no extra info that I can see. When I restart the module, the blue and red led flash for a second or so, and then it stops. It looks like it is attempting to start. The log shows no more than what I can see, just says it doesn't?work or something to that effect.???. I did turn on the extra logging in qnconfig, but it seems to have made no difference in what it shows. I might give up and plug it into my pi-star again. It does work there. Thanks for your help! Horst
On Tue, Mar 23, 2021 at 2:54 PM Colby Ross W1BSB < colbypr@...> wrote: Please do the following: ? sudo grep qndvap /var/log/syslog ? It¡¯ll be big, but it¡¯ll show more. Try to capture a couple of iterations of the program starting and stopping. ? Colby ? ? ? Yes, did all that.
?Here is the log.. doesn't really show any causes. ? On Tue, Mar 23, 2021 at 2:24 PM Colby Ross W1BSB <colbypr@...> wrote: Horst ? You re-ran qnconfig and set the serial number, yes?? It should be in the format Tom indicated, AP123456. I believe its case sensitive as well. If you¡¯ve done that, run an uninstall, and install, and it should restart the programs. If qndvap still isn¡¯t running after that, at the command prompt do a sudo journalctl -u qndvap -f and send us what it shows you. ? Colby ? ? ? Found the serial number, it is actually printed on the casing and it was obscured by a bit of velcro... duh...however, it still does not work. It just says the module is not running and when I try to manually start it in the maintenance menu, two leds flash briefly and then it goes back to the slow pulsing one. The firmware in my dvap is 1.7. I updated that because it kept crashing with pistar and that fixed it. However, it also no longer works with the original dvap tool. I can¡¯t see an option to look at the log because it hasn¡¯t started. ? On Mon, 22 Mar 2021 at 23:47, Tom Early <n7tae@...> wrote: The serial number for my old red 2M DVAP is on a white sticker on the bottom-side of the PCB next to the USB socket, visible through the translucent case. In any event if you can't find your serial number, put in "AP123456" in you qn.cfg file and then boot up your system. Then look in the qndvap log file. It will report the actual serial number found when it tries to lock the device. Then you can set the correct number in your config file.
I'm not quite sure why Scott KI4LKF originally put this serial number check in the code, but I am reluctant to remove the check. It has some usefulness if you were wanted to set up a 70cm/2m dualband hotspot based on two DVAPs.
|
Tom Early