Could also be the clock or just be the board I am using as many of the signal lines are dual function. I am hoping it is just related to stack and heap sizes and not some crazy interrupt problem.
#Rs ba1 ebay code
Big bug there as I can't get the USB and LCD code running at the same time, I mean WTF?. Way beyond my scope, I just want a couple more encoder dials (to hang my overweight knob on ) So now onto the LCD design. There's enough horsepower in this board to also embed a CW reader, decoder for digital modes, etc. A slanted 3x5 LCD touch screen with an encoder and knob. I'm sure I can get over that hurdle but it is their design so unless they publish the USB encoder design requirements in the future, which I doubt, I feel like I would be stealing. The hassles around a commercial product plus fighting with Icom as I reverse engineered their device would take the fun out. Anyway, I realize there is interest in this as us amateurs like to tinker so I am leaning more towards offering this as a QST or QEX project rather than trying to make it commercial.
#Rs ba1 ebay software
The radio would spin the frequency really fast, hard to even see the numbers, but the RS-BA1 software would just click along in 1.2sec jumps. I must have recompiled, tested and traced my code using Wireshark (thanks again for the that advice) 100 times. Anyway, I got it working so now I can move ahead. Then I had to program the ramping to take advantage of the ramp feature on the radio. So this meant I had to re-architect the code to be two-way (interrupt responding) to this packet as well as pacing my code against the host application ack's coming in. I was replying but about 50ms too slowly. Finally I found a packet coming from the RS-BA1 code that asked for the device firmware level. This drove me crazy as I just couldn't figure it out. Sending my frequency updates to the host code were being paced at 1.2sec vs the radio was just ripping right along. But that is done with the control endpoint (I'm told) and I am using the bulk in/out endpoints. There is a slight difference in a USB keyboard as the caps lock and other lights are set by the host PC. Remember my base code was originally designed to be one-way as a mouse and keyboard act. Here's an update: I had a heck of a time getting my code to work in two-way mode.
0 kommentar(er)
