Protocol to Error Message Output
- Ritterchen
- Offline
- Junior Member
Less
More
- Posts: 25
- Thank you received: 10
13 May 2024 19:40 - 13 May 2024 19:41 #300520
by Ritterchen
Protocol to Error Message Output was created by Ritterchen
Hi together,
is there a way to display incoming error messages from RS485/ Ethercat in a meaningful and easy way?
Aka take the error IDs each device sends into one pin each and convert them into a user-readable message.
E.g. Spindle Error Output sends error 21 (or 70 other errors)
It gets taken and looked up into a table what the ID stands for and displays the corresponding Message:
"Drive over-load (oL)"
Classic approach to my understanding would be to split up the int into bits, combine it together with ands and then create 70 pins that trigger the message display in the Interface. (Gmoccapy in my case)
Is there an easier way to do that?
In programming I would just create a file that gets fed into an array and then a loop that goes through that and spits out the message.
Just want to check before writing something that is already existing?
All the best
Fritz
is there a way to display incoming error messages from RS485/ Ethercat in a meaningful and easy way?
Aka take the error IDs each device sends into one pin each and convert them into a user-readable message.
E.g. Spindle Error Output sends error 21 (or 70 other errors)
It gets taken and looked up into a table what the ID stands for and displays the corresponding Message:
"Drive over-load (oL)"
Classic approach to my understanding would be to split up the int into bits, combine it together with ands and then create 70 pins that trigger the message display in the Interface. (Gmoccapy in my case)
Is there an easier way to do that?
In programming I would just create a file that gets fed into an array and then a loop that goes through that and spits out the message.
Just want to check before writing something that is already existing?
All the best
Fritz
Last edit: 13 May 2024 19:41 by Ritterchen.
Please Log in or Create an account to join the conversation.
18 May 2024 08:45 #300899
by andypugh
Replied by andypugh on topic Protocol to Error Message Output
I don't think that there is anything existing other than the "message" component and that would require the tangle of HAL that you describe.
This seems like a job for a Python userspace component.
If you do write it, consider submitting it to the project for inclusion.
This seems like a job for a Python userspace component.
If you do write it, consider submitting it to the project for inclusion.
Please Log in or Create an account to join the conversation.
18 May 2024 13:00 #300912
by cmorley
Replied by cmorley on topic Protocol to Error Message Output
Qtvcp/QtDragon and Gmoccapy have most of what you need:
linuxcnc.org/docs/stable/html/gui/qtvcp-...#_code_messages_code
linuxcnc.org/docs/stable/html/gui/gmocca...ration-user-messages
Sounds like you need one that uses a S32 HAL pin to select the message.
Is it just the change in the S32 that would change the messages or would there be a trigger but pin?
Chris
linuxcnc.org/docs/stable/html/gui/qtvcp-...#_code_messages_code
linuxcnc.org/docs/stable/html/gui/gmocca...ration-user-messages
Sounds like you need one that uses a S32 HAL pin to select the message.
Is it just the change in the S32 that would change the messages or would there be a trigger but pin?
Chris
Please Log in or Create an account to join the conversation.
Time to create page: 0.146 seconds