Keyboard Shortcuts
Likes
- BITX20
- Messages
Search
Re: W8TEE TFT/VFO DDS adapter
¿ªÔÆÌåÓýFor TFT info, this library works with the display I can't get to work with MCUFriends.
On 6/18/2017 11:40 AM, Michael Hagen
wrote:
|
||
Re: new SI5351 library tested OK on Raduino
It's just the standard library at
toggle quoted message
Show quoted text
You can also use the built-in function of the IDE to update the library to the latest version 2.05 73 Allard PE1NWL On Mon, June 19, 2017 02:09, Fede wrote:
Allard, do you know where i can download that Library? |
||
Re: BITX QSO Night, Sunday, June 18, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere
Hi Bill,
Very happy to have my first QSO Bitx to Bitx. I know my report was 33. Your signal was better, at about 36. Anyway my callsign is VA3NOI. My fellow Canadian VA3NFI does not own a Bitx40. Thank you for the contact and 73, -- Ion VA3NOI |
||
Re: BITX QSO Night, Sunday, June 18, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere
I was on from 7 pm to 7:30 pm EDT.? Very happy to work KC8WBK, N9ARZ, VA3NFI, KF4WBJ, and WI1B.? WI1B was not on a BITX, but he has?one in the shack and?will put it on the air soon. I was running my BITX DIGI-TIA (Digital VFO/BFO and?Termination Insensitive Amplifiers) to a CCI EB63A amplifier at about 100 watts.? Antenna is a dipole. I think we did?pretty well, considering?the band conditions.?? 73? Bill N2CQR? On Monday, June 12, 2017 2:38 PM, KC8WBK via Groups.Io <cruisenewsnet@...> wrote: BITX QSO Night, Sunday, June 18, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere Join us as we make contacts from BITX40 to BITX40 on 7.277 MHz in 40 meters! To participate, call CQ BITX at 7pm sharp, your local time, on Sunday. Call off and on for about 15 minutes. It is helpful if you call CQ BITX with your name and location.? Repeat your call a number of times if conditions are weak. This is a worldwide event at 7pm in each time zone.? You may participate in any time zone, regardless of your location, so you may wish to call in at 6pm, 7pm and 8pm, your local time, to contact hams in adjacent time zones. Report your QSO's, discuss propagation, noise, signal reports, audio reports, antenna type, etc. in this thread. This is an undirected, scheduled event.? The BITX QSO Night relies on you to call CQ BITX to initiate contacts with other stations, so warm up that final and transmit a few calls at 7pm on Sunday.? Talk to you then! |
||
Re: BITX40 TFT DISPLAY CODE - Coding A Control Button - Looking for Assistance to figure out why a Step Tuning button does not work
Jack,? After changing: ?text size in line 302,340,376 ?the sw1, sw2, sw3 ?now look good - right place right size. text size in line 850 was a 4 now a 3 - frequency correct size and fits perfect. The next one is the meter size its to wide ?when comparing it to your good display. ?---- looked where to change value ?but could not find to make it narrower. Your good display only goes as wide as the w in sw2. The msg is till not in correct place - did not find a location where to force it lower Getting closer........ Joe VE1BWV On Sun, Jun 18, 2017 at 1:53 PM, Jack Purdum via Groups.Io <econjack@...> wrote:
|
||
new SI5351 library tested OK on Raduino
Yesterday Jason NT7S released a new SI5351 library version 2.05 on github.
In the past it had been noticed that previous versions (2.02, 2.03, 2.04) produced strong clicks/pops during tuning. These clicks were caused by the PLL being unneccessarily reset each time the frequency was updated. For this reason it had been advised to use v2.01 until this problem is resolved. The PLL reset issue is now resolved in the latest library version 2.05. I have installed the latest library and found that it indeed works OK with the raduino code. So we can now safely use the latest SI5351 library version. Thanks Jason! 73 Allard PE1NWL |
||
Re: BITX40 package size
Where was the bit of track? ?Where was the spark?
toggle quoted message
Show quoted text
Might yet be brought to life. But at $59, a reasonably cheap lesson in what not to do. On Sun, Jun 18, 2017 at 02:57 pm, <mattcarus@...> wrote: small spark then nothing (raduino dead too ?) - clearly that bit of track was acting as a fuse.? |
||
Re: BITX40 package size
Right, got some time in front of the BITX again - here's an update...
Incorrect polarity was the original problem so fixed that. Powered up and everything looked OK - raduino lit up, no smoking parts, however no audio out either. Checked audio jack wiring and it looks ok, also no leads shorting out or anything like that, hmm ok, it's getting late so I'll try another day. Putting it all away I noticed a burnt out track on the bottom of the board. I'm getting a bit impatient and instead of checking what the track is, I just replaced it with some jumper wire and try power again... That was a mistake, small spark then nothing (raduino dead too ?) - clearly that bit of track was acting as a fuse. Packed it away again, slightly more annoyed than I was before (annoyed at myself, that it). I'm rapidly coming to the conclusion that I've probably damaged it so much that simply replacing it would be the least painful option. Matt 2E1HNK |
||
Re: Shielding plastic cases
Master Ice
?
Why not try the RS components spray on
screening, stock 247-4251.
It
gives a?silver plated copper shielding coating designed to give low
resistance even in thin layers on plastic electronic
housing.
I
used to use an earlier version professionally on cryptography equipment to help
limit compromising emissions.
It
worked very well and is intended for plastic.
It's
not cheap though.
?
Slim
G4IPZ
|
||
Re: Shielding plastic cases
I cant understand why some go to the trouble of buying a plastic case and then have problems about screening and not get an aluminium of steel box in the first place. Obviously aluminium is easier to work with. A bit of exercise with drills and files to drill and file holes as required will do good to everyone. Just take it easy and remember to measure twice and cut once. Regards Lawrence On Sun, Jun 18, 2017 at 7:51 PM, Kevin Gilot <kevinemtid@...> wrote: Thanks for the photo. When I thought Tape I was thinking strips of 1/2 inch or so across the case. Not fully covering the inside of it.? More of a Cage rather than a Box. Okay, makes sense to keep of the stray RF and such.? |
||
Re: Universal Case For Bitx And other Ham Radio Projects
¿ªÔÆÌåÓýThat is nice work. ?The design is attractive.? The web pages are being rebuilt. Please let the list know when your web store is back up and running. ? 73 de w9ctw |
||
Re: W8TEE TFT/VFO DDS adapter
¿ªÔÆÌåÓýAs suggested I am trying to get MCUFriend grafixtest to run. After hard coding to use 16 bit I get this error..... Is the Carrot underneath just a marker for pointing out the error?
C:\Users\Michael
Hagen\Documents\Arduino\libraries\MCUFRIEND_kbv-master\MCUFRIEND_kbv.cpp:573:23:
error: 'write_16' was not declared in this scope Strange, "^" I did not put it there.
Mike
On 6/18/2017 11:12 AM, Jack Purdum via
Groups.Io wrote:
|
||
Re: W8TEE TFT/VFO DDS adapter
¿ªÔÆÌåÓýI never added that define statement, it was found as an Error. I know everything is case sensitive, as I AM ON Page 100 of you wonderful Book! It is great reading, especially waiting at the Kaiser Hospital
for an appointment! ? So the error came out of adding the Define.? Fell out of the
sky. I went to the If else statement and hard coded it to ?? #define USES_16BIT_ BUS 1???? and still get errors. I tried getting help on Arduino Forum,? I don't know how that is going to go. Mike
On 6/18/2017 11:12 AM, Jack Purdum via
Groups.Io wrote:
|
||
Re: Universal Case For Bitx And other Ham Radio Projects
Joe Puma
¿ªÔÆÌåÓýLooking forward to seeing your cases on eBay. Please email the group when the cases are available as I am interested in buying one.? Thanks, Joe KD2NFC Sent from my iPhone On Jun 18, 2017, at 1:28 PM, Sunil Lakhani <vu3sua@...> wrote:
|
||
Re: W8TEE TFT/VFO DDS adapter
Jack Purdum
This error: "error: 'write_16' was not declared in this scope" suggests that in your code you used: #define write_16 which probably needs to be written: #define WRITE_16 since most C programmers write symbolic constants in upper case letters. C is case sensitive so?WRITE_16?and ?write_16 are different symbolic constants. Jack, W8TEE From: Michael Hagen <motdog@...> To: [email protected] Sent: Sunday, June 18, 2017 1:27 PM Subject: Re: [BITX20] W8TEE TFT/VFO DDS adapter Thanks, I added the 16Bit define in C file. now get error in Jack's code? "error: 'write_16' was not declared in this scope" Maybe there needs to be a ref to an external something? I think my correct display type is "ILI9481"? Which I have seen 0XDBDB returned in a test? I looked at Rinky Dink documents.? I looks like it uses the Data d0-d15 on the top half of the right side double connector. D37 and up.? The top pins are 5V.? Then d39 & d41 on the right side for Wr and Rst. d36 & 38 on the other side for RS and CS.? They say that's all on the Mega they use on that connector? On 6/18/2017 9:48 AM, Vince Vielhaber wrote: > > I haven't looked at the other responses yet, so I'm assuming you got > that info.? If not, I think you'd need to add > > #define USES_16BIT_BUS > > at the top of libraries/MCUFRIEND_kbv/MCUFRIEND_kbv.cpp > > Did you try 0x8357 as the g_identifier?? I see that it's in the > library so yours may just not be getting accessed correctly. > > Vince. > > > > On 06/18/2017 09:57 AM, Michael Hagen wrote: >> I am looking for a file in MCUfriend? >> >> A header or C file? >> >> Is there a #define somewhere to use Mega 2560 Pins. >> >> Yes, I have it plugged directly to a Mega, so I would need that option? >> >> >> I tried changing ID in Jacks new code.? Still nothing.? Default 0xD3D3. >> >> >> Thanks, I don't know where to look? >> >> Mike,WA6ISP >> >> >> On 6/18/2017 4:34 AM, Laurent CHABERT wrote: >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> *De :* [email protected] <[email protected]> de la part de Vince >>> Vielhaber <vev@...> >>> *Envoy¨¦ :* dimanche 18 juin 2017 05:00 >>> *? :* [email protected] >>> *Objet :* Re: [BITX20] W8TEE TFT/VFO DDS adapter >>> >>> >>> Did you try changing that line of code in the MCUFriend driver that >>> Jack >>> mentioned the other day?? That one's using the mega pins as opposed to >>> the standard pins. >>> >>> Vince. >>> >>> >>> >>> On 06/17/2017 01:09 PM, Michael Hagen wrote: >>> > Yes Rinky Dink works but I can't get any MCU Friend to work.? I spent >>> > most of the day playing with it. >>> > >>> > My TFT is directly plugged into a Mega 2560.? Its pinouts fit like a >>> > shield over the top of the 2560. >>> > >>> > Any hints to give me?? I don't know why? Rinky Dink works. >>> > >>> > I have run the ID program in MCUFriend, no ID.? I know that the >>> package >>> > says HX8357B for Driver? >>> > >>> > Mike, WA6ISP >>> > >>> > >>> > On 6/16/2017 4:58 PM, Vince Vielhaber wrote: >>> >> If the UTFT library works (the one from Rinky Dink) then the >>> >> MCUFriend_kbv library should once you find the right parameters. >>> UTFT >>> >> is slow and a memory pig. >>> >> >>> >> Vince. >>> >> >>> >> >>> >> >>> >> On 06/16/2017 07:40 PM, Michael Hagen wrote: >>> >>> Bought 2 of these displays.? Less than $8.? No Touch Screen. 36 >>> Pins, >>> >>> not 40. >>> >>> Uses 9481 Controller, package says Driver: HX8357B? >>> >>> >>> >>> Work fine but not so far with your recommended library (Friend?). >>> >>> A library at Rinkey Dink Electronics works? >>> >>> >>> >>> Parallel transfer, not serial. >>> >>> I did not look at whether you used serial or parallel? >>> >>> >>> >>> Mike, WA6ISP >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >>> > >>> > >>> > >>> > >>> >>> -- >>>? ? Michigan VHF Corp.? >>>? ? ? ? ? ? ? ? ? ? ? ? ? ? >>> >>> >>> >> >> > |
||
Re: Reducing output power?
Forgot to mention... ?I used this heatsink: ?
For low-power work without the input pad, the WA2EBY linear works well for WSPR, and the PSU flexibility provides some easy output power tailoring. ?I use a 'drok' DC-DC boost converter when I want to run full output power. ?250mW of input and 13.8VDC gives some signal boost, and the output power can be increased by adjusting the DC-DC through 28VDC. |