Notifications
Clear all

[Solved] Message sent at Solo error ?


Meric
(@meric)
Trusted Member
Joined: 11 months ago
Posts: 55
Topic starter  

Hi Milad, 

Nice stuff ^^

As far I know, Solo sent a messaeg when an error is encountered, right ? 

Is the lib can manage the message catching by an interrupt, or have I to code it ? 

 


Quote
Forum 1
(@milad)
Chief Member Moderator
Joined: 1 year ago
Posts: 138
 

Hi @meric

Happy to see you back, thank you.

Posted by: @meric

As far I know, Solo sent a messaeg when an error is encountered, right ? 

Yes, it does, it actually keeps sending the Error packet with 300ms Interval till the error is gone, so the users can catch them and interpret them.

Posted by: @meric

Is the lib can manage the message catching by an interrupt, or have I to code it ? 

At the moment the "GetErrorRegister" function returns you back the decimal equivalent of the errors in the error register which from that you can undrestand what error occured, but this is not at interrupt level, as doing these sort of costumization on Arduino can cause lots of other issues, since the resources are heavily shared.

I will remain available.

Regards
Milad

 

If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.


ReplyQuote
Meric
(@meric)
Trusted Member
Joined: 11 months ago
Posts: 55
Topic starter  

@milad

OK, so your advice is to not use the sent error message, but to put a request to get an eventual error message. I did that, actually, for the reasons that you mention.

=> But, is this error message can put some mess in the dial, in arriving at a non- asked moment, during a req/ack session ? 

I know that the priority is managed at a low level in CAN protocol, but I'm not really aware about UART. How collisions are managed ? 


ReplyQuote
Forum 1
(@milad)
Chief Member Moderator
Joined: 1 year ago
Posts: 138
 

Hi @meric,

Posted by: @meric

But, is this error message can put some mess in the dial, in arriving at a non- asked moment, during a req/ack session ?

In SOLO, the commands coming through UART / USB are queued, so if you request to read a parameter, there should be no interference with previously sent or received packets, but it's always good to have some little delay between the commands, sth around 1or 2ms can avoid any issue in this regard.

I will remain available.

Milad

If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.


ReplyQuote
Share: