Search results

On the 3V3 side of the ISO7721, the signal EXT_RX_3V3 is connected to INA. It seems it is the UART TX signal. Correct ??? It could make confusion for other persons than the schematics creator. TX pin should be named ".....TX....", on both sides

Could be interesting to know which application requires more than 3 canbus.

Check this thread and this post. I had the same problem and added the FLASHMEM attribute to all LVGL code. Definitely not a good way to do it. What looks strange to me, LVGL is succesfully used on ESP-32 which has less RAM. Is the code executed only in flash on the ESP-32 ???

I read : we operate in a noise environment Are signals comming from outside filtered, protected, limited,... ? or are they directly connected to teensy pins ??? How is your electronics connected to earth ground ??? And the PC used to connect to the Teensy ??

Just my 2 cents, the learning curve of CANopen is long, slow and painfull. I tried to learn, in order to help a collegue on the SW part. I switched back to the pcb design. Unless you should implement slave nodes to an existing master, you could still use CAN implementing your own protocol.

Is the Adafruit library able to handle 2 separate displays ??? May be it has some global variables. Try to connect only one display and make it work.

Using the debug library, debugging is also possible on Platformio. See https://forum.pjrc.com/index.php?threads/using-gdb-with-teensy-without-hardware-debugger-first-beta.61373/

Try PlatformIO.

No idea. As I said, try 1MHz. You have tracks too close to the big round holes. Machining these holes could touch these tracks depending on tolerances on everything: dimensions, positioning on the machine, tools used, and so on. And imagine you have to make these holes bigger for any reason...

SPI works on short connections. On your picture above, it seems the display is connected on the right to the red pcb. And, if I am correct, the Teensy is connected on the left of the red pcb. It makes a "long" line. Try 1MHz or even lower.

Try much lower than 12MHz, just to confirm it is not related to speed. And also measure SPI signals with a scope, both on the teensy and on the display.

In the thread you mentioned, last post, KurtE suggested to lower the SPI frequency.

Ethernet ?

I realise my question was not clear, and I corrected it in the first post and title. The right question is : are the Double handled by M7 core hardware by default ?

I use Float64 in a Teensy 4 GPS application to compute things like line crossing detection, distance measurements, and probably RTK in the future. I know the 600MHz is waaayyyy enough to compute the GPS 25Hz outputs, even unsing ieee library. But it would be nice to use what the M7 core offers...

I also use 24 to 5V DC-DC to power Teensy and a GPS module. On the Teensy, don't forget to cut the trace on bottom face and put a small diode on the pads. Don't hesitate to put ferrites, 1nF, 10nF and/or 100nf capacitors (any combination) on the Traco converters outputs

SPI and 3m cable ?!? What SPI clock frequency do you use ??? SPI on long line is not a good idea. Even tenth of centimeters could be hard. As you have 10 wires, you can try to implement RS422 interface for each one of Clock, MISO, MOSI and CS1.

I remember some devices sampling MOSI pin at falling edge of clock signal. Maybe the other edge, but not the standard way of SPI communication. It was on the 68HC11 era, and in the SPI setup, you could choose various clock phase and idle levels.

No decoupling capacitors ?????? Check page 85 of the datasheet.

Your switch code should be: switch (Mode) { case MM: mm(); break; case TPI: tpi(); break; case FEED: feed(); break; }

70kBytes/s is about 560kbits/s, far from 8Mbits/s. I don't know what is involved, but you have probably a lot of software overhead. Is the ESP32 able to receive at rates higher than 8Mbits/s ??? Not the bitrate set in the registers, but the rate of received bytes.

What is the default SPI bitrate ??? It looks like you don't change it in the code. You setup the Wifi, but no bitrate change.

See this thread

If you mainly need Teensy with canbus, check https://www.skpang.co.uk/search?page=2&q=teensy%2A&type=article%2Cpage%2Cproduct

I would not rely on a SD card for an important file written so often. External flash chip is maybe more reliable, I don't know. The best solution is to use a FRAM.

Wait, I just described the Teensy 4.2 :eek::ROFLMAO:

Using 0.1"/2.54mm pins rows instead of SMD connectors would be easier to use on any proto board available. After the proto phase, designing a carrier pcb for projects would be far easier by not using smd connectors. 4 small mounting holes would allow better fixing than relying on the pins. Let...

Time to use an old school LM555 :ROFLMAO:

If the fan has long wires, protect the Teensy for any radiated or conducted EMI.

Searching with "pc fan control arduino", you will find you need a PWM signal and could read the fan speed. But these two signals are 5V (if I am not wrong). And the Teensy is 3.3V, inputs beeing not 5V tolerant. The FAN PWM signal could probably accept the 3.3V signal comming from the Teensy...

USB and EMI are not good friends. You should use good shielded cables, filters on data, GND and 5V lines. Good pcb design also helps, using internal layers for USB signal routing. At the end, it is still possible the USB peripheral in the Teensy microcontroller is not very good at handling EMI...

As my collegues just asked me for a GPS solution to avoid cabling, I made further investigation about what this system is suposed to do. I discovered that this system is not directly involved for certification. It is more an internal tool for the first tests when checking the braking system. But...

In the current system, the driver start the measurement by pressing a button. He has one hand on the speed/brake lever, and the other on the button. At the same time he presses the start button and apply brake. When the vehicle stops, he writes the numbers, time and distance, on a test report...

I will use of the NEO-6P just for the prototype phase, and just because it is in my drawer with an unused Teensy board. For the final product, I will use a more recent GPS module. Like the Neo / Max 9 or 10 series mentioned by AndyA. Another reason to move to a GPS solution is also to avoid the...

Linking real time behaviour to alogorithm values is not a good idea. Hardly reusable, and unpredictable reactions. Implement a fixed real time behaviour and let the algorithm check if PWM should be updated, depending on limit values.

The main goal of this project is to avoid the encoder, which is not part of the machine. They have to each time install it, with cables hanging around. A solution where they open the window, install the magnetic antenna, connect the receiver to the power connector is a dream. I know GPS speed...

Mark, For various reason, RTK or dual receiver setup is not applicable. Too complex for the end users. I asked the final user about what he currently has. He told me that the current system, based on an encoder with pulse counters, displays meters with one decimal. Meaning 10cm resolution...

Hello, With a GPS, I want to measure duration and distance of the braking phase of railway machines, from 100km/h to 0km/h. I don't need absolute position precision. I juste need to measure distance of braking phase. GPS reception is good, test site is in a rural area. A first prototype is...

I already have an Ardu-stim, and even forked it to use a Teensy 4, with TFT and encoder. I want to extend it to generate real VR signals for factory ECU, transmission or diff controllers. They don't accept digital signals on VR inputs. I have a drawing of a device which generate correct voltage...

Don't connect them directly to GND or Vcc. You could set them as inputs with internal/external pull-ups. It will avoid any problems if anything make a short between pins, or between pins and GND or Vcc. Or set them as output. But see comment above.

Hi, For an engine simulator, I need to generate crank and cam position signals. Variable reluctance sensors generate one 360° sinus wave for each index, with sometime void between indexes. Nothing complex to generate with an audio output. But signals could be very low frequency during cranking...

You should connect all 3 controllers on the same bus. And configure them to be each at a different CANbus adress. this will ensure you can send single "broadcast" message to all three at the exact same time.

How are the GNDs connected ??? What is the transmission line length ??? some millimeters ?? some centimeters ??? some meters ??? If your line is long, use RS422 or RS485 line drivers. With 120ohms termination resistors and twisted pair cable, your transmission will be reliable on very long distance.

Is canSniff20 called in the CAN interrupt routine? Probably yes. Is it possible to use Hardwareserial.write in an interrupt context ????

The input structure have a pull-up resistor. Connecting a simple NPN transistor (with resistor on the base) would do the job.

You try to use COM3. Depending on your PC/laptop, COM3 could be an internal peripheral, and not the Teensy.

Looking for SSD1357Z, I found a datasheet: https://cdn.sparkfun.com/assets/4/d/0/2/7/DriverDatasheet_SSD1357_1_0__Wisechip_.pdf

If I remember, writing the file at the root level, not in any sub-directory, will also avoid slowing down. But can't remember if it is valid for all FATxx formats.

120 ohms resistors ???? Twisted pair cable ????

Teensy ADC is 12 bits. With somme errors. Check https://www.nxp.com/docs/en/nxp/data-sheets/IMXRT1060CEC.pdf