It looks like you're new here. If you want to get involved, click one of these buttons!
Subscribe to our Patreon, and get image uploads with no ads on the site!
Base theme by DesignModo & ported to Powered by Vanilla by Chris Ireland, modified by the "theFB" team.
Comments
just because you do, doesn't mean you should.
btw this particular "funny" has been resolved, although I'm not sure why the "solution" works. You received a message (RS485 bus) and are replying to it. Replying to it immediately causes the outgoing message to be garbled (although the TX buffer, and the trace buffer that I put in in an attempt to diagnose this) contain exactly what I'd expect. but if you set up a timer, and delay the TX by 2 clock ticks (ie you don't turn on TX interrupts until the timer has gone off), then everything works fine. maybe the RS485 h/w needs more time to react to being told "You're not receiving now, you're transmitting". Only happens with some messages, I guess its the ones that don't take long to process.
Seriously: If you value it, take/fetch it yourself
Seriously: If you value it, take/fetch it yourself
What ails you?
As per earlier post, I think I've got round the problem I was having, which appears to be a timing issue.
The present job is an "i/o board" which reads 8 digital inputs and writes 8 digital outputs according to messages sent on an RS485 bus. What did you do with your PICs?
Seriously: If you value it, take/fetch it yourself
Interpreting data from a line-scan camera for industrial measurement (parallel in/out + synchronising & timing);
Running a fatigue test rig (with 3 digit display & presettable counter, all from the PIC);
Various other hobby stuff including a 3 axis camera mount with R/C servos...
Brought up on 6502s