Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Triffid_Hunter: how goes the hacking?
- sliptonic: Some luck with the motherboard side of things. No luck on the extruder at all.
- sliptonic: It consistently reports the same value for the thermistor whether the extruder is connected or not.
- - 21:03 -
- sliptonic: I'm not convinced the two are even talking but I'm not sure how to test it.
- Triffid_Hunter: have you ever hacked on things in such a way that involved accessing raw memory?
- sliptonic: No. Always willing to learn though.
- Triffid_Hunter: would be interesting to write something into the rx struct and see if the reported value changes and stays changed
- sliptonic: Is it something you can talk me through?
- - 21:11 -
- Triffid_Hunter: sliptonic_shop: hm, do you have func.sh stuff working? can you mendel_reset; mendel_talk
- sliptonic: I've never heard of it. Where do I find it?
- Triffid_Hunter: sliptonic_shop: using linux or mac?
- sliptonic: linux
- Triffid_Hunter: lovely, well have a look at func.sh in your teacup repo
- * sliptonic walks up to the workshop
- Triffid_Hunter: put in your arduino serial device, then source ./func.sh in your shell.. that'll let you call all the functions therein like regular commands
- - 21:17 -
- Triffid_Hunter: the relevant ones here are mendel_readsym and friends which use M253/M254 to read arbitrary memory while it's running
- Triffid_Hunter: yep, M253
- sliptonic_shop: o.k. I think that's running
- Triffid_Hunter: mendel_readsym pulls addresses from mendel.sym, so you can for example mendel_readsym_uint8 mb_head to get the movebuffer head, or mendel_readsym_mb (special command) to dump the whole movebuffer
- Triffid_Hunter: or you can pass it an address you've come up with yourself
- - 21:25 -
- sliptonic_shop: mendel_readsym_uint8 mb_head returns 0
- sliptonic_shop: mendel_readsym_mb
- sliptonic_shop: dumps everything. cool.
- Triffid_Hunter: see what mendel_readsym rx gives you, should be 22 hex chars as it's 11 bytes long
- sliptonic_shop: 6900890D890D003C550000
- Triffid_Hunter: lose the first 10 (they're packet headers), next four should be a pair of temp readings if we're very lucky
- Triffid_Hunter: ah that's interesting, first should be 0x55
- Triffid_Hunter: mendel_readsym tx starts with 0x55?
- sliptonic_shop: 690000000000003C000055
- - 21:32 -
- Triffid_Hunter: hm, seems like your intercom isn't running
- Triffid_Hunter: post your config
- sliptonic_shop: http://pastebin.com/F9dS7ahQ
- sliptonic_shop: extruder config too?
- Triffid_Hunter: hm config looks ok
- - 21:39 -
- Triffid_Hunter: I'll have to have a play with it
- Triffid_Hunter: maybe put a serial_writechar('!'); in start_send in intercom.c or something so you can see if it's triggering
- sliptonic_shop: It won't let me. undefined reference to 'serial_writechar'
- Triffid_Hunter: may need to #ifdef HOST #include "serial.h" #endif at the top.. my toolchain complains about implicit declaration but links successfully, are you using the IDE?
- sliptonic_shop: yes.
- - 21:50 -
- sliptonic_shop: my skills are weak: what's wrong with this? http://pastebin.com/vkPspxae
- Triffid_Hunter: sliptonic_shop: might not like it before variable declaration, move it down a few lines, just before enable_transmit()
- - 22:00 -
- sliptonic_shop: o.k. the serial monitor is showing a marching line of exclamation marks. Like it's running start_send repeatedly.
- - 22:07 -
- Triffid_Hunter: sliptonic_shop: and so it should, about 100 per second?
- sliptonic_shop: About 2 or 3 per second.
- Triffid_Hunter: ah right, my bad, should be 4 per second
- sliptonic_shop: fair enough. I'll buy that.
- Triffid_Hunter: still no indication as to why tx wouldn't start with 0x55
- - 22:14 -
- Triffid_Hunter: hm, ends with 55 though
- Triffid_Hunter: wonder if gcc is packing it backwards
- Triffid_Hunter: they both have 55 actually, but in different spots
- sliptonic_shop: Any reason to believe this is related to my configuration at this point?
- Triffid_Hunter: no
- sliptonic_shop: was it something working at one time that has potentially changed?
- Triffid_Hunter: move your debug marker to the receive packet block, starting at line 167: if (packet_pointer >= sizeof(intercom_packet_t)) { here
- Triffid_Hunter: sliptonic_shop: I've never tested this stuff, markus amsler is the one who suggested the protocol change, then significantly fleshed out my skeleton code
- - 22:22 -
- sliptonic_shop: done. looks about the same 3-4 per second.
- Triffid_Hunter: hm so we should be receiving packets
- sliptonic_shop: I'm going to need to bail for the evening. I'll be around tomorrow though. Then gone for a week (kids on spring break).
- - 22:28 -
- sliptonic_shop: If you have any thoughts or want me to test anything, I'll stay logged in. Thanks again for the time.
- - 22:35 -
- Triffid_Hunter: yw, post on the forum, see if markus amsler has any ideas or comments
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement