d51r3verse

Results 11 comments of d51r3verse

100Hz traces more linear/quieter than 1kHz( bandwidth seems to work I think 😁 ) But, unexpected readings found `bandwidth`ed calibration&sweeps. Here is my experience( both ends terminated LOAD ) Cal:1kHz...

uClib build workaround of m4(freadahead) https://askubuntu.com/a/1099394 ``` perl -p -i -e 's/if defined _IO_ftrylockfile /if defined _IO_EOF_SEEN /g' ./build_dir/host/m4-1.4.17/lib/*.c ``` then, add follings to ```.build_dir/host/m4-1.4.17/lib/stdio-impl.h``` ``` #if !defined _IO_IN_BACKUP &&...

This is for musl build patches -reserved-

Reproduced with duplex hotspot DMR#1: BrandMeister TG91 -> RF:TS1 DMR#2: IPSC2 bMaster+'s TG91 -> RF:TS2 *TS1 shows with name on DMRIds.dat well, but TS2 randomly callsign only shows. *This happens...

![S__204087302](https://user-images.githubusercontent.com/29874379/54909420-83827b80-4f2d-11e9-8a9b-f39c82419c34.jpg) Issue occurs both TS1/TS2 source name resolutions. It **must** happens after I key up(Accessing TG or Reflector). Also occurs randomly(usually TS2) ![S__204087301](https://user-images.githubusercontent.com/29874379/54909419-82e9e500-4f2d-11e9-96ec-9d7b5e38ee4c.jpg) Tested on Windows, Armbian with latest commit...

@m0lmk DMRGateway/MMDVMHost does not designed for duplex using https://github.com/g4klx/DMRGateway/issues/78#issuecomment-475493134 Also you can not trigger PTT when you still receiveing on same TS[As for now, MMDVMHost accepts RF, but DMRGateway blocks...

Lol you spoke too soon... I addressed duplex issue earlier(/w my aweful english descriptions... sorry) #74 (comment) For example... XLX + DMR#1~4 configured/connected. Someone#1 talks to TG9 via XLXNetwork:TS2, Someone#2...

@shawnchain Actually it is not packet out-of-order issue. As you can see PacketSeq(`payload[4:1]`) is incremental(sequencial) with Frame#, But VoiceSeq(`payload[15:1]`) not a sequencial/mismatched with PacketSeq. It seems IPSC2 server application problem....

Log sections only??? I don't think [so](https://github.com/g4klx/MMDVMHost/blob/2aa130e22fb63298f661e5d17ea9f07961bc268b/Conf.cpp#L339-L345). Make sure you really modified right configuration file - CMDLINE should be `MMDVMHost _RIGHT_CONFIGURATION_FILE_EDIT_ME_`

https://github.com/qrp73/NanoVNA-Q/issues/13#issuecomment-552679259 Mine(Green PCB) was around 6.5 MHz