shawn

Yes, you could do that.

The short answer is that C strings don’t work with the ‘+’ operator. If you could share your code, or even a small representative runnable snippet, I could better provide guidance.

I’m not certain what your code looks like or what you’re doing, but does this link help? How to write data to connections Delays in order to send data aren’t necessary. Note that QNEthernet doesn’t send data immediately when writing data unless...

For anyone else facing this. I ended using the below instructions which worked perfectly. This is the line that goes in the .rules file SUBSYSTEM=="tty", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0483", SYMLINK+="ttyTSY%E{ID_SERIAL_SHORT}"...

I just pushed a bunch of changes that add Mbed TLS support. I'm still working on the design, but I'd love some opinions about what I have so far. I updated the README and added an MbedTLSDemo example. The design relies on lwIP's "altcp" feature...

If you want to use SLIP framing, see my SLIPStream Stream decorator library here: https://github.com/ssilverman/SLIPStream

My problem is that I can't see a problem and that this was a little too seamless... :D

I have dug through this forum a bit, and I know that this has already been brought up a few times, but I want to write my own plea. I have been using a teensy 4.1 for a formula SAE project to create a custom ECU for an electric vehicle. It was...

If you’d like, I can try to build it here and see what I can find. Something’s amiss with your setup.

Do library.json (preferred) or library.properties files exist in the root of those libraries under lib/?

Another tip: if you wanted to, you could dispense with putting WDT_t4 and teensy4_i2c inside your lib/ folder and instead use lib_deps, as follows. That is, unless you really want to use specific local copies. Note that when you build, the...

What happens if you change toolchain-gccarmnoneeabi@ to toolchain-gccarmnoneeabi-teensy@? Also, I don’t think any of those build flags are needed here because they’re the defaults (maybe with the exception of "-ffast-math"). In addition, the...

Awesome to see it drop in and working shawn!

Everyone starts there too, no worries. I really appreciate that, even as a beginner, you were willing to try these steps out. It gives me information about how easy it is to use my Ethernet library (QNEthernet). I adjust from there. A brief bit...

Looks like it works. Thanks for trying that out.

The deprecated warning is fine. I'm just trying to encourage use of the other Ethernet.begin() functions that don't take a MAC address. I can't see the code because you didn't attach Artnet.cpp. Sounds like it works now? :)

You didn’t attach your Artnet.h file, so I can't see what you have, but for that error, I suspect you didn’t do step 2, adding that “using” line. See my post #7. To recap the steps: 1. Replace the NativeEthernet.h and NativeEthernetUdp.h includes...

Did you see step 1 of my post #7? To use QNEthernet, replace all NativeEthernet.h and NativeEthernetUdp.h includes with a <QNEthernet.h> include. Make sure to also do step 2 just below the step 1 change(s). I suppose I could have said “all”...

I agree with @defragster. It looks like you're still including NativeEthernet.h and/or NativeEthernetUdp.h somewhere. Also, please attach the INO file.

Thank you for the offer. If you're using the Arduino IDE, you can just add the "QNEthernet" library. Next, do these steps: 1. Replace the NativeEthernet.h and NativeEthernetUdp.h includes with a single <QNEthernet.h> include. 2. Add a using...

Thanks for the explanation. I’m trying to solve some slowness if QNEthernet’s Ethernet.end() and then begin(…) is called. I’m verifying that all the pins are as they should be when they should be. You’re correct that I’m using these as peripheral...

Do you actually override yield() or use the EventResponder mechanism?

@Megatree_de In my quest to achieve great compatibility, would you be willing to try QNEthernet? All you’d need is to replace NativeEthernet.h with QNEthernet.h (and add a “using” line: using namespace qindesign::network;) and you don’t need to...

Yep. Search works better now. Thanks!

Forum works so much nicer on phones

Thank you for those clarifications, but I'm not following your answer with regards to INPUTs (Arduino-style "INPUT", no pull-up or pull-down) (I also think you were trying to answer my auxiliary question; thank you). Why would the DSE (drive...

Are you saying that the drive strength is only relevant to open-drain-output-configured pins? If that’s true, why are those being set for input pins? Even if it’s not true, why would they be set for input pins at all?

I'm fine with it the way it is now, but did you want to limit the duration after a post where you can edit it? Right now, it's letting me edit anything I've posted.

An auxiliary question is: Are pull-ups and pull-downs enabled when DSE (drive strength) is set to non-zero (output driver not disabled)? The chip spec. leaves me a little uncertain. It does say, “Pull-up, pull-down, and pad keeper are disabled in...

Why is the output driver enabled for INPUT modes for GPIO pins? (Drive Strength Enable (DSE) bits.) I'm seeking understanding. (Even for pull-up and pull-down input modes, maybe the pin sources current through the pull resistors, but this doesn't...

I just tried the search again (for “dsb”) and it finds this one message. Maybe something needs to trigger a re-index?

The ability to search for shorter terms such as "dsb".

Some code notes: 1. Add the listeners before starting and setting up Ethernet. This way, they’ll catch all events, including setting the static IP. 2. There’s extraneous arguments in the printf line that prints the local IP. 3. For code...

Here’s a link to Paul’s original Ethernet test code: https://github.com/PaulStoffregen/teensy41_ethernet Side note: I’ve implemented a Mongoose Ethernet driver for the Teensy 4.1.