Matrix user forums

Hi, Glad to hear it's receiving ok! Can you post your code that's giving the errors? I used m ((msg) as an array to receive the data and x (& y) as data to be extracted. Both were declared as local variables ( hence the '.' at the start) - it's good practice to keep a minimum number of globals t...

The receiving end displays data to uart.. Getting data out - bytes 5 and 6. Use ( in a calculation block) .x = .m[4] .y = .m[5] Note that array indexes start at 0. If the data is a word then .x = (.m[4] << 8) + .m[5] where x is a 16 bit variable - and assuming that data is sent high byte then low (t...

- And it works !!! So one Arduino acting as a J1850 sender and one as receiver.... Note that the transmit and receive programs haven't been merged (so use Send_msg from transmit and Receive.... you get the idea.) And because it should always be done so: 'Hello World' (rotating here to keep the scope...

Now done send too.

Output looks reasonable on the oscilloscope - but receive not happy.

I'll post when it works!

Oops - defined tcnt1_buf as a byte rather than 16 bit. Now receives something reliably (ie the same every time) just not the same as the message sent

Martin

For built up areas, how about a GSM module and send text messages.

Could get pricey (story about eagle flying to Iran and racking up roaming charges.) - but with the right SIM card it could work?

Martin

Okay - created a receive message macro. If you could try it with your hardware - there is a 50:50 chance it will work (it either will work or it won't :) ) I can't test it until I do a Send macro :( and second nano can pretend. I've put a very simple test into main - tries to receive a message and o...

I converted the CRC routine (probably should have left this as C - although it is only short - going for the easy targets first!) I used a string as the message to CRC - and really should have used an array of bytes (although is string is just an array of bytes :-) ) - FC doesn't let you change the ...

Ok - a simple 'proof of concept' test (after a very long day at work :-( ) A simple circuit - two arduino nanos - ground and 5v connected (I only found one USB lead :-( ) and D3 connected to D3 (signal) One nano outputting 200us pulses (as per above but at a 1s interval) and one receiving - flashing...

Yes, we can use this to measure a pulse, we start the timer when the pin is 'set' and then record the time when it changes state again - then compare this with the low and high bound of the expected pulse length. We could probably also use the GetRawCount or GetMicroSecs - from the timer component -...

- a bit more playing and I converted the C code (above) using Timer1.. - Little conversion was necessary -just added to supplementary code. This generates a steady 202us (probably within the realms of crystal errors on Arduinos?) pulse - and can be used as a starting point for a conversion. timer_te...

I took a quick look at using a timer component - and it's opened a bit of a can of worms... So - in the first instance I try to pulse a pin a 200us intervals using a timer and a delay. (Note that this is effectively how the C code you posted measures the length of SOF pulses.) - and there seems to b...

Not quite a complete fix - needs the bit-bang alternative too! Hopefully easy for Ben & co to incorporate.

I've been trying (and failing) to get them working with an ATTiny85...

Martin

The cause of this is the lack of an end frame in Refresh()..

From the data sheet:


So adding my own refresh macro which adds an end frame:


- and the correct number of LEDs now illuminated..

Martin

Just noticed a small bug in the Arduino (I've tested) implementation of AP102C component. A simple single strand of LEDs connected to SPI (hardware) works AOK - if you remember to set B2 to output. - But I noticed that one LED was not lit. Rather than counting to 60 (ran out of fingers) - I reset th...

Hi, Yes, sorry i didn't mean to criticise - I'd hesitated to post when you first asked the question. So, yes - I program because it is interesting and fun! Flow code is good because it has a friendly (honestly, we try) forum - and, speaking for myself, I enjoy chatting and thinking about programming...

Hi Dutch, I had a little play with this after your previous post.. Can I suggest that you investigate arrays - rather than saving to 8 individual variables. It will make your code much easier to follow (and shorter to enter too - always good) I'd suggest using a property for the pins too - will make...

I don't think there is a problem if you have an external clock and don't rely on any of the hardware.... See https://www.arduino.cc/en/Tutorial/ArduinoToBreadboard - of course there is the question of what to do with the Arduino afterwards - put another chip in it - and the associated problems of in...

Happy Halloween to you all.. A Flowcode Haunted House Project.... This was supposed to have been a weekend project - but building the house itself took a lot of time. It is from Matt Bergstrom's 'Cut and Assemble' haunted house book - and the result is a nicely detailed model. There is plenty of roo...

Some fairly minor bugs (on the Arduino platform (only?)) 1) Create a property aPin as a single analog pin. It a calculation box - aPin = 1 This gives a cannot assign to non-variable on left of equals error. (Note that the analog pins can be used as GPIO on Arduino platform - so should be possible to...

If I might interrupt with a couple of suggestions: (based on some Arduino code I did in v7 - I rewrote several of the ws2812 macros...) 1) Adding a SetPixelBrightness macro for a specified pixel might allow a chain of LEDs to be used? (An array of scaling factors could be used for 'ease' of use and ...

Flow code uses th address shifted left one bit (x2) with bit 0 as r/w

Both systems seem to be in widespread use - but it is a bit confusing - though I think the unshifted form seems more common.

Martin

Hi Jan, Looks like the MCU you are using doesn't have sufficient RAM (1024 bytes on the PIC 16LF1847) for the display buffer. FC is trying to allocate a buffer of 8 x 128 bytes for the display memory (1k) and there are several other variables (currentX etc) - you could use one of the 32x128 displays...

There is a 'restore' option under the 'Window' menu.

Alt W should display it

Martin

Use the NumberToHex$ function - see post in other thread....

You can just view the variable(s) in the simulation debugger (tick the display as hex box)- or you can use NumberToHex$ to convert to a string... Here: demo.fcfx I convert to a string and then display on a lcd_16x2 - this displays the result in the simulated display correctly (but that is one awful ...