> On 01 Mar 2016, at 16:04, Abhinav Jadon wrote:
>
> Hi,
> Updated the module, the same problem persists although this time the
> transmitter took longer than usual to turn off.
I’m running a bit out of ideas :-/
Since I cannot reproduce the problem, it would be great if you could compile
Hi,
Updated the module, the same problem persists although this time the
transmitter took longer than usual to turn off.
Cheers
Abhinav PS Jadon
2012122
Electronics and Communication Engineering Undergraduate
IIIT - Delhi
IASc Summer Research Fellow 2015
*E*: jadonabhi...@gmail.com
*M*: +919650
Hi,
I just pushed a commit to github.
Would be great, if you could update the module and let me know if that fixes
your problem.
Best,
Bastian
> On 01 Mar 2016, at 15:25, Abhinav Jadon wrote:
>
> Hi ,
> Sorry for the delay in following up. Had mid semester exams to prepare for.
> I have a
Hi ,
Sorry for the delay in following up. Had mid semester exams to prepare for.
I have a 8GB RAM Core i7 PC. Just to be sure that this wasn't a PC issue. I
ran it on a 16GB RAM Core i5 PC. Same issue propped up. So that leaves out
the memory leak option.
Abhinav PS Jadon
2012122
Electronics and
Hi,
> On 20 Feb 2016, at 12:05, Abhinav Jadon wrote:
>
>
> new mac frame (length 10)
> =
> frame too short to parse (<20)
> thread[thread-per-block[3]: ]: std::bad_alloc
> [Thread 0x7fffad60d700 (LWP 4907) exited]
Looks like you run out of memory :-/
Hi Bastian,
I used the Tag Debug Block to check on the sample generation. The Tag block
stops throwing debug data after few seconds which is followed by the TX LED
turning off. Thus I inferred something is happening on the code front.
Also,
to figure out what was going behind the scene, I used th
Hi,
> On 17 Feb 2016, at 11:45, Abhinav Jadon wrote:
> Upon running the transceiver code on a single X310, the transceiver shuts
> down after few seconds of action (the LED ceases to blink) while the RX
> continues to be up and decodes the packets.
I can’t tell you much about the LEDs of the
Hi Bastian ,
There is another issue regarding the same topic I would like to bring to
the fore.
I use a pair of X310. Due to some constraints, I shifted to one X310.
Upon running the transceiver code on a single X310, the transceiver shuts
down after few seconds of action (the LED ceases to blink)
Hi,
> On 14 Feb 2016, at 14:46, Abhinav Jadon wrote:
> There are no overruns and the connections to the antenna ports are correct.
> The frame detection is working
Note, that this also means that frame detection is only triggered once per
frame. Sometimes, it can be triggered all the time (i
Hi Bastian,
There are no overruns and the connections to the antenna ports are correct.
The frame detection is working
I tried all the stuff you told me to try ie I tried LMS ansd LO offset,
they worked as in I saw some packets being decoded by the wireshark
connector. But the packet content was i
Hi
> On 10 Feb 2016, at 15:13, Abhinav Jadon wrote:
> Next I replaced the loopback with a uhd source and sink and connected the RF
> frontends using a SMA cable. It fails to give me any packet (the wireshark
> connector). I tried playing with the value of rx_gain and tx_gain. I also
> tried pl
Hi ,
I was working on the Wifi Transceiver Flowgraph. I created a loopback in
the flowgraph itself to be sure that atleast the transceiver works in
theory. It did work like magic.
Next I replaced the loopback with a uhd source and sink and connected the
RF frontends using a SMA cable. It fails to
12 matches
Mail list logo
