Hi Darwin,

Not sure if you saw my earlier comment, but I had power sequencing issues occasionally on my v6 that would lead to a blank white screen. I added some code to force wake the screen in my software version, and that seemed to solve the problem for me. You might try R1.5.0.



Reed

Hi Reed, I saw your message earlier but I’m thinking of making sure I did not fry the display, I’m new to amateur radio , my first HF is ubitx v5 & recently QCX x40m, and again lately learning arduino/IDE/sketch. ?I will try to load your software , thank you very much.

73 de EI3IHB ?

Hi, I uploaded with the new ubitxv6 or R1.5.0 firmware with 30316 bytes and 38plus tabs using old boot loader but still with white screen. J1 is jumpered , led pin on display is powered from raduino pin15 otherwise it’s blank.?

Dang. I was hoping that would "Just Work".

Since you were able to run a test pattern on the screen, the next step I would take would be to hook a oscilloscope and/or logic analyzer up to all of the SPI pins and compare the signals during the successful test pattern against the failing Arduino output. Not sure if you have access to those sorts of tools though.

?One possible failure point would be if the Arduino's CS pins were reversed. If you touch the screen, can you cause stuff to happen? You won't necessarily know what you're pressing, but you should be able to hear changes in the sound when you, for instance, change VFOs or bands. Alternatively, if you swap the pins for CS to the touch screen and CS to the display, does it work?


Reed

OK, looking at the V6 Raduino schematic, here are the TFT Display pin#'s and where they would go on the Raduino's NANO.? Also their output name so you can correlate if not using a NANO - they have to match the pin assignments in the software.

Jim - W0EB

TFT Pin# and where it goes.
1 = VCC = to NANO pin 12
2 = GND = to Raduino ground
3 = CS_TFT = to NANO pin 28 (D10)
4 = RESET = Same as TFT pin 1
5 = D_C = to NANO pin 27 (D9)
6 = SDI = to NANO pin 29 (D11)
7 = SCK = to NANO pin 1 (D13)
8 = LED BACKLIGHT = through 22 ohm 1/4 watt resistor to +5V (hot end of resistor to TFT pin 1)
9 = SDO = to NANO pin 30 (D12)
10 = SCK =? to NANO pin 1 (D13) - parallel with pin 7 on TFT
11 = TOUCH = to NANO pin 26 (D8)
12 = SDI = to NANO pin 29 (D11) parallel with pin 6 on TFT
13 = SDO = to NANO pin pin 30 (D12) parallel with pin 9 on TFT
14 = NO CONNECTION

Reed , no response if I touched the screen , even if I swapped the CS cables , can hear Morse Code on ubitx , the volume control is responding but not the tuning knob. No response with cw key but can hear click when I press ptt ,but no rf output based on swr meter. And I don’t have an oscilloscope & my Elmer is cocooning. Btw I’m not successful in loading a software to test the touch function of my ili9341 to verify if the “touch” is really working. ?Thank you.?

Yeah, I can make a build with some debug output tonight.

I'm somewhat surprised that the knob would also not be working. That's a pretty basic device. You might re check all of the wires, and ensure that you have appropriate pull up resistors, since I think I remember that the v6 had some built in that the v5 did not.


Reed

开云体育

开云体育

Alright. Darwin - on my Github, there's now a branch called "input_output_debug". Select it, download it (or git fetch, if you prefer), and load it onto your radio. This software does NOT work as a radio, but may help in debugging.



This branch doesn't activate any of the normal functions or menus while running, but rather produces output from inputs fairly directly. When you push the knob button, you should get a beep. A long press will get you a different beep. Touching the touch screen will produce a different beep. Long pressing the touch screen will generate yet another kind of beep. Turning the knob will produce different kinds of beeps depending on which direction you turn it, and how fast you turn it.

In addition to all the beeping, on the screen there are two squares drawn that light up with the button presses (black normally, white when short pressed, red when long pressed), and two text boxes indicating how far the knob has been turned recently, and what the last point (in pixel coordinates) touched was.

Finally, all of the input data (button presses, touch presses, touch locations, and knob turns) are streamed out on the serial port, so even if your screen and speaker don't work, you should be able to get data out on the serial monitor with a baud rate of 38400.

Give it a shot, and report back on what you observe. What makes it beep? What doesn't? What data do you get on the serial output? Do you get anything on screen?


Reed

Reed, I will try this tonight & update here, thank you very much .?

Reed, I loaded the nano raduino with ubitxv6_input_output_debug (28,980 bytes & ~74tabs) , the ili9341 is still showing white screen & no response when touched. Tuning knob will produce crackling noise when rotated, can hear statics when knob is stationary , no beep with quick press but with beep with long press ( beep after ~3secs ) . Volume knob is still responding ok, the ptt & cw key is silent.?

I tried the 3.5” nextion enhanced, touch is responding but not all items on the screen ?& the frequency is fixed at 0.0.0 , thank you very much.?

darwin EI3IHB?

Reed, ?I’m still reading how to transfer data thru serial port from arduino.

W2CTX , Nextion is a touch screen display used for KD8CEC firmware on ubitx.?

Hi Darwin,

The serial monitor should be very simple.

1) Open serial monitor from the tools menu


2) Select the desired baud of 38400


At that point, you should see text coming out.


The volume knob is purely hardware, so I wouldn't expect it to do anything based on software changes. I didn't put any beeps on the PTT and CW keyer, but also didn't disable that code, so I would have expected them to function "normally". On my rig, running the input_output_debug build, the PTT triggers the relay and shows "TX" on the screen. CW key input doesn't do anything. Here's a video of me manipulating the test build: https://www.youtube.com/watch?v=Wbpqw5-YeXc

If you're not getting beeps for all of the various inputs, then I suspect that there's some sort of hardware issue, connections, or something. That's not something I can easily help with, unfortunately, since I can't probe and check the physical stuff remotely. If you can you sketch a basic diagram of how you have stuff hooked up, that might be helpful. Make sure to draw not what you THINK you have done, but rather, make sure to look at your setup, and draw what is actually there. I did see your image on 6May (#78647), and it looks like there are several missing connections that I would expect you would need, but I don't know if you've changed things since then.

• The touch screen T_DO and T_DIN need to be connected to the SPI bus with the screen, or the touch screen part won't work (though it wouldn't prevent the screen from working). Using the v6's schematic notation, with the VCC as pin 1 and ground as pin 2, pins 7/10, 6/12, and 9/13 of the LCD should all be connected in pairs, so that the SPI clock, MOSI and MISO are shared between the two devices on the board.
• The v6 schematic has the screen's reset and LED pins both pulled to 5V, whereas you have them floating - not sure if this is a problem, but it is a difference

Reed