Most recent activity
-
- 7 comments
- 846 views
-
thanks for your help! I will play around with this method and write some code to produce the correct strings of bits. I'll do some testing with a sent decoder. If I find that it works well, I can try to write something up, perhaps others will find this useful.
-
I would really like to try it on the nRF52, i can verify with an ocsilloscope , if anything it will be a learning experiance.
-
I'm doing to project where I would like to be able to transmit SENT messages:https://www.renesas.com/us/en/document/whp/tutorial-digital-sent-interface-zssc416xzssc417x#:~:text=The%20basic%20unit%20of%20time%20for%20SENT%20is,starts%20a%20message%20frame%20and%20provides%20a%20method.
My first thought was to use the digitalpulse method but I then realized that the longest unit of time "tick" can be 90uS. the timeing may require using low level programming. I'm looking for a place to start, I can write my own module but perhaps there is a module that I can start with. I'm just looking for any advice on how to best tackle wtih issue.
thank you in advance. -
- 5 comments
- 670 views
-
I think you are correct I, tested with hardware & software I2C and I can relaibly communicate with my hardware now !(with external pullups) I'm not entirely sure what happened overnight but when I went to debug using the hardware I2C this morning it just worked straight away, then it worked fine with the software defined I2C as well. I think my biggest hangup was the software not throwing an error with the software I2C, I didn't know what was going on. Now that i'm aware of that quirk, it wont surprise me in the future. thanks for your help!
-
Thank you for your prompt response, Gordon. It is good to know this quirk of the software I2C, I will change my code to rely on the hardware I2C instead, for now. Does the Software I2C object accept arguments to disable internal pullup feature when the External Device already has Pullup resistors? This would be ideal for some of my work. I will get back to testing my custom pcb, I designed a small hat for the MDBT42Q breakout board to interface with a texas instument LDC3114 chip and add analog output capability utilizing a MCP4725 DAC. both of these chips are on a I2C bus. Thanks again!
-
I was having an issue with setting up chip Via I2C with the MDBT42Q breakout board. I kept getting numbers that made no sense. I disconnected the Chip from the Board and the I2C read command would still return "data". I belive there is something wrong with this function. I setup an I2C again, with nothing attatched and the read function still returns something with no error. I'm running the lastest firmware I could find; espruino_2v17_mdbt42q.
pasted from the web editor:
var i = new I2C();
=I2C: { }
i.setup({ scl : D15, sda: D14 });
=undefinedi.readFrom(0x2A, 3)
=new Uint8Array([255, 255, 255])this occurs with nothing connected to the MDBT42Q breakout board. I think i need some help with this!
I would be happy to contribute to the espruino community!