For newbies like me: Hal Pin Numbers ==> versus =>
- blacksmith99
- Offline
- Junior Member
-
Less
More
- Posts: 36
- Thank you received: 4
31 Dec 2014 12:40 #54443
by blacksmith99
For newbies like me: Hal Pin Numbers ==> versus => was created by blacksmith99
Hi,
You might see the following error in the Debug file information:
Debug file information:
your_hal_file.hal:199: Pin '<==' does not exist
5504
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
The 199 tells you the error is on line 199 in your hal file.
**************
An excerpt from the Upgrading to 2.6 from 2.5 Wiki:
HAL syntax for connecting pins & signals is more strict
The halcmd manpage has always shown "<=", "=>", and "<=>", preceeded and followed by a space character, as the accepted arrows for connecting pins and signals. However, before 2.6 halcmd would accept any number of "=" characters in the arrows. As of 2.6, only the documented arrows are accepted. If you have a "net" command in a .hal file that uses multiple "=" signs, you'll get a load-time error. Simply change it to use the documented arrow styles to fix it.
***********
I worked on this quite awhile before finally finding the fix in the Wiki note above.
Before the 2.6 version it ran without complaint.
After 2.6 they are enforcing the rules!!
Anyway, I hope this helps someone else looking for a problem after the upgrade.
Regards,
BS99
You might see the following error in the Debug file information:
Debug file information:
your_hal_file.hal:199: Pin '<==' does not exist
5504
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
The 199 tells you the error is on line 199 in your hal file.
**************
An excerpt from the Upgrading to 2.6 from 2.5 Wiki:
HAL syntax for connecting pins & signals is more strict
The halcmd manpage has always shown "<=", "=>", and "<=>", preceeded and followed by a space character, as the accepted arrows for connecting pins and signals. However, before 2.6 halcmd would accept any number of "=" characters in the arrows. As of 2.6, only the documented arrows are accepted. If you have a "net" command in a .hal file that uses multiple "=" signs, you'll get a load-time error. Simply change it to use the documented arrow styles to fix it.
***********
I worked on this quite awhile before finally finding the fix in the Wiki note above.
Before the 2.6 version it ran without complaint.
After 2.6 they are enforcing the rules!!
Anyway, I hope this helps someone else looking for a problem after the upgrade.
Regards,
BS99
Please Log in or Create an account to join the conversation.
Time to create page: 0.090 seconds