<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67603/hx711-routines-using-in-ant-bike-powe-rmeter-example</link><description>i am developing a bike power meter and designed my own hardware. 
 From software point of view I used the Ant+ bikepowermeter example from Nordic. 
 So far my status is, 
 connect to Garmin sportswatch and accepted as bike powermeter. works! 
 calculating</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Oct 2020 11:07:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67603/hx711-routines-using-in-ant-bike-powe-rmeter-example" /><item><title>RE: hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/thread/277108?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 11:07:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:525c24ce-88ac-4816-adc3-3b8981d2b121</guid><dc:creator>bronsus</dc:creator><description>&lt;p&gt;Thanks now it works. Thank you very much for your excellent support!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/thread/277104?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 10:56:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbeafd2d-c50d-4c8b-b514-aa0ff57c6127</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Try to compile hx711 with optimization enabled.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/thread/277065?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 09:22:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:72b99fe7-2f5d-4d45-a541-b5dc9475884e</guid><dc:creator>bronsus</dc:creator><description>&lt;p&gt;I just changed the interrupt level to 2 and also tried 3, but no changes, :(&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/thread/277048?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 08:49:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f6d5ead1-c32a-474d-aec3-dbacb7813116</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;You are right that the softdevice can interrupt the application as for instance shown here:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/processor_avail_interrupt_latency/exception_mgmt_sd.html"&gt;https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/processor_avail_interrupt_latency/exception_mgmt_sd.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Using interrupt level 2 and 3 may be better than using 5, 6 or 7 for application timing critical events.&lt;/p&gt;
&lt;p&gt;The timing should be similar to BLE, so it is in the order of 60-70us for softdevice timing critical events (level 0 and 1):&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/ble_processor_avail_interrupt_latency/ble_peripheral_connection_performance.html"&gt;https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/ble_processor_avail_interrupt_latency/ble_peripheral_connection_performance.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/thread/277026?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 07:37:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a8452bb-d915-491b-a402-4d401c06c9e5</guid><dc:creator>bronsus</dc:creator><description>&lt;p&gt;Hi Kenneth, thanks for your quick reply which helped me. I changed&amp;nbsp;&amp;nbsp;&lt;span&gt;GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS&amp;nbsp; from4 to 6 and now there is no memory error any longer.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;But now I am facing a new problem.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Th hx_sample () routine always comes back with&amp;nbsp; Data_Error.&amp;nbsp; I set some Debug Points and figured out that&amp;nbsp; m_sample.count = 20, which says me that the readout has been interrupted by an Interrupt,&amp;nbsp; probably by the softdevice. Normally the&amp;nbsp;m_sample.count should be 24 when everything has been read out.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any ideas&amp;nbsp; ?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: hx711 routines using in ant bike powe rmeter example</title><link>https://devzone.nordicsemi.com/thread/276881?ContentTypeID=1</link><pubDate>Mon, 26 Oct 2020 13:30:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58cee638-77ba-4939-8cbf-2326db64e0b4</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;The easiest should be to start with the ANT example (which use the softdevice) and then include the peripheral drivers and code into the ANT example, rather than the other way around.&amp;nbsp;For instance the ANT example is configured with&amp;nbsp;SOFTDEVICE_PRESENT in the preprocessor symbols which is used by the peripheral drivers, you would need to copy all the defines sdk_config.h to the ANT example.&lt;/p&gt;
&lt;p&gt;If&amp;nbsp;&lt;span&gt;nrf_drv_gpiote_in_init() return&amp;nbsp;NRF_ERROR_NO_MEM, then I suspect you should increment&amp;nbsp;GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS in sdk_config.h&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>