Search results

The Teensy Micromod has twice the flash of the Teensy 4.1 but a slightly smaller amount of Serial and SPI ports (I think).

When posting code can you paste it between CODE tags using the </> button. It makes it much more likely that you will get an answer to your query as your code is presented in a more understandable mannber. #include <Arduino.h> #include <USBHost_t36.h> //...

Perhaps you should have asked CLAUDE to elucidate.

As @h4yn0nnym0u5e said you need to download and install TeensyDuino in order to program Teensy.

From Kickstarter: Will I be charged more later? That depends. When you redeem your proof of pledge, you may be required to pay applicable sales or value-added tax and/or shipping fees, depending on the reward and where it is being delivered.

Could you show your code using QNEthernet. If you do I am sure Shawn will be in touch.

I suggest you try using QNEthernet. NativeEthernet is NOT actively SUPPORTED by it's author and hasn't been for quite some time, whereas QNEthernet is VERY ACTIVELY SUPPORTED. The Author is often on this forum helping users with their Ethernet code.

Ok, when using the Teensy with an Audio Board like that, it has happened that parts from the underside of the Teensy touch parts of the Audio Board and SHORT OUT. That's one of the reasons why it's better to use tall plug and sockets for the Sound/Audio board to/from the Teensy.

A photo showing the Teensy would be useful.

Can you please post your code between code tags using the </> button. Below is what you code looks like when posted in this manner. Much more readable which will help someone to HELP YOU! #include <Audio.h> #include <Wire.h> #include <SPI.h> #include <SD.h> #include <SerialFlash.h> // Audio...

If you feel so aggrieved why don't you buy the IC_MKL02Z32_T4_QFN16 from Paul and maker your own Teensies?

"what features do you want?" Teensyduino compatibility!

Can you show your code. Paste it between code tags using the </> button.

It's difficult to say without seeing the code. When you post it do it between code tags using the </> button, it preserves indenting etc helping to read and understand the code.

It's easy to translate into English with Google Translate.

I imagine there could be some similarities with this project.

I know, sometimes you can get so engrossed in your project you cannot see the wood for the trees. Glad I could help.

Use #define MB ModbusRTUClient Then you can use MB.whatever

When you post code can you do it between code tags using the </> button. It preserves formatting and makes the code much more readable. I have included your code below.. I think you will agree there is a world of difference between the two. By the way it would be SO MUCH BETTER if you could...

This is what you need to do: Show us your code.

Glad you got it sorted. These sorts of problems can be difficult to sort out.

You could try cleaning out your temp folder. I periodically have to do this. I use the following batch file which I place on my desktop, then I can just click it. I put the pause at the end so that I have the opportunity to examine what was deleted if I wish. del /F /S /Q...

Show your code, so that we can see what is happening. Use the </> button to post your code, this maintains formatting which will make your code easier to read and understand.

Probably/possibly DEAD now!

Can you post your code so we can see what is happening. When you do post the code, use the </> button on the left. Doing it that way preserves indenting etc.

You say the Teensy functions just fine but then you say that it will not turn on or be detected by the computer until I short the USB connector ground to the USB power. Those would seem to me to be two contradictory statements. Can you reset it to blink, and flash different sketches to it...

Having detected the Teensy, what happens when you try to program it?

The fuse is a self resetting thermal fuse. Given that there was a spark you may have taken out the fuse and/or other devices. You should not need to connect either side of the fuse to cause the board to turn on. I suggest you connect the T4.1 directly to the computer to see if it still...

SD.h IS included in the SD Library, at least in TD 1.60b5. Are you ALL sure that you are NOT mixing up releases ( 1.59/1.60b5 ) of the SD and SdFat drivers with different releases of Teensyduino? I don't know whether there is a conflict but there could be.

If you are using Teensyduino 1.59, I suggest you use the SdFat (and SD) library from that release. Certain files are different in SdFat and SD (from 1.60b5 release).

What version of TeensyDuino are you using?

I've just compiled a deepsleep example for T4.0 and T4.1 without problem. I am using Teensyduino 1.60B5.

NOT without 1 change, see my post #12, now incorporated into Teensyduino. NOTE: Although the files shipped with Teensyduino incorporate the required change, it is not incorporated into the file in https://github.com/PaulStoffregen/Snooze/blob/master/src/hal/TEENSY_40/hal.c. Look at line 652...

Note that the version included with Teensyduino has an altered hal.c which allows it to compile and work with T4.x. The version on Duff's Github page DOES NOT incorporate this modification. See my post #12.

Ok, I understand you not wanting to add additional hardware, but if you have 3 spare pins you could wire each CAN Rx pin to another i/p pin and try using that (those) for wakeup purposes. Using the individual pins would tell you which CAN channel was causing the wake-up.

When you post code can you do it between CODE tags using the </> button. This maintains formatting and makes you code more readable and easier to understand. Here below is you code between code tags. Bye the way IT DOES NOT COMPILE. #include <Arduino.h> #include <imxrt.h> #include <DMAChannel.h>...

When posting CODE to the forum can you post it between CODE tags using the </> button. This preserves the code layout and makes it much easier for someone to examine and understand your code, and therefore much more able to help you.

Just a suggestion. Can you wire OR your CAN Rx lines (using diodes to isolate each other) and connect the resultant wire to a vacant pin. Then use that pin to wakeup from sleep. As I said above it will take the T4.x over 5 ms to wake up so it's more than likely that you will lose some data...

I do now recall that there was a problem with T4.x. See the comment and solution here. I think this is now included in Teensyduino, but it is worth a check just in case it has slipped through.

It is some time since I did any work with the Snooze library. I do recall that the Teensy 4.x hibernate return from sleep results in a Teensy reboot. Teensy 4.x deepsleep, however, operates as expected. I ran some tests to determine wakeup times as the T4.x was not waking up as expected. I was...

Ah, expensive carriage!

Where are you? By the way Paul has a few for sale as well.

Gosh you are clever. I would never have got that going in a month of Sundays. Welcome to Teensy by the way.

Ah yes!

As I said on the other post Teensy.exe is in "C:\Program Files (x86)\Arduino\hardware\tools\"

On Windows there is ALWAYS a directory called "C:\Program Files (x86)". If you don't spell it properly you won't find it!

You should be looking in C:\Program Files (86)\Arduino\hardware\tools

Why not just use a resistor potential divider.

From a quick cursory look the problem seems to be with static elapsedMillis lastRunTime = 0;. Each time you enter the function it is set to zero which will cause you to exit the fn in the next line of code. To overcome the problem put the elapsedMillis creation outside the fn...

You might find this interesting/of use.