Search results

When using a tap, it is important to keep backing it out to clear the swarf as it cuts and a smear of grease will keep the swarf together. There should be no risk of destroying the insert unless you go at it like a Gorilla!

Yes, no. I give advice based on my own personal engineering experience over five decades. It is up to you what you do with it. All examples of these that I have used take an M3 nicely. If you have one which is larger than normal, then tap M3.5 or M4 as required.

I have used many of them, an M3 tap is DESIGNED for metal.

A carbon microphone is a variable resistor, so hopefully that will help you to utilise it. Originally it would have a 50V power supply.

Easy enough to put an M3 tap through them.

Finally got the display to work. 100r resistors on MOSI, SCLK and CS cleaned up the ringing nicely.

I am now going to design it for the Teensy 4.1. I do have a few issues to solve on the 3.6 version first, the pressing one being that the keyboard (Ps/2) input seems to die after a sentence of more than a few characters. The Teensy continues to run and functions as normal, there is just no...

Indeed. I have tried that and Controlio, even on a paid for service they are unable to help much and often send you off down rabbit holes. When you point it out, apologies are forthcoming and sense resumes for a few minutes. Then it goes back down the rabbit holes again. Treat AI like you...

I know this is an old post, but nobody seems to have put it right before. The two batteries will stabilise at a similar terminal voltage and no harm will result. Paralleling batteries is an established method of improving current capacity.

A 7805 from 12V is probably going to be close to exceeding its ratings, especially "bareback". Even at 200mA, a fraction of its capability the dissipation is 7V x 0.2A = 1.4W. You would be better with a switching type regulator.

This was an irritation here too, as I was using the secondary SPI on the 3.6 to avoid the Audio board. Now of course the Audio board uses it and the SPI goes back to convention. It is going to need yet another PCB redesign to use it in this project but maybe I should be satisfied with one...

That's very helpful and I will experiment further. Is the touch panel the GS1680 type? I have had zero luck in getting mine to work, but persevering with it when other jobs are sorted. Fonts wise, I could do with one a third smaller than standard. The smallest is far too small and the...

The holes are large clearance holes for plastic mounting pillars and I understand that boards are drilled before processing. Therefore there should be no issue, although after finding a major error on that board due to mirroring (again!) I will put a prohibited area around them for Mk6.

That is the working set with the T3.6. The device is behind the display with very short lines direct to the pins on the display.

Many thanks for that suggestion, how low can I go? I did put the 'scope on the SCLK signal and was surprised that it wasn't a nice clean square wave of a constant frequency. But hopefully that just shows that I am unfamiliar with the way SPI actually works.

Tried that: //tft.begin(12000000); tft.begin(12000000, RA8875_800x480); // Init the tft

Referring to this thread... https://forum.pjrc.com/index.php?threads/ra8875-and-4-1-with-spi.69787/ Was anything ever achieved? I have two of these displays and they work fine with a Teensy 3.6. However I have been unable to get a coherent display with the 4.1 Teensy. Once in a while it will...

I uninstalled everything and reloaded it step by step and the 4.1 has appeared and seems to be working.

In Devices, I have checked that it appearsas a USB keyboard. Removing that device and reinserting Teensy reloads it, so I am confident that the hardware is OK. My suspicion is that the loading of Teensyduino boards manager is failing. I do see it "loading" before the window disappears once in...

I have been using a T3.6 without issues. Connecting the same computer and cable to the Teensy 4.1, it is not recognised and is missing from the list of boards. It doesn't appear in the list that can be loaded either. The Teensyduino add on has been setup and all other Teensy boards are there...

1.6mm I would guess unless it is a multilayer PCB.

A hardware debounce might be useful perhaps?

I am using the PS/2 keyboard for now, but I have made provision for playing with USB. There is a "breakout" which terminates in pins at the edge of the PCB for all the optional connections.

This is a derivative of the PD0LEW design, using a Teensy 3.6. This version uses an RA8875 display and has been a real pain in the rear to program it! I had some help interference from various AI services that mostly led me astray, but eventually I have a working receive section. Sadly the...

Thank you. I read your response 30 minutes after sending the boards for manufacture, but I think that the boards can be modified to suit fairly easily. This is a 3.6 but I assume that the same applies as for the 4 series. Teensy isn't pulling half an Amp, no. My circuit is pulling that and...

I am still not understanding, sorry. I can't use the onboard regulator to power the circuitry because it is pulling over half an Amp. Plugging in the USB or feeding Vin with 5V means that the circuitry is fully (if USB powered only) or partly supplied by that onboard regulator instead of the...

Sorry to hijack the thread, but could you elucidate on that for me please? In my high current requirement project, do I cut the track and then feed just the 3v3 input, or as I assume, the 3v3 LO pin as well, for the audio board? If I then try to program the Teensy, does it work as normal...

Just run the microphone (suitably amplified) into headphones. If it sounds OK, don't worry about it any more than that.

You need to forget digital for a moment and go back to principles. Noise cancellation is done wideband, not at spot frequencies, except for individual cases. Present for one channel, a line level "clean" signal and one from the "dirty" signal and sum them. The difference is the "dirt"...

That microphone response graph is the inverse of what I would expect to see. The notches are also strange, unless the microphone is faulty. Even then, it is not going to be doing much at VLF! I have a suspicion that you are still trying to input raw signals and that is why the response looks...

My (5") display has similar issues, but the capacitive controller is the GSL1680. I can get no response whatever from it. GSL1680 data sheet.

First quick test was to incorporate SPI.h into a working system with an OLED. That compiles and loads with no apparent detriment to anything else. I will keep tinkering. Next test was to remove the speed restriction from begin.tft... No difference.

Fully understand that Kurte, it's like looking for a needle in a haystack at midnight! The heartbeat LED stays off and when I have my sensible head on again I will try to break it down. My feelings are that it is to do with SPI because that is the only thing different to a previous TFT that I...

Today I have been able to start modifying the software to suit the new display. I have tried al the options for the pins and it has made no difference to an issue of possible incompatibility. The program starts to run and then appears to crash every time before it starts to look for input from...

Progress is being made. I have now got compilation success on alternative pins, to avoid the audio board and other pins I have already assigned. Reset is pin 11 on the parallel bus connector JP3. This works: /* Explain the minimal setup and how to use instances... */ #include <SPI.h> #include...

Curiouser and curiouser! I have reconnected back to a decent 5V supply, the display and Teensy share the same supply. No change as expected. I then took a flylead from pin 11 on the parallel bus and flashed it to earth. The display went black and on the next boot, it came back uncorrupted. I...

Thanks both. I will have another dabble but I am getting convinced that the board is faulty, so have emailed the seller for their comments.

This is an interesting document for I think an earlier version. It shows pin 10 on JP2 needing a seperate interrupt signal fed to it. https://forum.arduino.cc/index.php?action=dlattach;topic=232749.0;attach=115746

No difference apart from the (corrupt) image being smaller. Still the same random selection of different screens. This is what I ran... /* ROUND GAUGE EXAMPLE with ballistic! This example show how to create 3 round gauge that react like the real one with (almost) correct ballistic The 3 gauges...

Jumpers verified, will try the other resolution setting now. It is as you suggest, sold as an 800x480.

Another one of the random displays after a reboot...

The 'sillyscope' traces...

A few more images and the connection diagram from their datasheet...

I have the latest or at least a very recent build of the IDE. I removed the RA8875 library from the included libraries because it was being selected for compilation rather than the t4 library. It compiles correctly according to the debug information. The images show a variety of screens after a...

Hi Kurte, I can't find that particular sketch on my system. I have done more testing, both with the embedded library and the forked library. I have also connected and configured the Reset line, all without benefit. I can see the clock starting every time now, so happy with that. There also...

I have tried a few things... First I improved the power supply to the board. The display is a 5V so was being powered from the USB supply, but now it is on its own decent supply and the Teensy is also fed from it on the Vin pin. Next step was to lift the Teensy out of the breadboard, remove...

Thank you Kurt, that is greatly appreciated. I have got it installed and have been trying to get it all working to no avail. I am not at my best so will have another play tomorrow. Symptoms are a black screen, with all connections to it 3.3v high. I thought that CS ought to be low? Anyway...

The Sumotoy library will not compile. I am using a 3.6 and have tried to compile without making any alterations to the basic setup example. The Adafruit library is hard coded to use pins that I don't think I have available, according to the header in its example for a Uno... // Library only...

It really is that simple? I thought that the pin assignments were going to conflict, the Adafruit library for instance gives only a single option for connections and I thought that the other one only had a couple of options, neither of which matched what I have in use. Sorry if I am just being...