Search results

Or maybe any limitations of sending the request within a WHILE loop?

Was wondering if anyone knows of anything that would prevent the Midi Channel msg being sent or even blocked? ie: does something else need to be enabled first or if something else is running this prohibits the channel msg???

I have a home-made MFC (midi Foot Controller). It uses a Teensy 3.6 MPC. It performs most tasks adequately (ie: change Preset/Scene, read Reset name, toggle individual effects on/off etc). However - I'm trying to get it to detect if the AXEFX 2 is switched on - before it starts running the main...

hmmm - just spotted a major flaw in my proposal. ie would still need to power the Teensy somehow. Doh!!

Appreciate the easier thing to do would be to just go buy some off the shelf suitable lights. But TBH we're back in a COVID lockdown & i need something to fill the time with AND also I'm sick of buying these things only to be disappointed with battery life. So.... i have (well the wife has to...

Hi, I decided to give up on the payload implementation. I got it working without - so decided to invest the time on other aspects. May revisit in future. BUt thanks allfor the help. Another question i have is with regards powering these units with batteries. I'm using these NRF24L01+...

Thanks for all the responses. I now understand what's happening and why.

OK. So ref the RTC re-sync code snip I included in the OP? What is this trying to achieve? Will it only resync teh RTC if I "send" something on the Serial port?

I've been adding a RTC to my Temp Sensor project. I pulled code from the various availbe example sketches. I have the following in the main Void Loop() if (Serial.available()) { Serial.println("Serial Available"); time_t t = processSyncMessage(); if (t != 0) {...

https://www.amazon.co.uk/dp/B01FX7909Q/ref=pe_385721_149135791_TE_itemhttp:// doe sthis link work?

BTW - looks very simialr to that one. But markings are slightly different. Mines does nt call out teh Touch COntroller XPT2046. Just says HVGA 480x320

OK thanks. Per post #14 & 19 - I assumed these folks had already proved thsi display can work with Teensy. I will take a look at the Libs you have suggested - cheers

Im seeing things like TFT_CS LCD_CS TFT_RST LCD_RST which I assume are equivalent. But then TFT_RS LCD_DC are they equivalent? Sorry - probably quite simple - but just not getting it.

Kuman 3.5 inch 320*480 Resolution Touch Screen TFT LCD Display With Protective Case + 3 x Heat sinks+ Touch Pen for Raspberry Pi 3 Model B, Pi 2 Model B & Pi Model B+ SC11 https://www.amazon.co.uk/dp/B01FX790...135791_TE_item Its the Dispay pin numbers Im after (not descriptions) pls. SO I...

HI - returning to this after several years. SO trying to get the OP TFT workinhg with a T3.2 again. Im so confused with all teh different labelling for teh various pins. SO can some mark the TFT pin number against the Teensy Pin Number pls

TBH. I apprecaite folks are not recommending using my earlier stated method of adding order of a 1000 to the various senors to ID them. But that does appear to work. So wondering what I will actually benefit from perserving with the 'typedef struct'.

Was just starting to believe it was time to give up on the 'typedef struct' stuff. Just couldn't get it to work fully. typedef struct { uint16_t NodeId; //2 byte integer float temperature; //4byte float } PayloadFrame; static PayloadFrame Out_Payload; Implemented as suggested - but the...

Will give the 'type-definition' stuff another crack in the morning. On a side note in the mean time... As a stop gap, I did what I refered to in a previous post -ie added 2000 to the reading of 1 sensor before TX'ing & 3000 to the other. The idea being that I would know where the reading came...

Sorry been off line for a few days. Thanls for that info. Nothing is ever simple is it :)

Hi, Sorry Didn't make a note of the ID that was being Recieved - but it was at least an 8 didgit number. And it changed sometimes too. Even though it was coded thus: unsigned int ID = 2; // sets the unique ID. The Temp recieved was always reading 0.00. Unfortunately I've removed that code...

Fair enough - thanks

Can I be really cheeky & ask for a response to teh 2nd part of #64 pls? (ref the code in ##57). The pay load is not returning whats being send - so I'll put that on back burner for now.

:) yes they were 2 seperate statements - sorry. 1st one relating to teh payload. 2nd just a general question about that link you sent.

Sorry - but the payload thing is a little unlcear to me at the moment. Apprecite teh advice & I will look at it a little further down the line. Also ref the code you ref'd in #57. Am i missing something - but is there anything in the Rx code that guarentees that when radio.read(&temp1...

Thanks for your thoughts. I understand what you are saying. But I am storing all the reading Im getting on an SD card on the Base/Rx unit. So its critical I know which reading came from which Sensor/Room. As Im sure CorBee can confirm - my knowledge on this RF stuff is quite limited - this is...

once more - thank you.

Believe me I have been - for the last 2 hrs. I did come across this one. But from what I can see - this just sends a float from each Tx project (ie temp1 & temp2 resp). The base unit then reads the sent "floats". Its not sending a String ? Sorry if Im missing something obvious.

Hi, Any ideas how I would take the temperature value from senor (which is a float) but then send it as a string prefixed with some text. ie Sensor reading = 23.25 So sent vlaue would be Sensor-A_23.25 I can send & receive a Float nps now. But as i will hopefully be wanting the base unit to...

..and good on you to keep persevering on your end too. Im off to try & send soem reall data now. Later!

I had more than fingers crossed mate & but it appears between all teh things we had crossed - it's done teh trick- looks like you've suceeded. They're now working.!!!!!! Thanks so much for your guidance, wisdom & patience. Much appreciated. No doubt I'll be back - so don't run away to far :)

Yep = thats exactly what Im doing :) Thanks

Several. So does the 1st set of report output I posted - with the MCU & RF unit mounted on a Perf Baord look OK? ie Post #45

Sorry my post wasnt clear - forgot to paste the report in that post. So I concluded that becasue originally I was getting this: ***** CheckConnection Starting ***** FIRST WITH THE DEFAULT ADDRESSES after power on Note that RF24 does NOT reset when Arduino resets - only when power is...

This what im now getting with a single project on a perf board:

I did yes - no luck either. I'm currently trying solder Nano & Radio unit onto a small perf board. WIll report back what that yeilds. Thanks for your continued support & help.

Yes doen this too

thanks. I'm using short cables as still working at breadboard stage. wires are 100mm max. Got 2 modules running now. But still can get data to be recieved

DOH!!! Now dont I just feel stupid (again). Maybe thsi RF stuff is just a step too far for me. I did think it was strange. But I thought the switching was being done in the code - to send as a Tx then switch to recieve as a Rx. All teh other examples I seen explicity called out seperate code...

OK I got really frustrated with all this and took it right back to basics. Now my board literally just has the NRF24L01+ connected. And I loaded the GETTINGSTART project that comes with NRL24 library - just to see if I could get one of these things to talk to itself. BTW - I had to change the...

hmmm I trie dthe TX exmaple as suggested. Still got TX failed msg in Serial. But accidently disconnected teh SCK pin from board (aka D13 on Nano) & it suddenly changed to Acknowledge Recieved

BTW - change my Tx Code to just this : void loop() { currentMillis = millis(); BlinkLED(); String myStr= "Text"; bool rslt; rslt = radio.write(&myStr, sizeof(myStr)); Serial.println("Data Sent "); Serial.println(myStr); if (rslt) {...

OK will crack on with this later. Family stuff to deal with Im afraid. Thanks for help so far

no no - sorry. I was responding to you comment about simple code. WHilst waiting for teh new HW I started on tehRTC & Log captuiing to SD card. Thast why my code is full of other stuff :) I have everything here now.

Thanks. I take your points. I'd started the sensor stuff first becasue I was waiting for the Nano's & NRF24L01+'s to arrive :). SO to my earlier point ref 'nan'. Could I be getting that even if teh Tx isn't actually sending anything?

I couldnt get that to work - but i'll keep trying. TBH dont really understand teh format of teh read & write commands with teh "&" prefix & size of float

I can only view 1 serial at a time - but when connected to the Rx - the recvieved value just reads '****** SENT Temperature : nan 4' ' radio.read(&SENT_temperature, sizeof(float)); // Read information from the NRF24L01 Serial.print("****** SENT Temperature : ")...

Transmit: #include <SPI.h> #include <OneWire.h> #include <DallasTemperature.h> #include <elapsedMillis.h> #include <nRF24L01.h> #include <RF24.h> #define ONE_WIRE_BUS 2 int debounce_time = 100; int ButtCntr = 0; unsigned long currentMillis; unsigned long previousMillis = 0; unsigned long...

I will do :) Its just Im not at my PC at moment

Thanks - so does the NAN imply its definately recieving "somethng". I have no idea how to check if actually recieving soemthing.

So managed to get teh Teensy 3.6 reading Temp vlaues from sensor. I also manged do the same with a Nano. SO moved onto installing the NRF24L01+'s on both T3.6 (Rx) & Nano (Tx). All i ever get is "nan" on the Recieving T3.6. Spent all afternoon trying various thing & nothing. Is teh "Nan"...